Issue cards upstream using members' L1 profiles, fund them from asset balances, and enable worldwide spending.
Card Issuance Overview
A Card's Lifecycle
产品/BIN ─► 申请 ─► 开卡 ─► 充值到卡 ─► 消费
│
├─► 冻结 / 解冻
├─► 补换卡 / 挂失
└─► 销卡（先清空卡内资金）
Physical cards add two stages: binding and activation.
Three Features Specific to Card Issuance
1. Card Credentials: Our Responsibility Covers Our Servers; Verified Ownership Permits Plaintext Access
We store only the first four and last four digits. Lists and details always show masked numbers. After verifying that a card belongs to your merchant and the specified member, we return its card number, CVV, and expiry in plaintext. PIN is excluded from read responses. How you display these details to your users is your responsibility.
End users must be able to access these three details conveniently, without being sent to our hosted page for another verification.
secure-session retrieves the details upstream in real time and returns plaintext, with no-store in the response. This endpoint does not use idempotency caching.
2. Card Funds Are a Liability Owed to the Member
The money is physically held upstream and recorded in a separate ledger bucket. Therefore:
- Empty the card before closing it; otherwise, funds automatically returned upstream go to our account
- Chargeback penalties debit only available funds, never the card balance
3. Card Top-ups Are Asynchronous in Two Stages
下单成功 ≠ 钱到卡了
A successful recharge only means the order was received. Wait for the card credit Webhook to confirm arrival. Apply the spending limit only after credit is confirmed; increasing it earlier enables spending before the funds arrive.