Fiat To Crypto

Operations for fiat to crypto conversions (on-ramp)

Request on-ramp quote

post

Generate a quote for converting fiat currency to cryptocurrency.

Authentication

All API requests to Orda require HMAC signatures using your project's client ID and client secret. The signature is a HMAC-SHA256 hash of the request body, using your Client Secret as the key.

Required Headers

Header
Description

x-client-id

Your project's client ID

x-signature

HMAC-SHA256 signature derived from your client secret

Content-Type

application/json for this request


Intent Specification: The quote request uses an intent object to specify the amount calculation method:

  • fromAmount: Specify exact fiat amount to spend

  • toAmount: Specify exact crypto amount to receive

  • usd: Specify USD value for conversion

Important Notes:

  • Currently supports BRL to BRZ conversions

  • Provide EITHER recipientId OR settlementDetails (not both)

  • If using recipientId, recipient must have crypto settlement details configured

  • If using settlementDetails, provide destination chain, token, and address inline

  • Quote includes PIX payment instructions for BRL

  • Quotes expire after 5-10 minutes (check expiresAt field)

  • Exchange rates include all fees

Authorizations
x-client-idstringRequired

Your project client ID from orda dashboard

x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

x-timestampstringRequired

Unix timestamp in milliseconds for replay protection (recommended)

Header parameters
x-client-idstringRequired

Your project client ID from orda dashboard

Default: prj_abc123def456ghi789Example: prj_abc123def456ghi789
x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

Default: a1b2c3d4e5f6789abc123def456ghi789abc123def456Example: a1b2c3d4e5f6789abc123def456ghi789abc123def456
x-timestampstringOptional

Unix timestamp in milliseconds for replay protection (recommended)

Default: 1704067200000Example: 1704067200000
Body
fromCurrencystring · enumRequired

Source fiat currency code (currently only "BRL" supported)

Example: BRLPossible values:
recipientIdstringOptional

UUID of the recipient to receive cryptocurrency (provide either this OR settlementDetails)

Example: 123e4567-e89b-12d3-a456-426614174000
Responses
chevron-right
200

On-ramp quote generated successfully

application/json
post
/onramp/quote

Get on-ramp status

get

Check the status of a fiat-to-crypto transaction.

Authentication

All API requests to Orda require HMAC signatures using your project's client ID and client secret. The signature is a HMAC-SHA256 hash of the request body (empty string for GET requests), using your Client Secret as the key.

Required Headers

Header
Description

x-client-id

Your project's client ID

x-signature

HMAC-SHA256 signature derived from your client secret


Status Values:

  • In_progress: Payment pending or being processed

  • Completed: Cryptocurrency successfully delivered

  • Failed: Payment failed or was rejected

Deposit Status Values:

  • awaiting: Waiting for fiat deposit

  • received: Deposit received, processing

  • confirmed: Deposit confirmed, converting to crypto

  • completed: Crypto sent to wallet

Authorizations
x-client-idstringRequired

Your project client ID from orda dashboard

x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

x-timestampstringRequired

Unix timestamp in milliseconds for replay protection (recommended)

Query parameters
transactionIdstringRequired

UUID of the transaction to check

Example: 550e8400-e29b-41d4-a716-446655440000
Header parameters
x-client-idstringRequired

Your project client ID from orda dashboard

Default: prj_abc123def456ghi789Example: prj_abc123def456ghi789
x-signaturestringRequired

HMAC-SHA256 signature of canonical request body using your client secret

Default: a1b2c3d4e5f6789abc123def456ghi789abc123def456Example: a1b2c3d4e5f6789abc123def456ghi789abc123def456
x-timestampstringOptional

Unix timestamp in milliseconds for replay protection (recommended)

Default: 1704067200000Example: 1704067200000
Responses
chevron-right
200

Transaction status retrieved successfully

application/json
get
/onramp/status

Last updated