Skip to main content
POST
/
v1
/
card-issuer
/
fund-customer
curl -X POST 'https://crypto-api.yativo.com/api/v1/card-issuer/fund-customer' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "fernando@truther.io",
    "amount": 10,
    "source_chain": "SOL",
    "pricing_mode": "receive_x"
  }'

{
  "success": true,
  "message": "Customer funded successfully",
  "data": {
    "transfer_id": "bridge_1778501099297_2ea87af00de1",
    "status": "completed",
    "source": {
      "chain": "SOL",
      "amount": 10
    },
    "destination": {
      "token": "USD"
    },
    "pricing_mode": "receive_x",
    "estimated_amount": "10.000000",
    "estimated_time": "immediate"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.yativo.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Authorization
string
required
Bearer token: Bearer YOUR_ACCESS_TOKEN
Supply exactly one customer identifier. The customer must have completed onboarding (KYC approved, wallet ready) before funding.
​
customer_id
string
The customer_id from the List Customers or Look Up Customer response. You may supply any one identifier: customer_id, card_id, external_id, or email.
​
card_id
string
Card ID from card creation.
​
external_id
string
Your own reference (external_customer_id) set at onboarding.
​
email
string
Customer email address.
​
amount
number
required
Amount in USD. How this is interpreted depends on pricing_mode — see below. Minimum 5.
​
source_chain
string
required
Your master wallet chain to use as the funding source. SOL or XDC.
​
pricing_mode
string
Controls whether amount is what you send or what the customer receives.
  • send_x (default) — Your master wallet is debited exactly amount. Any applicable fees are deducted before the customer’s card is credited.
  • receive_x — The customer’s card is credited exactly amount. The system works backwards through the fee schedule to calculate how much your master wallet must supply. Use this when the customer is owed an exact payout.
Example — funding $200:
pricing_modeYou sendCustomer receives
send_x$200~$198 (after fees)
receive_x~$202 (fees added)$200 exactly
​
destination_token
string
Optional target currency (USD, EUR, GBP). Defaults to the customer’s card currency. Must match — mismatches return an error with the correct required currency.
curl -X POST 'https://crypto-api.yativo.com/api/v1/card-issuer/fund-customer' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "fernando@truther.io",
    "amount": 10,
    "source_chain": "SOL",
    "pricing_mode": "receive_x"
  }'

{
  "success": true,
  "message": "Customer funded successfully",
  "data": {
    "transfer_id": "bridge_1778501099297_2ea87af00de1",
    "status": "completed",
    "source": {
      "chain": "SOL",
      "amount": 10
    },
    "destination": {
      "token": "USD"
    },
    "pricing_mode": "receive_x",
    "estimated_amount": "10.000000",
    "estimated_time": "immediate"
  }
}
When estimated_time is "immediate" the transfer is already settled — no polling needed. When estimated_time is "2–5 minutes", save the transfer_id and poll Get Transfer Status until status is completed.