Trace a payment
When you need to answer "what happened to this bill, in what order" — a support question, or a disagreement between the till journal and the platform — the payment's status history is the record to read.
Payment history
curl https://api-live.kcpboundless.com/api/transactions/by-payment/01997b3e-6c31-7a42-9f10-4d2c8b5e7a01 \
-H "X-API-Key: bndl_live_..."
Returns the append-only status history for a payment, newest first. Each element is one status event, carrying:
| Field | Meaning |
|---|---|
status | The state the payment moved to. |
previousStatus | The state it moved from. |
actionReference | The action that caused the move. A void carries a VOID- prefix. |
failureReason | Why, when the event is a refusal or an error. |
acquirerReference | The acquirer's own reference for the event. |
transactionEventId | Unique to this event. |
The history is how you confirm after the fact that a CANCELLED payment was
voided rather than cancelled at the device: look for the VOID- prefix on actionReference
(see Reverse a payment).
Raising a case with support
When raising a case about a specific payment, include:
- the payment
id, - the
pspReference, - the
acquirerReferenceif you have it, and - the UTC timestamp.
Those four identify the event unambiguously on both sides. Integration support and production escalation contacts are issued with your onboarding pack.