For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
GuidesAPI ReferenceSDKs
GuidesAPI ReferenceSDKs
  • Get Started
    • Overview and Solutions
    • Choose an Integration
    • Quickstart
    • Branding Guidelines
    • Get Support
  • Accept Payments
    • Instant Payments
    • Trustly Pay
    • Recurring Payments
    • Scan and Pay
    • Remember Me
    • Payment Integration Checklist
  • Send Money
    • Send Payouts Using Online Banking
    • Send Payouts Using Account Information
    • International Transfers
  • Retrieve Data
    • Verify Accounts Using Online Banking
    • Verify Accounts Using Micro-Deposits
    • Retrieve Bank and User Information
    • Tokenize Bank Information
    • Trustly ID
    • Insights Data
  • Core Concepts
    • Key Concepts
    • The Establish Data Object
    • Transactions and Transaction IDs
    • Tokens and Account Security
    • Redirect URLs and Return Flow
    • Webhooks and Events
    • Content Strings
  • API Fundamentals
    • Authentication and OAuth
    • Secure Requests and Signature Validation
    • Idempotency
    • Testing
    • Status codes and type definitions
  • Manage Your Integration
    • Go-Live Checklist
    • Merchant Portal
    • Reports and Reconciliation
    • Refresh Bank Authorization
    • Override Risk Declines
    • VIP Tiers
    • Financial Institution Status
Dashboard
Products
PaymentsDataPayouts
Company
AboutCareersContact Sales

Terms of Use | Privacy Policy | © 2026 Trustly, Inc.

Developer-friendly docs for your API
GitHub|Contact Support|Business Help Center|Merchant Portal
Terms of Use|Privacy Policy|© 2026 Trustly, Inc.
Developer-friendly docs for your API
LogoLogo
North AmericaEurope
North AmericaEurope
On this page
  • Prerequisites
  • Integration workflow
  • Create a bank authorization
  • Required parameters
  • Example request
  • Example response
  • Send funds (deposit)
  • Example request
  • Handle the response
  • Event notifications
  • Testing
Send Money

Send payouts using account information

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Send payouts using online banking

Next

Transfer funds internationally

Built with

You can use the Disbursements API to send funds to a customer using their Account Number and Routing Number. This is a manual entry workflow where you collect the banking details in your own UI and pass them to Trustly with the API.

When you handle raw banking data (Account and Routing numbers), you are responsible for maintaining Payment Card Industry Data Security Standard (PCI DSS) and National Automated Clearing House Association (NACHA) compliance.

To avoid handling sensitive data, Trustly recommends using Send payouts using online banking.

Prerequisites

  • Sandbox credentials: You need your accessId and accessKey.
  • Legal agreement: Your contract must explicitly allow the use of the Disbursement payment type.

Integration workflow

The following diagram illustrates the API-only workflow for Disbursements. Unlike Payouts, there is no Lightbox interaction.

The following table details each step of the Disbursement workflow.

StepParticipantActionDescription
1MerchantCalls EstablishYou send the customer’s account and routing number to Trustly to create a token.
2TrustlyReturns IDTrustly validates the format and returns a transactionId.
3MerchantCalls DepositYou initiate the transfer using the transactionId and the specific amount.
4BankCreditsThe banking network processes the credit to the customer’s account.
5TrustlyNotifiesAsync: Trustly sends a webhook to your backend confirming the funds have settled.

Create a bank authorization

Use the Establish API to tokenize the customer’s banking information. This creates a transaction record you can reference for the deposit.

Important: You must append createTransaction=true to the endpoint URL for this request to work correctly.

Endpoint: POST /establish

Required parameters

ParameterDescription
paymentTypeMust be set to Disbursement.
account.routingNumberThe 9-digit American Bankers Association (ABA) routing number collected from the customer.
account.accountNumberThe customer’s bank account number.
merchantReferenceYour unique identifier for this customer or session.
amountThe maximum limit for future transactions processed with this authorization. Set to 0.00 to indicate no upper bound.
currencyThe 3-letter ISO currency code. Currently, only USD and CAD are supported.

Example request

$curl -X POST "[https://sandbox.trustly.one/api/v1/establish?createTransaction=true](https://sandbox.trustly.one/api/v1/establish?createTransaction=true)" \
>  -u "YOUR_ACCESS_ID:YOUR_ACCESS_KEY" \
>  -H "Content-Type: application/json" \
>  -d '{
>  "merchantId": "YOUR_MERCHANT_ID",
>  "merchantReference": "user_123_ref",
>  "paymentType": "Disbursement",
>  "currency": "USD",
>  "amount": "0.00", 
>  "account": {
>    "routingNumber": "124003116",
>    "accountNumber": "123456576",
>    "type": 1
>  },
>  "returnUrl": "[https://not-used.com](https://not-used.com)",
>  "cancelUrl": "[https://not-used.com](https://not-used.com)"
>}'

returnUrl and cancelUrl are required fields in the schema but are not used in this flow because there is no user redirect. You can pass placeholder URLs.

The API returns a Transaction object. You must store the transactionId from this response, as it is required to initiate the subsequent Deposit call.

Example response

Store the transactionId returned in the response.

1{
2  "transaction": {
3    "transactionId": "1002613662",
4    "status": 0,
5    "statusMessage": "Authorized",
6    "payment": {
7      "paymentType": 4,
8      "account": {
9        "accountNumber": "123456576",
10        "routingNumber": "124003116"
11      }
12    }
13  }
14}

Send funds (deposit)

Once you have the transactionId, use the Deposit API to initiate the transfer of funds.

Endpoint: POST /transactions/{transactionId}/deposit

Example request

$curl -X POST [https://sandbox.trustly.one/api/v1/transactions/1002613662/deposit](https://sandbox.trustly.one/api/v1/transactions/1002613662/deposit) \
>  -u "YOUR_ACCESS_ID:YOUR_ACCESS_KEY" \
>  -H "Content-Type: application/json" \
>  -d '{
>    "amount": "25.00",
>    "merchantReference": "payout_001"
>  }'

Handle the response

The following table outlines the response statuses returned by the Deposit API and the recommended actions for each status.

StatusDescriptionAction
AUTHORIZEDThe payout request is accepted.Deduct the funds from the customer’s balance in your system and wait for the Completed webhook.
DECLINEDThe request failed.Do not deduct funds. Notify the customer.

Event notifications

Disbursements are asynchronous. You must implement a webhook listener to determine when the money actually arrives. See Handle webhooks.

The following are the statuses that can be returned:

  • Processed: The file has been sent to the Federal Reserve (ACH).
  • Completed: The funds have settled in the customer’s account (typically T+1 or T+2).
  • Reversed: The transaction failed after processing. For example, the account is closed.

Testing

You can use the following test data to simulate a successful Disbursement authorization in the Sandbox environment.

FieldValueResult
Routing Number124003116Valid ABA Routing Number
Account Number123456575Simulates a valid account

For a complete list of test scenarios, including error triggers and other account types, see Testing.