Learn about the different statuses of a transaction.
Every Bink transaction moves through a series of states that reflect its processing status. Understanding these states helps you track your transactions effectively and handle them appropriately in your application.
When you first create a transaction, it enters a QUEUED
state. This indicates your transaction has been received and is waiting to be processed by Bink’s concurrency-controlled queue system.
The APPLIED
state indicates a successful transaction. When you see this state, it means:
When you enable inflight for a transaction in your request, it moves from QUEUED
to INFLIGHT
. In this state, the transaction is on hold until you take further action.
From the INFLIGHT
state, your transaction can move to one of three possible resolution states:
When you send a commit command for an inflight transaction, Bink creates a new record with the APPLIED status, indicating the transaction has been successfully processed and the balances have been updated.
If you send a void command, Bink creates a new record with the VOID
status, indicating the transaction was not completed and the inflight balances have been reset.
The REJECTED
state occurs when a transaction is not processed due to reasons like insufficient funds in the source balance. When this happens:
Once a transaction reaches the REJECTED
state, it is final. To retry the transaction, you would need to create a new one. Learn more: Handling insufficient funds with Blnk.
All transactions in Blnk are immutable. Once a transaction has been applied, committed or voided, you cannot roll back the status to its previous status.
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.
To ask questions or discuss issues, please contact us or join our Discord community.