Skip to main content
POST
Transfer Funds
Auth method: Signed (HMAC) — this endpoint requires the full set of signed headers: x-access-id, x-request-id, x-timestamp, and an HMAC-SHA256 authorization signature. See Authentication.
This endpoint handles both native coin transfers (ETH, TRX, BTC) and token transfers (USDT, USDC) in a single call. Pass chain and currency. The transfer is submitted on-chain asynchronously. When the transaction confirms, Tender fires a SUB_USER_WALLET_TRANSFER_CONFIRMED webhook to your server. Supported chains: ethereum, tron, bitcoin

Example

Headers

string
required
Base64-encoded HMAC-SHA256 signature of the request payload using the API secretExample: "5e73d044c44d733fcf819ad3409aaad..."
string
required
Current timestamp in ISO 8601 formatExample: "2025-03-15T09:45:53.000Z"
string
required
Unique identifier for the request (UUID v4)Example: "550e8400-e29b-41d4-a716-446655440000"
string
required
Your API access ID provided by TenderExample: "your-access-id-here"
string
required
Example: "application/json"

Body

string
required
The chain to use for the transfer. Supported values: ethereum, tron, bitcoin.Example: "ethereum"
string
required
The currency to transfer (e.g. ethereum, usdt, usdc, bitcoin). Must be supported on the specified chain.Example: "usdt"
string
required
The subwallet address to send from.Example: "0xabc123..."
string
required
The destination address.Example: "0x999fff..."
number | string
required
Amount to transfer in human-readable units (e.g. 0.01 ETH, 50 USDT).Example: 10.5
string
required
Your own reference for this transfer, for idempotency and reconciliation.Example: "payout-9921"
string
required
The address reference label of the sender address.Example: "slot-2"

Response

string
required
Example: "success"
string
required
Example: "success"
object
required

Error Responses

Authorizations

authorization
string
header
required

Signed (HMAC) authentication. Required headers: x-access-id, x-request-id (UUID v4), x-timestamp (ISO 8601), and authorization (Base64 HMAC-SHA256 signature of {timeStamp, requestId, accessId} using your access secret).

Headers

authorization
string
required
x-timestamp
string<date-time>
required
x-request-id
string<uuid>
required
x-access-id
string
required
Content-Type
string
required

Body

application/json
chain
enum<string>
required

Chain to use for the transfer.

Available options:
ethereum,
tron,
bitcoin
currency
string
required

Currency to transfer (e.g. ethereum, usdt, usdc, bitcoin). Must be supported on the specified chain.

sender
string
required
receiver
string
required
amount
required
merchant_reference
string
required
address_reference
string
required

Response

Transfer submitted