Why the Crypto Network Matters When Your Customer Pays

A familiar coin name is only part of the instruction

A customer says they have USDC and are ready to pay. Before you create their checkout, confirm which network they can send it on. USDC exists on multiple blockchains, including Base, Ethereum and Solana. The coin name alone does not identify the payment route. Circle publishes separate USDC contract information for each supported blockchain. See Circle's USDC contract directory.

For a merchant, the practical rule is straightforward: the customer's currency and network must match the current invoice. A correct-looking address is not enough to justify selecting a different network. Treat the network name as part of the payment instructions, just like the amount.

Follow the customer's invoice, not your settlement balance

Ulasend supports specific combinations of stablecoins and networks. The available options depend on your account and accepted payment methods. A live invoice fixes its source when it is created; the checkout then shows that source's currency, network, exact amount, address and any required memo. Review supported payment methods.

Your merchant settlement is a separate part of the journey. Supported incoming routes settle into USDC on Base, but that does not mean every customer should send USDC on Base. A customer paying an invoice issued for another supported source must follow that invoice's instructions. Conversion and settlement happen through the selected route.

Run through five details before the customer sends

Give staff a short checklist they can explain without asking to control a customer's wallet. The customer should review these details on their own sending screen:

• Currency: select the exact stablecoin named at checkout.
• Network: match the displayed network, not the cheapest available option.
• Address: use the address from this invoice, not an older saved recipient.
• Memo: enter it separately whenever the checkout requires one.
• Amount: send the requested amount and account for any sending or withdrawal fee.

Change the payment request before changing the network

For example, imagine an invoice requests 250 USDC on Base. A customer who holds USDC on Ethereum needs a compatible payment arrangement before sending. Choosing Ethereum because it is the wallet's default does not satisfy the Base instructions.

If the customer cannot use the selected network, pause the payment. Check whether your account accepts a source they can use and create a new invoice with that selection. Ulasend does not switch an issued live checkout to a different coin or network. Keep the original invoice record when checking any payment already sent. Read the source-selection guide.

Avoid keeping two payment requests in circulation without explaining which one the customer should use. If they have already submitted a transfer, investigate its status before asking them to pay again.

If the wrong network was used, stop and document it

Ask for the invoice reference, transaction hash, sending network, currency and amount. Contact Ulasend support with those details and have the customer check with their sending provider. Do not promise automatic recovery or ask for another transfer as a troubleshooting step. Coinbase, for example, tells senders to match the recipient's expected network and warns that it cannot recover funds sent on the wrong network. Read Coinbase's troubleshooting guidance.

For the next sale, make the network check part of the conversation before checkout is issued. That gives the customer a clear payment path and your team a cleaner record to reconcile.