Release 2026-08-11
This release focuses on improving payment operations and financial visibility, with clearer decline and failure information in the Dashboard, support for payments where the platform acts as the seller, and new API capabilities for querying payouts and their underlying movements.
With these updates, platforms can more easily understand unsuccessful payment outcomes, support platform-owned payment flows, and access the payout data needed for reconciliation, reporting, and operational workflows.
Enhanced Dashboard decline reasons
Payment decline and failure reasons are now presented more clearly in the Getpaid Dashboard, providing platforms with more actionable context when reviewing unsuccessful payments.
This improved visibility makes it easier to understand payment outcomes directly from the payment details view, reducing the effort required to investigate failures and supporting more effective operational and customer support workflows.
See the payment lifecycle documentation for more information about payment states and outcomes.
Platform as a seller payments
Platforms can now support payments where the platform itself acts as the seller, expanding the payment flows that can be handled through Getpaid.
{
[...]
"splits": {
"type": "per_transaction",
"accounts": [
{
"type": "seller",
"id": "acc_4q90qx2kdczs59yqfq34p09qx6",
"split": {
"type": "remaining"
}
}
]
},
[...]
}
This enables platform-owned transactions to use the same payment capabilities and lifecycle handling available across Getpaid, providing greater flexibility for platforms that need to collect payments directly in addition to supporting their sellers.
See the Getpaid API reference for more information about the available payment and checkout capabilities.
Support for querying payouts and payout movements
Platforms can now query payouts through the Getpaid API, providing programmatic access to payout information across the accounts available to them. Results can be restricted to a specific account or filtered by payout status, making it easier to support reconciliation, reporting, and operational workflows across sellers.
{
"type": "payouts",
"filters": {
"account_id": "acc_44678r08jtm8zbt227tzhc4nw5",
"statuses": [
"completed"
]
}
}
The response includes matching payouts together with their account, lifecycle status, amount, currency, and timestamps.
{
"type": "payouts",
"cursor": "Q3VyaW9zaXR5IEtpbGxlZCB0aGUgQ2F0Cg==",
"data": [
{
"id": "pyt_4y1qet59bdxz8ae7psj6vdh4w1",
"reference": "PAYOUT-20260804-0001",
"account": {
"id": "acc_44678r08jtm8zbt227tzhc4nw5",
"legal_name": "Titan Biking"
},
"status": "completed",
"amount": 431100,
"currency": "EUR",
"created_at": "2026-08-04T09:30:00.000Z",
"updated_at": "2026-08-06T11:12:00.000Z"
}
]
}
See the Query payouts API reference for the complete request and response schemas.
Each movement exposes its balance impact and processing fees, together with information about the financial operation that generated it and, for payment-related movements, the associated payment.
{
"cursor": "Q3VyaW9zaXR5IEtpbGxlZCB0aGUgQ2F0Cg==",
"data": [
{
"id": "mov_4y1qet59bdxz8ae7psj6vdh4w1",
"type": "capture_split",
"gross_amount": 450000,
"processing_fees": 600,
"net_amount": 449400,
"currency": "EUR",
"created_at": "2026-08-01T13:45:00.000Z",
"operation": {
"type": "capture",
"id": "cpt_57fm2pjycji1jbj68h1rvk9bnc",
"reference": "ORD-202608-0012",
"gross_amount": 500000
},
"payment": {
"id": "pay_4y7kptsvn11qq6d354g5tx735v",
"reference": "ORD-202608-0012",
"gross_amount": 500000,
"origin": {
"type": "checkout",
"id": "cko_4kf9v6xp00hzc99rdwr5m97wce"
}
}
}
]
}
Together, payout and payout movement queries give platforms direct access to both payout-level information and the movements assigned to each payout, enabling more detailed reconciliation and financial operations.
See the Query payout movements API reference for the full schema.