Crypto Payments for Merchants: A Guide to Assets, Fees and Custody

Start with your business need

Choose your situation. Each option has one suggested route and a guide to the details.

For the numbers, compare payment costs and network timing.

Crypto payment decisions begin with a sale: what the customer can pay, what your business needs to receive, and how staff know when to deliver. A wallet address solves the destination problem. It does not decide your pricing, provide a customer-facing request, explain an ambiguous payment, or match receipts to orders.

This series follows those decisions in order. It covers several assets and operating models; PayIn is one specific USDC receiving option, not a universal recommendation for every merchant.

AI-generated concept illustration, not a product screenshot or a functional payment request.

1. Choose what customers pay and what you keep

A customer paying BTC is not necessarily a merchant holding BTC: a processor may convert the receipt. Similarly, accepting USDC does not automatically mean receiving dollars in a bank account. Write down both ends before comparing fees.

Your decision	Read next	What to take away
BTC, ETH or stablecoins?	Asset comparison	Price denomination, customer holdings and settlement asset
Why consider USDC?	USDC benefits and limits	Dollar-denominated requests without assuming bank settlement
USDT or USDC?	Neutral merchant comparison	Exact network, wallet and conversion-route fit
Which type of stablecoin?	Stablecoin types	Currency exposure, backing and redemption differences

Do not choose solely from market-cap rankings. Ask a few actual customers which asset and network they already use, and check your own route for spending or converting receipts.

2. Choose a network the whole route supports

A stablecoin balance on one chain is not automatically spendable on another. Your checkout, receiving wallet and later conversion destination must agree on the asset and network. Distinguish native issuance from a bridged representation before displaying a code.

Start with USDC network selection, then native versus bridged USDC. For setup, use the Base guide or Solana receiving-account guide.

For a queue at a counter, compare the whole interval from scanning to staff confirmation. Checkout speed separates wallet preparation, approval, processing and notification. Block time alone does not establish when your merchant workflow can hand over an order.

3. Calculate the cost of the complete journey

Include more than a headline network fee. A customer may need an asset conversion; a provider may charge a percentage and a fixed fee; you may later exchange receipts and withdraw to a bank. Refunds are another transfer and operational task.

Use the USDC fee worksheet for an illustrative small sale and a larger invoice. If a provider advertises gasless payments, read paying without ETH or SOL: the customer may avoid holding the native gas asset while someone else funds the transaction.

Technical background lives in the x402 guide and facilitator roles. These explain payment infrastructure, not a universal merchant pricing schedule.

4. Decide who controls the money

Separate hosting from custody. Someone can host your payment page without holding your receiving-wallet keys. A self-hosted system can still connect to a custodial wallet or service. Ask who signs outgoing transfers and whether a settled receipt becomes an account balance subject to withdrawal rules.

Read custodial versus non-custodial payments, hosted versus self-hosted systems and the provider comparison. Evaluate named products and settlement routes rather than assigning one label to an entire company.

5. Design the actual sale

For an online invoice, choose a payment link rather than a bare address when the customer needs a recognizable request and amount. For a staffed counter, choose between printed QR and live POS. A printable sign helps customers find the request; the paper itself cannot announce a payment.

Staff need a receipt-verification routine and a way to distinguish equal-amount orders. Online fulfillment needs callbacks and order logic, not just a customer return page.

6. Plan the money's next step

Before collecting a day's revenue, decide who may move it, where it is recorded, and how you will handle a refund or unavailable conversion service. Use the payment security checklist, after-receipt workflow and end-of-day reconciliation guide.

Where PayIn fits

PayIn currently provides USDC Payment links and customer-facing POS displays on Base, Polygon and Solana, with no merchant registration required and currently free creation/use. It does not currently accept BTC, ETH, USDT or every stablecoin discussed in this series, and it does not promise permanent free pricing or automatic bank payout. The merchant receiving guide explains the current product flow.

Frequently asked questions

Does crypto acceptance require a payment processor?

Not always. A knowledgeable payer can transfer to a receiving address on an agreed network. A merchant tool adds a payment request, customer flow, records or operational feedback; choose the functions the sale actually needs.

Is USDT incompatible with x402?

Not as a general rule. Asset version, authorization method, network and facilitator matter. The USDT/x402 compatibility guide explains the distinctions and the limits of what has been verified.

Does a successful blockchain transfer complete my order?

The business must still match the right asset, amount and recipient to the order and apply its fulfillment policy. A receipt is one input to that decision.