OnLink
API reference

Deposit instructions for both legs

The KES rails you send us on (buy leg) and your USDT deposit address (sell leg). Every reference is an explicit field — the KES accountReference is the exact value to put in the M-PESA account-number field or the bank narration. Your USDT deposit address is permanent and shared across all your sell orders, so it cannot identify which order a deposit is for; attach the transaction hash with PATCH /v1/orders/{id}.

GET
/v1/funding

Authorization

partner-key
X-OnLink-Key<token>

In: header

Response Body

application/json

application/json

application/json

curl -X GET "https://example.com/v1/funding"
{  "kes": [    {      "rail": "mpesa_paybill",      "paybill": "444174",      "accountReference": "46013001348902",      "beneficiaryName": "ONLINK MASTER_PESASWAP",      "currency": "KES",      "instructions": "M-PESA > Lipa na M-PESA > Pay Bill > Business number 444174 > Account number 46013001348902. Then quote the paymentReference from your order in your own records — we match the payment by the reference we issued, not by the amount."    }  ],  "usdt": {    "chain": "tron",    "asset": "USDT",    "address": "TQiBwkXtUUNygiLdSwdeaZCKagwPsD1a7C",    "memo": null,    "instructions": "Send USDT on the Tron (TRC-20) network to this address. It is your permanent deposit address and is the same for every sell order, so we cannot tell your orders apart by it — after sending, attach the transaction hash with PATCH /v1/orders/{id}. No memo or tag is used."  }}