Yellow Card Business: stablecoin collections, treasury and local payouts

Yellow Card’s 2026 operating story has an essential split: the firm announced the closure of its retail mobile app while continuing its business stablecoin infrastructure and liquidity/payment services. It would be materially misleading to describe the former individual app as open for ordinary new consumer purchases. The active service here is a B2B platform for enterprises, fintechs, wallets and financial institutions needing local fiat and stablecoin conversion, transaction routing, treasury infrastructure and payments in selected African and other emerging-market corridors.[1][9][2][3][4]

The developer documentation describes receiving local-currency payments from end users and delivering digital assets to their private wallet, or taking a crypto deposit and paying fiat to a beneficiary. Businesses integrate these routes through APIs and a portal, with country-specific payments rails. This is a direct settlement or quoted liquidity model, not an unrestricted global BTC order book. Marketing mentions support for 50+ fiat currencies and 30+ blockchains; neither count means every business can open an account or move funds across every pair and corridor.[1][9][2][3][4]

Yellow Card’s business documentation advertises real-time foreign-exchange/crypto rates and corridor-based transactions, but does not establish one universal maker/taker schedule suitable for every asset and fiat pair. The commercial cost can include the executable exchange rate or markup, local collection/disbursement fees, onchain gas, partner charges and liquidity terms negotiated for the business. These are not necessarily all disclosed on a general marketing page. An enterprise should request a written rate specification and fee annex for each intended country, payment method and settlement currency.[2][3][6][4]

For example, quoting a stablecoin-to-NGN payout requires matching the USDC or USDT chain, input amount, reference timestamp, quoted fiat amount after charges and local disbursement fee. A quote shown for a bank account cannot be carried over to a mobile-money wallet without confirming its channel tariff. Similarly a claim of instant or near-instant onchain settlement does not imply a domestic bank payout is completed instantly. Consumer or competitor commission rates do not establish the business tariff.[2][3][6][4]

Yellow Card’s direct-settlement API guide sets out a precise buy flow: a business creates a local-currency receive request specifying target crypto network and customer wallet; the end user makes a supported local payment; after confirmation and compliance screening, the provider sends crypto to that wallet. The corresponding sell flow collects crypto to a specified address and initiates fiat payout to a bank or mobile-money destination. The customer’s payment method and the business’s settlement account are distinct from each other.[4][6][7][3]

The guide distinguishes events such as `COLLECTION.COMPLETE`, `COLLECTION.SETTLEMENT_PROCESSING` and `COLLECTION.SETTLEMENT_COMPLETE`; the last is used when a crypto payout transaction hash is available. For crypto-to-fiat, `PAYMENT.PENDING_SETTLEMENT` and `PAYMENT.COMPLETE` represent different states. A corporate integrator should not treat receiving a request ID or quote as confirmed funds. The API’s 20-country B2B payment coverage statement and 50-plus currency marketing claim have different measurement bases; check each current corridor and available beneficiary channel.[4][6][7][3]

Yellow Card’s platform supports a variety of wallet and transaction configurations. Its developer pages refer to hosted stablecoin wallets or customer subwallets for some businesses, but the direct buy/sell settlement flow explicitly allows transfer to the end customer’s own external wallet without creating a permanent consumer Yellow Card account. The exact custody and title-to-assets position must therefore be drawn from the signed B2B agreement and the chosen API product. A blockchain token being credited to a wallet does not make the related fiat leg risk-free.[3][4][5]

Risk includes corporate account access, transaction signing/custodian design, stablecoin issuer reserve or freeze rights, chain failure, bank payout reversals and country-specific money movement rules. A partner integrating the API may be separately responsible for its own customers’ disclosures, verification and consumer complaint procedures. The ability to create a hosted wallet is not evidence that Yellow Card insures all third-party cryptocurrency liabilities or treats them as bank deposits.[3][4][5]

The company’s retail closure notice says the business will focus exclusively on companies and institutional-grade stablecoin infrastructure. Individuals should not be sent to a new retail-account flow merely because an old help article about consumer deposits remains indexed. The B2B payment API requires a partner relationship and sandbox/production credentials, with identity, business verification, payment-method and local compliance conditions. End customers of an integrating business may have their own verification duties and are not automatically direct Yellow Card clients.[9][6][3][8]

The FAQ markets payments across 20 supported countries while the broader developer portal describes far more currencies and blockchains. These figures are not equivalent to proof that every service, licence or partner bank works in every territory. An African treasury department should get a current business corridor matrix showing collection methods, local-currency payout availability, high-risk transaction restrictions, daily/transaction limits and the named local contracting entity. The entity licensed in South Africa cannot be substituted as the counterparty to a Nigerian local transfer without contract evidence.[9][6][3][8]

Yellow Card offers official business support and partner API documentation. A business transaction incident should include its request ID, API event history, channel and country, beneficiary identifier, wallet address, quote, business account and proof of the underlying collection/settlement. Such records distinguish a quote that expired from a locally collected payment whose stablecoin send is still pending. Sending duplicate payouts merely because a webhook has not appeared can cause irrecoverable double settlement.[4][9][6]

Former individual retail customers face a separate closure/refund process. The October notice requests identity selfies, identification and matching bank/mobile money account information or a correctly matched external crypto wallet address, with a stated 3–5-business-day refund time after a valid request. That period is a company estimate and should not be represented as unconditional. A partner business’s complaint under its enterprise agreement has different contact rights from a consumer seeking to retrieve a balance from a discontinued app.[4][9][6]

Yellow Card publishes a multi-country list with materially different legal statuses. As of its August 4, 2026 update, Yellow Card Financial South Africa (Pty) Limited reports FSCA Category I authorisation for crypto assets, FSP number 53790; separate bank sponsorship arrangements permit third-party payment participation from January and March 2026. Botswana reports a VASP licence and Zambia a VASP registration. These statuses should not be flattened into one worldwide “Yellow Card licensed everywhere” claim, and the categories of payment services differ from crypto exchange and custody authorisations.[8][10]

The August company table described a Nigerian SEC Accelerated Regulatory Incubation Program application as pending, whereas an August 13, 2026 Nigerian SEC announcement listed additional providers accepted into the accelerated programme. This later information can affect the company’s current status, but admission or approval-in-principle is not the same as a full unrestricted market licence. Ghana’s Bank of Ghana VASP registration and US FinCEN/Canada FINTRAC MSB entries are also entity-specific registration categories, not blanket authority to sell investments in every country.[8][10]

Yellow Card operates through several local companies rather than one homogeneous worldwide exchange counterparty. Its licence page identifies Yellow Card Financial Inc., Yellow Card Financial South Africa (Pty) Limited, Yellow Card Financial Nigeria Limited, Yellow Card Services Zambia Limited, Yellow Card Botswana Proprietary Limited and other entities; the country and business product determine which, if any, is actually contracting. The retail-app closure did not itself extinguish these B2B operations. The due diligence task for an enterprise is to obtain the locally relevant service agreement, fee annex, safeguarding provisions and dispute channel.[8][9][2]

Operator

Yellow Card group — entity depends on region and B2B product

Exchange model

Centralised

Service scope

Business customer stablecoin-to-fiat and fiat-to-stablecoin transactions, treasury and multi-currency payout infrastructure across supported corridors. The former retail mobile app is closed to new individual trading; legacy balances use the published refund process.

Client types

Professional clients; Institutional clients

Pricing publication

Quote only

Other names

Yellow Card Business; Yellow Card B2B; Yellow Card API

Headquarters

Multi-country operating group

Covered jurisdictions

South Africa; Nigeria; Ghana; Zambia; Botswana

Pricing scope

Real-time FX/crypto conversion quotes and corridor-specific payment/treasury charges. No public universal maker/taker schedule or flat business fee is verified; request contractual quote and fee annex.

Funding scope

Local banks, mobile money and stablecoin deposits/withdrawals on supported networks and 20-country payment API corridors; broader marketing currency counts are not all equivalent account-opening jurisdictions.

Custody and asset handling

Depending on API flow, Yellow Card/partner may hold stablecoin or fiat balances and initiate direct settlement to designated wallets. Not all partner-direct settlements create hosted retail crypto balances.

Client eligibility

KYB-onboarded businesses, banks, fintechs and institutional partners in selected corridors. End-user API payment steps may involve separate KYC/AML; direct Yellow Card individual retail accounts are no longer offered.

Support

Business sales, portal, API help and support. Former consumer customers directed to special refund route; closure notice says refund may take 3–5 business days, subject to eligibility/evidence.

Authorisation and registration scope

Multiple distinct local entities and statuses: South Africa FSCA Category I FSP 53790 with crypto assets; Botswana VASP licence; Ghana/ Zambia registrations; Nigeria SEC accelerated incubation approval-in-principle versus old company page pending language; US/Canada MSB entries are not full exchange licences.

Exchange metadata checked 26 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10

The economic usefulness of Yellow Card’s B2B model lies in accessing local fiat settlement against crypto/stablecoin liquidity without building every regional bank integration in-house. That does not make the corridor price or total execution cost invariant: funding, FX conversion, stablecoin network and mobile-money charges must be modeled separately. Developers should validate webhook idempotency so retries cannot create duplicate payments, record the trade quote and its expiry, and reconcile the final fiat and crypto legs independently.[4][8][9][2]

Yellow Card’s active business service is best compared with enterprise payment and conversion providers using the same corridors, volumes, beneficiary types and settlement deadlines. Its discontinued retail app is unavailable for new individual trading; former retail customers use the separate closure and refund process.[4][8][9][2]