Move money from a single source to multiple destinations.
Available in version 0.6.0 and later.
Blnk allows you to move money from a single source to multiple destinations in one transaction. This provides enhanced flexibility for complex money flows and makes tracking and reconciliation easier.
One sender, many recipients is pretty common: a payroll run, a marketplace split, or a refund that returns funds to several customer wallets at once.For example, Sarah is sending USD 30,000out of her balance. She routes 20% to Alice, a fixed $10,000 to Bob, and assigns "left" to Charlie so whatever remains after the first two legs goes to Charlie automatically.Money movement would look like this:Explore the map yourself here
Balance ID
Amount
Alice
bln_f2073f6b-905a-4e3e-b5a2-8d1b3dc2fb7f
20% (USD 6,000)
Bob
bln_64c50fb5-32d5-4f78-9f4a-e8b01aaf025d
USD 10,000
Charlie
bln_7d98dfe9-5c3e-4c9b-b96a-65f6d9f7b89b
Remaining amount (USD 14,000)
Sarah (Sender)
bln_92e4b9b6-0b85-4ef4-87a2-682c31500d38
Total: USD 30,000
From a product perspective, that usually maps to one user-facing action (“Send $30k”) while your ledger still exposes each recipient line for reporting, disputes, or partial reversals.
When sending to multiple destinations, you can only send from one source.
Array of destination objects with identifier and distribution fields
Yes
array
destinations.identifier
Balance ID of the destination account
Yes
string
destinations.distribution
Amount to send to this destination (specific amount, percentage, or “left”)
Yes
string
atomic
When true, all destination legs succeed or the entire split fails. Default: false.
No
boolean
meta_data
Custom transaction data
No
object
When sending to multiple destinations, do not include the destination field in your payload. Use the destinations array to group the participating balances in your payload.
By default, Blnk processes a multiple destinations split with atomic: false. Each destination leg is evaluated independently. Legs that pass validation are marked APPLIED, while legs that fail are marked REJECTED. This can result in a partial split, where some destinations are credited and others are not.Set atomic: true to enable all-or-nothing processing. All destination legs must succeed for the split to be completed. If any leg fails, Blnk rolls back any previously APPLIED or INFLIGHT legs, reversing the credits so the split is fully cancelled and no partial state remains on the ledger.
Use atomic: true when partial results are not acceptable. For example, when sending a split payment, every destination must succeed for the transaction to go through.
When you create a multiple destinations transaction, Blnk creates separate transaction records for each destination.Blnk returns a response containing:
A main transaction ID for the overall split transaction. If inflight: true, it can be used to commit or void all transactions at once.
A destinations array with individual transaction IDs for each destination.
This will return all individual transactions that were created as part of the multiple destinations transaction, allowing you to track and manage the complete set of related transactions.
When a transaction uses precise_amount, use precise_distribution in place of distribution only for destinations that specify an exact value.For example:
Blnk automatically generates unique references for each transaction record by appending a counter to your original reference (starting from 1).Example: If your reference is ref_001adcfgf, the generated references will be:
ref_001adcfgf_1 (first destination)
ref_001adcfgf_2 (second destination)
ref_001adcfgf_3 (third destination)
This ensures traceability while maintaining connection to the original transaction.Also see:
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.
