Transfer funds from a person's external checking or savings account to a business to purchase goods or services.



Set Up Enterprise Account In Sandbox



You must be configured for this use case, or your transfer request will result in an error. Contact your Orum representative for more details if you plan to incorporate this use case into your product.


Disbursements offer a convenient way for businesses to send funds directly to a person’s bank account for purposes other than a typical platform payout. Common examples of disbursements include:

  • Insurance claims: Enable your insurance company to make seamless payments to beneficiaries who have filed a claim
  • Legal settlement: Enable your company to make payments to beneficial parties in legal settlements where funds are owed
  • Rewards programs: Enable your rewards platform to quickly distribute rewards to eligible customers

Transfer Request Requirements

In a disbursement transfer, persons can remain in the created state.

Use CaseSourceDestination
DisbursementEmptyPerson (Created)
- Customer reference ID
- First name
- Last name

External Account (Verified)
- Account reference ID
- Customer reference ID
- Customer resource type
- Account type
- Account number
- Routing number
- Account holder name


For the following steps, we’ll assume you’re building an insurance company and want to enable seamless claims disbursements to your beneficiaries.

  • Insurance Company wants to pay out beneficiaries for insurance claims
  • Beneficiary wants to be paid seamlessly after filing an insurance claim (person)

1. Authenticate to Deliver

Use the /authenticate and /refresh endpoints.

2. Create a beneficiary and their associated bank account

Use the POST /persons endpoint to create the customer and the POST /external/accounts endpoint to create the external account. The external account can be created as soon as the consumer is created.

To send payments to claim beneficiaries only a first and last name are required during creation. Additionally, disbursement transfers do not require KYC verification or continuous watchlist monitoring. This means that the beneficiary’s status will remain in the created state.

     "customer_reference_id": "beneficiary_1",
     "first_name": "Francis",
     "last_name": "Smith"
     "account_reference_id": "beneficiary_account_1",
     "customer_reference_id": "beneficiary_1",
     "customer_resource_type": "person",
     "account_type": "checking",
     "account_number": "987654321",
     "routing_number": "900000009",
     "account_holder_name": "Francis Smith"

3. Send a disbursements transfer

Use the POST /transfers endpoint to create the transfer. When initiating a disbursement, ensure that the source object is left empty and that the beneficiary from Step 2 is in the destination object. For this type of transfer, you do not need to specify a funding source. By passing only the destination object, Deliver understands that the transfer is a disbursement and will pull funds from the FBO balance.

  • The beneficiary only needs to be in a created state
  • The source and destination bank accounts must be in a verified state
     "currency": "USD",
     "destination": {
          "account_reference_id": "beneficiary_account_1",
          "customer_reference_id": "beneficiary_account_1"
     "transfer_reference_id": "transfer_1",
     "amount": 100000,
     "speed": "asap"

Send a disbursement transfer diagram


Disbursements workflow