Yellow Card
Connect Yellow Card to the rest of your business, with the right person approving what changes and a record of every action.
15 ways to read, 2 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Yellow Card, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Send stablecoin to a wallet
crypto_payouts.createApproval by rule - Send a payout
payouts.createApproval by rule - List balances
balances.listRead
Example flow
- Yellow Card · List balances
balances.listDone - Yellow Card · Send stablecoin to a wallet
crypto_payouts.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Yellow Card.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Yellow Card
- Yellow Card's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Yellow Card test account before you go live.
For developers
Technical detail
Yellow Card: stablecoin and local-currency balances, rates, channels, payouts, collections, stablecoin sends, conversions and vault transactions; governed payouts.
Yellow Card API docs- Source actions
- 15
- Destination actions
- 2
- Data types
- 9
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
balances1
- List balancesSource
Available balances across your fiat and stablecoin wallets.
channels1
- List payment channelsSource
Bank, mobile money and other rails for sending and receiving, with limits and fees.
collections3
- Get collectionSource
Read one collection by its Yellow Card ID.
- List collectionsSourceIncremental
Money collected from payers (receives), with local amount, rate and fees.
- Find collection by your referenceSource
Read the collection created with your own reference (sequenceId).
conversions2
- Get conversionSource
Read one conversion by its Yellow Card ID.
- List conversionsSourceIncremental
Conversions between local currency and stablecoins, with the effective rate.
crypto payouts3
- Send stablecoin to a walletDestinationNot retried automaticallyApproval before production
Sends USDT, USDC, PYUSD or EURC from your balance to an external wallet address. Moves money from your own account: runs when you enable this write on the connection, within any limits you set; asked for outside a published flow, a person approves it first.
- Get stablecoin sendSource
Read one stablecoin send by its Yellow Card ID.
- List stablecoin sendsSourceIncremental
Stablecoin sent from your balance to wallets, with the rate and fees.
networks1
- List banks and mobile networksSource
Banks and mobile money operators for a country or channel; use the ID when sending.
payouts4
- Send a payoutDestinationNot retried automaticallyApproval before production
Pays a bank or mobile money account in local currency from your Yellow Card balance, accepted on creation. Moves money from your own account: runs when you enable this write on the connection, within any limits you set; asked for outside a published flow, a person approves it first.
- Get payoutSource
Read one payout by its Yellow Card ID.
- List payoutsSourceIncremental
Payouts (sends) to bank and mobile money accounts, with local amount, rate and fees.
- Find payout by your referenceSource
Read the payout created with your own reference (sequenceId).
rates1
- List exchange ratesSource
Your buy and sell rates per local currency, in local-currency units per 1 USD.
vault transactions1
- List vault stablecoin transactionsSourceIncremental
Stablecoin deposits into and sends out of your custody vaults, with transaction hash.
Access and limits
- Authentication
- Yellow Card API key and secret
- Plans and access
- A Yellow Card business (partner) account with API keys from the Treasury Portal. Countries, channels, limits and custody vaults depend on what Yellow Card enables for the account; sends need API write permission.
- Test environment
- Create sandbox API keys in the Treasury Portal; sandbox requests move no real money.
- Rate limits
- Yellow Card does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries.
- Pagination
- Payouts, collections and stablecoin sends page with startAt and perPage inside a date window; conversions and vault transactions use a cursor.
- Provider events
- Yellow Card posts send, receive, conversion and custody events to registered webhook URLs, signed with X-YC-Signature (HMAC-SHA256 of the body with the API secret). Flows can start the moment something happens: when a collection is completed; when a collection fails; when a payout is completed; when a payout fails.
Before you build a flow
- Payments run through your own Yellow Card account exactly as you set them up: payouts and stablecoin sends run when you enable the write on the connection and publish the flow. Add limits or approval rules if you want, and daily reconciliation shows what moved. A payout is accepted on creation, so enabling the write and publishing the flow (or a person's approval, for a payment asked for outside a flow) is the acceptance step.
- Payouts and settlements: Yellow Card payouts are sends to recipients, read with the payouts list; there is no separate settlement batch.
- Refunds: Yellow Card refunds collections back to the payer; refunds show as collection status changes (pending_refund, refunded).
- Disputes: Yellow Card publishes no dispute or chargeback API.
- Intentional exclusions: creating collections, accepting, denying or cancelling requests, refunds, conversions and quotes, RFQs, vault and wallet changes, virtual accounts, bank account resolution and the travel-rule callback.
- Recipient and payer names, account numbers, phone numbers and identity documents are not returned.
- Payouts and collections need both dates for a window; without them Yellow Card reads the last 24 hours.
Developer reference
- Create the Yellow Card credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Yellow Card, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/yellow-card and the Connections API.