Cash-out safety

Cash out USDC safely: check the fiat leg before release.

Non-custodial escrow removes platform custody risk, but the payment-app leg still has operational risk. Treat the fiat payment like a real payment workflow, not a chat-room handshake.

01

Before creating a deposit

  1. 01Confirm that the provider, account type, region, and payment type permit the activity before creating a deposit.
  2. 02Use the exact payout identifier required by an eligible method.
  3. 03Confirm the account can receive the selected currency and approximate order size.
  4. 04Complete any required extension setup only after checking first-party provider policy; Wise prohibits P2P crypto-sale receipts and PayPal may require preapproval.
  5. 05Set order sizes that fit your payment app limits and your tolerance for reversal risk.
  6. 06Use truthful payment descriptions. Never disguise or misrepresent the purpose of a transfer to evade provider review.
02

During an order

  • Do not release manually just because a buyer says they paid.
  • Check amount, currency, sender, recipient, timestamp, and status inside your payment app.
  • Be cautious with pending, review, refundable, disputed, or reversible payments.
  • Keep records for your own accounting and tax reporting.
  • Pause or withdraw if a payment app starts throttling or reviewing incoming transfers.
03

Known risk areas

Reversible transfer
Some payment-app or bank payments can be challenged later. Use conservative limits and known methods.
Account flag
Banks or payment apps may review restricted activity. Follow their rules, describe payments truthfully, and stop if the account is under review.
Wrong amount
Buyer paid too little, too much, or wrong currency. Do not release unless the active order exactly matches.
Failed proof
Payment may be real but verification failed. Use manual release only after checking evidence yourself.
Stuck intent
Buyer started but did not complete. Wait for expiry or cancel before the locked portion frees.

Common questions

What is USDCtoFiat?

USDCtoFiat coordinates non-custodial sales of native Base USDC for USD, EUR, or GBP through ZKP2P smart contracts. Payment-provider eligibility and account policies still apply; technical route support is not permission to use an external account, and Wise currently prohibits P2P crypto-sale receipts.

Does USDCtoFiat hold my funds?

No. You sign every transaction from your own wallet. Your USDC is locked in a public Base contract and releases to the buyer only after their payment is proven. You can withdraw any unfilled deposit at any time.

What does it cost to sell?

Creating and managing a seller deposit is free, though Base gas applies to onchain actions. The offramp SDK is free to integrate. On delegated fills, Delegate's 0.10% manager fee comes from the USDC released to the buyer, not from your fiat proceeds or your quoted rate. Peerlytics analytics and API credits are priced separately.

Do I need a centralized exchange account?

No exchange account is required to use USDCtoFiat. You need a wallet holding USDC on Base and an account on the payment app you want to be paid in. The payment app's own account rules and limits still apply.

Do I need to complete KYC?

USDCtoFiat does not collect identity documents, hold your fiat, or hold your keys. The payment app you use still controls its own verification, limits, and account rules. USDC settlement happens through Base smart contracts, and we cannot change what Venmo, PayPal, Wise, Zelle, or your bank requires.

Can USDCtoFiat reverse a fiat payment?

No. Fiat moves directly through external payment platforms. USDCtoFiat cannot reverse, freeze, or mediate a payment-app transfer.

Should buyers write crypto or USDC in the payment note?

No. Crypto-related wording can increase the chance a payment platform or bank flags the transfer. Use neutral notes where a note is required.

When should I pause a deposit?

Pause or withdraw if your payment account is being reviewed, you are near transfer limits, the rate is stale, or you no longer want that liquidity publicly fillable.