Disbursement

post

https://sandbox.api.of.ayoconnect.id/it/api/v2.0/transfer-interbank

This API is used to initiate a disbursement.

HTTP 200 means the request has been successfully received. - Disbursement is processed asynchronously, so the final transaction result may not be available immediately. - Do not mark the transaction as failed when a 5XX18XX response code is received. - Wait for the callback for up to 30 minutes. If no callback is received, call the Status Inquiry API.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

beneficiaryBankCode

string

required

Unique identifier used to identify the beneficiary's bank.

beneficiaryAccountNo

string

required

Beneficiary account number.

For e-wallet transfers (GoPay, OVO, ShopeePay), use the customer’s registered phone number in the e-wallet, with prefix 08 (example: 08123456789).

beneficiaryAccountName

string

required

Name of the beneficiary account returned upon successful account validation.

partnerReferenceNo

string

required

Unique 32-character alphanumeric string generated by the merchant. Used as the transaction identifier and must be unique for each transaction.

sourceAccountNo

string

required

Merchant unique identifier (merchant code) registered with Ayoconnect.

transactionDate

date-time

required

Date and time of the disbursement. Must follow ISO 8601/RFC 3339 format (example: 2026-02-14T13:37:10+07:00).

customerReference

string

required

Unique identifier obtained from a successful Account Inquiry. This value is required in the Disbursement request.

amount

object

required

Information about the amount to be disbursed to the beneficiary.

additionalInfo

object

Additional metadata or remarks included in the request. Supports up to 4 fields: notes, additionalInfo1, additionalInfo2, additionalInfo3.

Headers

Authorization

string

required

length between 35 and 35

Authorization header. Only 'Bearer' authentication is supported.

Authorization-Customer

string

required

Represents the customer access token (accessToken field) obtained from the B2B2C Token API. The value must start with "Bearer " followed by the B2B2C Token.

X-EXTERNAL-ID

string

required

length between 32 and 32

Unique identifier (32 alphanumeric characters) to identify the request. It must be unique per request and can't be reused in subsequent requests.

If the same value is used in another request, it will be considered as a duplicated request, and consequently rejected.

X-PARTNER-ID

string

required

length between 6 and 6

Unique identifier (6 alphanumeric characters) to identify the particular merchant. It must be unique per merchant.

X-LATITUDE

string

required

Geographical coordinates of the end customer location

X-LONGITUDE

string

required

Geographical coordinates of the end customer location.

X-TIMESTAMP

string

required

length between 24 and 27

Client's current local time in yyyy-MM-ddTHH:mm:ss.SSSTZD format.

X-SIGNATURE

string

required

Integrity checking. Asymmetric Signature: SHA256withRSA(Private_Key, stringToSign)

stringToSign = client_ID + "|" + X-TIMESTAMP

X-IP-ADDRESS

string

required

Public IP Address of the end customer.

CHANNEL-ID

string

required

length between 5 and 5

Numeric ID that shows which client or application sent the request. It is used for tracking and reporting.

Responses

Callback

200Request successfully received

401Invalid Token