A direct payer sends USDC or USDT on the agreed network. In the account-detail route, a regulated partner receives accepted incoming fiat and converts it to USDC on Arbitrum. Match the payer's available method to the balance the recipient can use.
Both routes end with a supported stablecoin in the self-custodial wallet. Receiving cash, converting the stablecoin or funding a card requires a separate transaction.
| Receiving route | What the sender uses | What you receive | Main dependency |
|---|---|---|---|
| Direct wallet payment | A compatible stablecoin and network | USDC or USDT in a self-custodial wallet | Exact token, network, address, and sender capability |
| Partner-issued local account details | ACH/wire, SEPA-style EUR transfer, Faster Payments, SPEI/CLABE, or Pix | The partner currently converts the incoming fiat to USDC on Arbitrum | Country, KYC, endorsement, payer, and partner eligibility |
Cadmos Pay is entirely self-custodial, and the user controls the wallet's signing authority. Cadmos never takes custody and is never the bank, broker, exchange, fiat counterparty or trading counterparty. The regulated account-detail provider controls its fiat leg. A later card, cash, or conversion provider controls the next leg.
Route one: send the asset to the wallet
The direct route has one transfer:
payer → stablecoin transfer on the agreed network → recipient wallet
The payer may use a bank, exchange, or other provider to obtain the stablecoin. The recipient may use another provider later for cash or card spending. Each provider controls its own step.
Before payment, agree on the asset, network, address, amount, fee responsibility, and the event that counts as settlement. An invoice also needs its reference currency and any conversion source; a family payment needs a clear recipient and purpose. The detailed USDC and USDT invoice guide owns the full template and accounting checklist.
Stablecoin market prices can vary from their reference value. Circle describes that risk in its USDC terms and risk disclosures.
The token and network must both match. Circle publishes network-specific entries in its official USDC contract directory, and Tether lists supported USD₮ deployments on its protocol page. Select the route from the wallet's receiving flow because several networks use the same address format on separate ledgers.
For a new payer, send a small test when the economics allow it. Verify the token, network, destination, and net amount before the remainder. Confirmed blockchain transfers are generally final; Ethereum's wallet guide covers that property. Cadmos documents a narrow manual process for some mistakes in its cross-chain recovery guide.
Route two: use eligible local account details
For payers using an ordinary local transfer, eligible Cadmos users in supported countries can request personal payment details issued by an independent regulated partner:
| Currency | Local details or scheme |
|---|---|
| USD | ACH and wire details |
| EUR | IBAN |
| GBP | Faster Payments details |
| MXN | SPEI / CLABE details |
| BRL | Pix details |
Only the EUR route uses an IBAN. Use the local identifier shown for each other currency.
An independent regulated partner issues and controls these payment details. The partner sets country availability, identity checks, acceptable payers, transfer types, fees, settlement times, and limits. Its current country rules block Lebanon. Eligible users elsewhere should rely on the option and terms shown in the app.
Confirm that the partner permits the payer name, payment purpose, and transfer type before sharing personal account details. A reference may also be required.
Two Pix routes
Pix appears in 2 separate partner products within Cadmos Pay:
- Receive BRL: An eligible user gets personal Pix details and shares them with an accepted payer. The partner converts the incoming BRL to USDC on Arbitrum and sends it to the user's self-custodial wallet.
- Buy USDT: The user opens Add Money, chooses BRL and Pix, pays the on-ramp partner from a Brazilian account, and receives USDT on Arbitrum in the self-custodial wallet.
The selected product determines the asset received. The Brazil Pix guide explains the purchase route.
Marketplace payout rules
A freelance marketplace controls its payout destinations. It may restrict providers, require an exact beneficiary-name match, test the account, or reject certain financial institutions.
Before entering partner-issued details into a marketplace or employer portal, confirm that the platform accepts the account type, the beneficiary name matches, the account provider permits that payer, and the return process is documented.
Use a payout method the platform explicitly lists or arrange a supported direct wallet payment with the client.
After receipt: cash, cards and conversion are separate routes
Cash requires a separate conversion. In supported locations, an eligible user may see a local-agent buy or sell option under the relevant app flow. The user accepts a separate quote and settles through the method supported by that agent. The independent agent or partner is the fiat counterparty.
Availability depends on country coverage, identity checks, the option appearing for the user, agent hours, liquidity, currency, and limits. Confirm the amount, settlement method, collection procedure, and receipt. Use only instructions shown in the verified flow.
Card spending requires a separate funding action. A partner card program controls the funded balance, eligibility, limits and refunds. The self-custodial wallet and card guide explains the funding process.
Wallet and provider limits
Cadmos imposes no wallet-balance or transfer-volume ceiling on direct supported wallet activity. Partner routes apply their own limits.
The sender's exchange can impose withdrawal limits. A blockchain can charge changing fees. A stablecoin issuer can apply controls under its terms. A bank, account-detail provider, agent, card program, or fiat on-ramp can set transaction caps, request more documents, delay settlement, or refuse a route.
Calculate the total route cost:
sender acquisition + withdrawal + network + conversion or spread + recipient exit
Calculate every leg through the recipient's final use. Acquisition, withdrawal, conversion, and cash access can outweigh the initial transfer fee.
Keep a record that explains the payment
For any receipt, retain the payer and recipient, purpose, agreed asset or currency, route, timestamps, gross and net amounts, fees, and the value used for accounting. Add the address and transaction hash for an on-chain payment. Add the quote, transfer receipt, provider reference, and any returned-payment record for a partner route. For commercial work, keep the contract, purchase order, or invoice with those records; for a personal transfer, keep the message or reference that explains the relationship and purpose.
A blockchain transaction records asset movement. Separate records establish commercial purpose, beneficial owner, tax treatment, and source of funds. Regulated providers may request originator, beneficiary, and payment-purpose information; FATF's Travel Rule supervision guide covers transfers involving service providers and self-hosted wallets.
Protect payment instructions like bank details and confirm address changes through a known second channel. Keep recovery phrases and private keys secret from employees, partners, agents, and clients. Cadmos's role and user responsibilities are set out in the Terms of Service.
Before the payer sends, document the starting asset, receiving balance, counterparty at each step, limits, and final use. That route map determines whether the payment works for the recipient.
This guide is general product information, not financial, legal, tax, or investment advice. Stablecoins carry issuer, market, network, smart-contract, liquidity, and regulatory risks. Partner and agent availability depends on jurisdiction, identity checks, product eligibility, liquidity, and current terms; the terms and quote shown at the time of use control.