Getting Started - Disbursement
Send Money is Brick's disbursement product for businesses that need to send funds to destination bank accounts, virtual accounts, or supported Ewallet destinations. You can use Send Money from the Brick Dashboard for operational workflows or integrate it through APIs for automated payout systems.
Use Send Money when you need to pay employees, vendors, partners, customers, sellers, creators, suppliers, or other beneficiaries from your Brick balance. Brick provides disbursement methods, status tracking, callbacks, account validation, and transfer proof documents to help your team operate and reconcile money-out workflows.
What You Can Do With Send Money
- Create single transfers from the Brick Dashboard.
- Upload and process bulk transfers from the Brick Dashboard.
- Create disbursements through API.
- Validate recipient bank accounts before creating payouts.
- Track disbursement status by Brick transaction ID or your own reference ID.
- Receive callback notifications when transaction status changes.
- Download transfer proof documents for records and customer support.
Pricing
Disbursement via API or Dashboard is an on-demand service—you only pay per successful transaction.
You simply top up your Brick balance, and each disbursement deducts:
- The transfer amount
- A transfer fee
- Applicable VAT (PPn)
For full details, visit our Pricing Page.
If you have custom volume, operational, or pricing requirements, contact the Brick team for the commercial setup that applies to your account.
Have a large volume of payments? Talk to us for custom pricing and support.
Coverage
Brick disbursement coverage depends on the destination type, disbursement method, and supported bank or payment network. Review the coverage list before enabling a destination in production.
View the full list of supported payment destinations in the Disbursement Destination List.
📘 Note on Virtual Account Coverage
Some Virtual Account (VA) channels are sensitive to expiry settings and the looping mechanism used by the issuing bank:
- Close-loop VAs: These can only be recognized within the host bank’s own ecosystem (e.g., via internal transfers or channels).
- Open-loop VAs: These are accessible from external banks and can receive funds via interbank transfers.
In many cases—especially with e-commerce platforms—VAs are issued as close-loop, which limits their interoperability and often results in lower success rates, especially when payments are made from outside the issuing bank.
Maintenance Logic
In the world of financial technology, scheduled or unscheduled maintenance is a common operational event—especially from downstream providers such as banks and payment networks.
To ensure reliability and minimize disruptions, Brick applies the following maintenance logic to disbursement transactions:
If a destination (e.g., a bank or Ewallet) is under maintenance for 6 hours or less, we will:
- Hold the transaction temporarily
- Automatically resume processing once the destination becomes available
This approach ensures transaction integrity while avoiding premature failure or retries that could lead to duplication.
⏳ During this time, the transaction status may appear as PROCESSING or delayed in completion.
If you have concerns about specific transactions or need assistance during a maintenance window, please don't hesitate to contact our Operational Support Team for real-time updates.
What to read next
You must set up at least one Sender Detail before initiating any disbursement transaction, including single and bulk transfers. Without it, disbursement features will be disabled. Read more in Sender Detail.
Want to use disbursement via Dashboard? See the Dashboard Guide.
Prefer to integrate disbursement via API? See the API Guide