Skip to main content
When you combine inflight: true with multiple sources or multiple destinations, Blnk records each leg as a separate inflight transaction linked to a root split ID.

Record split inflight

From Blnk Core 0.15.0, inflight commit and void go through the queue by default.
To use the queue, set "skip_queue": false or omit skip_queue.
1

Record the split

Create a split transaction with "inflight": true:
2

Read the response

The response returns immediately with status: "QUEUED" for the split request itself. Blnk then queues each leg separately for processing.The worker then records each split leg as a separate INFLIGHT transaction. Every leg, and any later commit or void child, shares the same meta_data.QUEUED_PARENT_TRANSACTION.
201 Queued
3

Store the queued parent

Save meta_data.QUEUED_PARENT_TRANSACTION from the create response.Use this ID, not the per-leg IDs in destinations, when you commit, void, verify, or refund the split.
4

Commit or void the split

Call Update inflight with the queued parent ID. Blnk commits or voids every pending inflight leg in one request.
Update inflight
200 Queued
The worker creates an APPLIED or VOID child for each leg. Every child keeps the same meta_data.QUEUED_PARENT_TRANSACTION, so you can verify the whole split with webhooks or polling.

Error handling

Structured errors are available from Blnk Core 0.15.0 and later.
Split inflight commit and void use the same Update inflight endpoint as single inflight transactions. Blnk returns 400, 404, and 409 when the request ID or state is wrong.
404 Not Found
To resolve the error: Other commit and void errors match Commit & void inflight - Error handling. See API error codes for the full catalogue.

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.