This SNAP Disbursement guide is currently available in English.
Retrieve the latest state of a Regular or BI-FAST transfer.
POST /v2/payments/disbursements/snap/status
Choose your transaction reference
Request: provide exactly one of originalReferenceNo or originalPartnerReferenceNo, together with the appropriate service code. Sending both lookup identifiers is rejected.
Response: a successful inquiry includes both original references, identifying the same transaction. They are not two separate transfers.
Field
Type
Required
Description
originalReferenceNo
string
Conditional
Brick transaction reference. Supply this or originalPartnerReferenceNo, not both.
originalPartnerReferenceNo
string
Conditional
Your original transfer reference. Supply this or originalReferenceNo, not both.
serviceCode
string
Yes
01 for Regular; 02 for BI-FAST.
Transaction outcomes
State
latestTransactionStatus
transactionStatusDesc
Meaning
Completed
00
Success
The transfer completed successfully.
Processing
03
Processing
The transfer has not reached a final outcome.
Failed
06
Failed
The transfer reached a final failed outcome.
An inquiry does not change the outcome These examples show alternative outcomes for existing transactions. A successful inquiry returns HTTP 200 and responseCode 2000300 even when the transaction is Processing or Failed.
Supply only one lookup reference. A successful response includes both references.
Inquiry rate limit
For the same authenticated client and the same transaction:
A maximum of 5 Check Status requests is allowed within a 30-second window.
The 6th and subsequent requests within that window return HTTP 429 with responseCode: "4290300".
The limit applies only to the affected transaction. Other transactions under the same authenticated client remain unaffected and have their own inquiry limits.
Looking up the same transaction using originalReferenceNo or originalPartnerReferenceNo shares the same limit.
Wait for the affected transaction’s rate-limit window to reset before trying again.
Timeouts and unresolved transactions
If your transfer submission returns no usable response, look up the transaction using originalPartnerReferenceNo. A timeout does not prove a failed transfer. Do not create a replacement while its outcome remains unresolved.
