Initiate On-ramp
On-ramp
Initiate On-ramp
Create an on-ramp request using a valid quote
POST
Initiate On-ramp
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.Headers
string
required
Base64-encoded HMAC-SHA256 signature of the request payload using your API secretExample:
"5e73d044c44d733fcf819ad3409aaa..."string
required
Example:
"2025-03-15T09:45:53.000Z"string
required
Example:
"550e8400-e29b-41d4-a716-446655440000"string
required
Example:
"your-access-id-here"string
required
Example:
"application/json"Body
string
required
The
quoteId returned by Get On-ramp Quote. Must not be
expired or already used. Each quote is single-use.Example: "b7f2a1c3-9d4e-4b2f-a8c0-1e2d3f4a5b6c"string
required
Wallet address that will receive the crypto. Must be valid for the chain specified in the quote.Example:
"TRDFGhjkytywooiueonuoo"object
required
Details of the customer making the fiat payment
object
Optional key-value pairs for your own reference. Values must be strings or numbers.Example:
{ "orderId": "ORD-9821", "userId": "usr_42" }Error cases
Response
string
required
Example:
"success"string
required
Example:
"Onramp initiated"object
required
Authorizations
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
Base64-encoded HMAC-SHA256 signature of the request payload using the API secret
Current timestamp in ISO 8601 format
Unique identifier for the request (UUID v4)
Your API access ID provided by Tender
Body
application/json