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.
Overview
The Yativo Card Issuer Program lets businesses issue virtual and physical payment cards to their own customers under their platform. As an issuer you manage the full card lifecycle — from customer onboarding to card creation, balance funding, and transaction monitoring — through a single API. Typical use cases:- Fintech apps offering spending cards to users
- Corporate expense management platforms
- Digital banking services for underserved markets
- Wallets that want to add a card spending layer
Access to the Card Issuer Program is by invitation only. Contact your Yativo account manager or support@yativo.com to request access. The program section will not appear in your dashboard until your account manager enables it for your account.
How It Works
Your account manager grants eligibility
Yativo’s team reviews your use case and enables the Card Issuer Program on your account. Nothing is visible in your dashboard until this step is complete.
You submit an application
Once eligible, the Card Issuer section appears in your dashboard. Choose your funding structure (
master_wallet or non_master) and an optional IBAN add-on, then submit.Yativo approves your program
Our compliance team reviews and approves the application, typically within 2–5 business days. On approval, your settlement wallets are auto-provisioned.
Funding Structures
Choose your funding structure at application time. It cannot be changed after approval.| Structure | Source Chain | Best For |
|---|---|---|
master_wallet | Solana (SOL) or XDC | You hold the source funds and push them to customer cards on demand |
non_master | Per-customer | Each customer deposits to their own collateral wallet — you do not hold a shared balance |
Apply for the Program
Once your account manager has granted eligibility, submit your application.| Field | Required | Description |
|---|---|---|
funding_structure | Yes | master_wallet or non_master |
iban_enabled | No | Set to true to enable EUR IBAN issuance. Requires additional regulatory review. Default: false |
Response
Check Program Status
Response (approved, master_wallet)
Master Wallet & Balances
Master wallet issuers (funding_structure: master_wallet) have two types of wallets:
Source wallets (SOL and/or XDC)
These are the wallets you deposit USDC into. SOL deposits are bridged automatically to your settlement wallet. XDC deposits are bridged manually on your own schedule (XDC deposits accrue yield while held).| Chain | Token deposited | Bridge | Time |
|---|---|---|---|
| SOL | USDC_SOL | Automatic | ~2–5 min |
| XDC | USDC_XDC | Manual | ~20 min |
Settlement wallets
These are auto-provisioned on approval. All three currency balances share the same underlying on-chain address.| Balance | Funded by | Used for |
|---|---|---|
| USD | USDC bridge from SOL/XDC | Funding cards in USD regions |
| EUR | Swap from USD | Funding cards in EUR regions |
| GBP | Swap from USD | Funding cards in GBP regions |
All three balances are managed internally by Yativo. To move from USD balance to EUR balance, use the swap endpoint below.
Get master wallet balances
Response
xdc is null if XDC is not enabled for your program.
Get funding deposit addresses
non_master programs, pass ?customer_id=... to get the per-customer address.
Swap Between Currency Balances
Swap USD ↔ EUR ↔ GBP within your master wallet balances.| Field | Required | Description |
|---|---|---|
from_token | Yes | USDC, EUR, or GBP |
to_token | Yes | USDC, EUR, or GBP (must differ from from_token) |
amount | Yes | Amount to sell, in the from_token currency |
Response
Fund a Customer’s Card
Transfer from your master wallet to a customer’s card wallet. The destination currency is automatically detected from the customer’s card region (e.g. UK customers receive GBP, EU customers receive EUR).| Field | Required | Description |
|---|---|---|
customer_id | One of | Customer’s Yativo customer ID |
card_id | One of | Card’s unique ID |
external_id | One of | Your own external reference |
email | One of | Customer’s email address |
amount | Yes | Amount to send (interpretation depends on pricing_mode) |
source_chain | Yes | SOL or XDC — which master wallet to send from |
pricing_mode | No | send_x (default) or receive_x — see below |
destination_token | No | Override the auto-detected destination token. Must match the customer’s card region currency or an error is returned |
Pricing modes
| Mode | You specify | Customer receives |
|---|---|---|
send_x | The amount you send from your master wallet | Less than amount (bridge fees deducted) |
receive_x | The amount the customer should receive | More than amount is sent from your master wallet (you absorb fees) |
The currency mismatch check is enforced at the API level. For example, if a customer’s card is in a EUR region, you cannot fund them with a USD destination — the API returns
TOKEN_MISMATCH and tells you the required currency. Swap your USD balance to EUR first, then fund.Response
Look Up a Customer
Find a customer by any of their identifiers. The underlying wallet address is never returned.customer_id, card_id, external_id, or email.
Response
List & Manage Customers
Deposit History (XDC)
XDC deposits are tracked individually so you can choose when to bridge each one.awaiting_manual status can be manually triggered. SOL deposits are bridged automatically.
Funding History
Card Reissue
When card reissue is enabled for your program (admin-toggled), your customers can request a card reissue from the card management screen. This feature is off by default and is enabled per-program by Yativo’s compliance team. Check whether it’s enabled:Rate Limits & Program Limits
| Resource | Default | Adjustable |
|---|---|---|
| Max customer accounts | 1,000 | Yes — contact your account manager |
| Daily funding cap | $50,000 | Yes — admin-configurable per program |
| Monthly funding cap | $500,000 | Yes — admin-configurable per program |
GET /card-issuer/status under limits.
Webhooks
Subscribe to issuer events using the Webhooks API:| Event | Description |
|---|---|
issuer.program.approved | Your program application was approved |
issuer.customer.kyc_approved | A customer’s KYC was approved |
issuer.customer.card_created | A card was issued for a customer |
issuer.funding.completed | A card funding bridge settled successfully |
issuer.funding.failed | A card funding attempt failed |

