Issuing section

Stablecoin Cards

Provision cards only after KYC/KYB approval, connect to a Rain-style issuing provider through an adapter, and authorize card transactions against stablecoin balances with fast approve or decline decisions that fit the card lifecycle from provisioning to clearing.

2 core flows KYC required before provisioning Real-time authorization

Interactive flow lab

Provision cards, then authorize spend

Use the tabs to switch between issuing a card and deciding a card transaction.

High-level sequence

Provision a card, then authorize a spend

Two connected flows: issuing a card behind the KYC gate, then deciding a transaction in the network window.

Customer Cards API Risk · KYC Card issuer Ledger · Treasury

1

Customer→Cards APIrequest

Request a card (identity already KYC-approved).
2

Cards API→Risk · KYCrequest

Confirm the eligibility gate before provisioning.
3

Risk · KYC⇢Cards APIresponse

Eligible — proceed.
4

Cards API→Card issuerprovision

Create the cardholder and provision the card.
5

Card issuer⇢Cards APIresponse

Card active — customer notified it is ready.
6

Card issuer→Cards APIauthorization

Authorization request arrives at the point of sale.
7

Cards API→Ledger · Treasuryrequest

Reserve funds — place an authorization hold if the balance is available.
8

Ledger · Treasury⇢Cards APIresponse

Hold placed — approve, or decline if funds fall short.
9

Cards API⇢Card issuerdecision

Return the decision inside the network window; clearing & settlement follow later.

Endpoint map

Find the issuing call

Filter cardholder, card, authorization, transaction, and Rain adapter endpoints.

Concept notes

The card ideas worth remembering

Questions

Check your understanding

Pick an answer and the page will explain the reasoning.