Sell USDC for a bank payout

Choose Sell, enter the native USDC amount, and select the EUR or USD payout route. Review the fiat result, rate, spread, service fee, any network treatment, and the exact deadline. The quote applies only to the order and conditions displayed.

Provide accurate customer details, the self-controlled Ethereum wallet expected to send, and the intended bank beneficiary. Verify the email and complete requested checks before the order reveals a dedicated deposit destination. Then make one new transfer and retain its transaction hash.

• Use the exact sending wallet recorded for the Sell order.
• Send only native Ethereum USDC to that order’s dedicated address.
• Transfer the exact amount once; do not split or batch it.
• Submit the new transaction hash associated with that transfer.
• Track confirmations, review, and the eventual bank payout separately.

A Sell quote fixes the displayed USDC requirement and fiat payout only through the stated quote window and receipt conditions. Pressing Send before the deadline is not necessarily the same as the service confirming receipt before it expires.

Wallet signing, network broadcast, gas replacement, congestion, and the configured confirmation threshold all take time. A late, underpaid, overpaid, unmatched, or otherwise non-conforming transfer can require review, return, cancellation, or a replacement calculation. The old quote must not be assumed to survive expiry.

The recorded source wallet and the observed Ethereum transfer help connect the payment to the correct order. A transaction hash alone is not permission to reuse another person’s payment, an earlier transaction, or a transfer sent to a different order.

Do not withdraw directly from an exchange or custodial platform if it cannot guarantee the actual sending wallet required by the order. Do not use Base, Polygon, Solana, Arbitrum, another network, bridged USDC, another stablecoin, a smart-account batch, or a multi-recipient transfer unless the current secure order explicitly supports that exact route.

The bank beneficiary must be entered accurately and must be an account the customer is authorised to use. EUR and USD routes can require different fields. Recheck the name, IBAN or account details, routing information, country, and currency before creating the order because an outgoing bank payment may not be recallable.

Email verification protects the order session but does not replace identity, wallet-control, source-of-funds, transaction-purpose, sanctions, fraud, or bank checks. A-PFI does not require a permanent customer password account; it may still request the evidence necessary for a particular Sell order.

Never reuse a deposit address from a previous order, send before the dedicated address is revealed, substitute a cheaper network, copy a shortened address, submit an old hash, or claim one transfer against two orders. Amount similarity by itself does not identify a payment.

If you believe a transfer was sent incorrectly or is not detected, stop before sending anything else. Keep the wallet receipt and new transaction hash, return to the tracker, and open one secure Support request for the affected order. Recovery or return is not guaranteed.

A broadcast transaction can appear on an explorer while the order still waits for the configured confirmations and internal checks. Once the qualifying transfer and any required review are complete, the bank payout is prepared for the confirmed beneficiary.

Blockchain confirmation does not guarantee immediate bank credit. Banking cut-offs, intermediary banks, weekends, beneficiary checks, or operational availability can extend the timeline. Follow the status attached to the order rather than treating an estimate as a guaranteed completion date.