Skip to main content
This guide is for Blnk versions 0.10.8 and older. For version 0.11.0 and newer, see the updated documentation.
You can manage insufficient funds scenarios in two ways: through automatic rejection handling when transactions are attempted with insufficient balance, and through proactive balance checking before initiating transactions.

​
1. Automatic rejection

When a transaction is posted where the source balance has insufficient funds, Bink automatically handles this scenario to maintain ledger integrity. Blnk checks only the balance amount to determine if it is sufficient for the transaction amount being processed. If funds are insufficient, Blnk:
  1. Rejects the transaction.
  2. Records this rejection in your ledger using the same state tracking mechanism (i.e. QUEUED → REJECTED). Learn more about transaction lifecycle.
  3. Sends a webhook notification to inform your system of the state change and new ledger record.
You can also preemptively track the transaction status (via reference or parent_transaction) to know if the transaction was successful or rejected.

​
2. Proactive balance verification

Instead of waiting for a transaction.rejected webhook, you can implement a preemptive available balance check in your workflow. Here’s how: First, query the balance of the sender using:
cURL
curl -X GET 'http://YOUR_BLNK_INSTANCE_URL/balances/{balance_id}?with_queued=true' \
  -H 'Authorization: Bearer YOUR_API_KEY'
Next, calculate your available balance: 
available_balance = balance - queued_debit_balance
  • If the available balance is sufficient, proceed with posting your transaction.
  • If the available balance is insufficient, you can gracefully handle this scenario in your application by notifying the customer immediately, avoiding the need for webhook handling.

Queued balances

Learn how queued balances work

​
3. Insufficient funds for inflight transactions

Starting from version 0.11.0, Blnk now includes inflight balances in the insufficient funds check. The manual checks described below are only necessary for versions 0.10.8 and older.
When working with inflight transactions, your system must always consider both the actual balance and any pending inflight amounts. To do this, compute an available_balance for your customers indicating the amount available for them to spend on new transactions: 
available_balance = balance - inflight_debit_balance - queued_debit_balance
To check for insufficient funds before initiating an inflight transaction:
  1. Query the source balance, and compute the available_balance: 
    GET /balances/{balance_id}?with_queued=true
  2. Compare the new transaction amount against available_balance:
    • If amount ≤ available_balance: Proceed with transaction.
    • If amount > available_balance: Handle gracefully in your application by notifying the customer of insufficient funds.
With this approach:
  • You ensure that pending inflight transactions will always be committed when they need to.
  • Customers are prevented from spending funds that are waiting to be deducted from their balance.

​
Need help?

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.
Tip: Connect to Blnk Cloud to see your Core data.You can view your transactions, manage identities, create custom reports, invite other team members to collaborate, and perform operations on your Core — all in one dashboard.Check out Blnk Cloud →