Check Disbursement Status

Brick sends disbursement status updates through callback notifications, but manual status checks are useful when a callback is delayed, your server is temporarily unavailable, or the original API response leaves the transaction state unclear.

When to Check Status Manually

Processing for Too Long

If a disbursement remains in a processing state for more than expected, query the latest status before taking further action.

API Error During Creation

If the create-disbursement request returns a server error, do not immediately retry the payout. First, check the transaction by transaction ID or reference ID to avoid duplicate payouts.

Missed Callback

If your callback endpoint was unavailable or misconfigured, use the status API to reconcile your internal records.

Status Check Options

Recommended Flow

1. Store the transaction_id returned by Brick and your own reference_id when creating the disbursement.
2. If the callback is missing or the transaction state is unclear, query the status API.
3. Retry a disbursement only when the queried status confirms that the original transaction failed or was not created.