Receiving overseas payments in USDC

A named virtual account gives the customer bank details for incoming transfers. Identity verification and account approval can be separate stages. The provider's program determines eligible countries and activities.

Receiving payment for work requires permission to accept third-party transfers. Confirm this explicitly; own-account top-ups don't establish permission to collect client payments.

Use the details issued by the provider for the intended transfer method. The recipient name and currency must match. Domestic US and international payment instructions can differ.

Keep the invoice reference and ask the client to retain their transfer confirmation. The provider may need the amount, date and bank reference to investigate a delay.

One model converts incoming bank transfers into stablecoins and sends them to a linked wallet. BlindPay documents this process. It remains a potential integration for white.cards and is not connected yet.

Show the deposit amount, fee and amount delivered to the wallet. Bank account currency, token and settlement network are separate settings to confirm before the first transfer.

A client's transfer confirmation doesn't mean the balance is available. The app needs provider status updates to distinguish a deposit, review, completed settlement and return.

When a review delays payment, show the reason and what the provider needs next. Document requests need a submission channel; returns need a status linked to the original transaction.