Status lifecycle
Payments and payouts move forward through a fixed set of states.
A transaction is created in pending and moves forward only. The last three states are final and never change again.
| Status | Meaning | Final |
|---|---|---|
| pending | Awaiting customer approval | No |
| processing | Accepted by the provider and being processed | No |
| success | Funds received; your wallet has been credited | Yes |
| failed | Refused by the customer or provider | Yes |
| expired | Customer did not respond in time | Yes |
Finding out the outcome#
Two ways, and you should build both:
- Webhook. We POST the final state to you. This is the primary path. See Webhooks.
- Status endpoint. Poll
GET /payments/{id}at any time. Use it as a fallback and for reconciliation sweeps.
Do not settle on a 202. A 202 Accepted means we took the request, not that money moved. Only release goods, credit an account or mark an order paid on a final status.
Payouts#
Payouts use the same non-final states, but end in success or failed only. A payout has no customer-approval step, so it cannot expire. Expiry belongs to pay-in, where the customer must approve in time.
After a final status#
A final status is final for that transaction. Provider reversals and operational corrections are handled separately from the transaction's own status.
Pending confirmation How a reversal or correction is represented, and whether it appears as a separate ledger entry and event, is being confirmed.
Maly Tech Ltd. This guide is provided for information. Where it differs from your signed agreement, the agreement applies.