Transaction Status Codes

STATUS‌‌‌‌‌   ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌    ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌ ‌‌STATUS_IDComment
CREATED1Transaction created
PROCESSING-DEBIT2Funds have been pulled from the sending node and have been sent to the receiving node. Transaction cannot be cancelled.
‌‌ ‌‌
(Ledger balance for sending node will update during this step.)
PROCESSING-CREDIT3Funds are being credited to the receiving node. Transaction cannot be cancelled.
SETTLED4 Transaction is assumed successfully settled.
For external transactions, such as ACH, there might be a small delay between this status and when funds are settled in the external account due to limitations of the payment rails.
Although the transaction is settled there is still exposure to ACH Returns and Chargebacks (Card Disputes).
Note: A check should have SETTLED status after it has been cashed.
‌‌ ‌‌
(Ledger balance for receiving node will update during this step.)
CANCELED5Transaction has been canceled
RETURNED6Transaction has returned
This is how ACH Returns, Card Chargebacks, Returned Wires, and similar are expressed in our system.
QUEUED-BY-SYNAPSE-1Transaction has been queued by Synapse

This could occur for a number of reasons including the user not having verified KYC, the transaction breaking the platform limits, the country of destination not being allowed, the user being a match on sanctions lists, and so on.

As an initial step please check the user has SEND-AND-RECEIVE permissions. Resolution will vary based on the nature of the issue. You can contact Synapse SupportSynapse Support - Help Center: | Customer Support Email : [email protected] | Customer Support Phone Number : +1 (415) 688-2943 | Customer Support Hours : Monday-Friday, 8:00am - 7:00pm PT for more information. Transaction can be cancelled.

Transactions can only be canceled in CREATED and QUEUED-BY-SYNAPSE statuses.

Updated 6 months ago

Transaction Status Codes

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.