Card Issuer Program
List Card Customers
List all customers onboarded under your card issuer program
GET
Card customers are separate from WaaS customers. This endpoint returns all customer card records regardless of onboarding stage. For wallet sub-accounts (crypto deposits/withdrawals/transfers), see WaaS Customers.
string
required
Bearer token:
Bearer YOUR_ACCESS_TOKENinteger
Page number. Defaults to
1.integer
Results per page. Defaults to
20, max 100.string
Filter by onboarding status. One of:
otp_requested, otp_verified, kyc_initiated,
kyc_completed, card_created, active.boolean
Include balance fields for each customer’s account wallet. Defaults to
true. Pass false for faster responses when balances are not needed.Balance fields
Each customer object includes three balance fields (allnull when the wallet is not deployed or include_balances=false):
Balances are updated in real time whenever the card provider sends a balance change notification (e.g. after a card purchase). For wallets where no such notification has been received yet, a live on-chain query is made as a fallback — in that case
available_balance equals ledger_balance since pending information is not available from the chain alone.
Onboarding stages
Using customer identifiers
Theid field is the canonical identifier for a customer card record. You can also use yativo_card_id, external_customer_id, or email interchangeably in endpoints that accept a customer identifier (e.g. Fund Customer, Look Up Customer).
Customers with safe_deployed: false cannot be funded yet — the account wallet deploys automatically once KYC is approved.
