To accept USDC on Base with PayIn, create a payment link, enable Base, and enter the receiving address of a wallet you control. Customers open the public link and approve the supported checkout in their wallet. You manage attempts and completed payments through a separate private link.
This works best for customers who already have a compatible wallet and native USDC on Base. It is not a card checkout or an automatic conversion service for tokens held on another network.
Check three different pieces of information
A receiving wallet address, a token contract and a network identify different things. Confusing them can make a valid-looking setup unusable.
| Item | What it identifies | Where you use it |
|---|---|---|
| Receiving wallet address | The destination you control | The Base receiving-address field |
| USDC token contract | The asset being transferred | Asset verification, not your receiving-address field |
| Base network | The blockchain recording the transfer | Wallet and checkout network selection |
Circle lists native USDC on Base at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. That is not your merchant receiving address. Check the official USDC contract list when identifying the asset. A token's displayed name alone is insufficient.
The same EVM wallet address can appear on different networks. That does not mean its USDC balance is available on every network. A customer holding USDC elsewhere needs a supported way to obtain it on Base before using this checkout; PayIn does not bridge it inside the payment page.
Prepare a receiving wallet
Use a wallet that supports Base and that your business can access securely. Verify the full receiving address in the wallet's own interface. Do not paste a token contract or a deposit address copied from an unrelated network.
If using an exchange deposit address, first verify that the provider accepts the exact asset and network and any deposit restrictions. A merchant-controlled wallet usually makes ownership and transaction checks easier to reason about. Keep seed phrases and private keys out of PayIn, customer messages and support screenshots.
You do not need to connect a merchant wallet to create a PayIn link. Entering a public receiving address does not give PayIn signing authority over that wallet. Creating a link also does not require purchasing USDC. Future wallet transfers, refunds or moving funds between networks can have separate costs.
Create the link
- Open Create link.
- Enter a recognizable payment title and choose a fixed amount or customer-entered amount.
- Enable Base and enter your Base receiving address. Enable other supported networks only when their receiving setup is ready.
- Review the setup and create it.
- Save the private management link using its copy or backup action.
PayIn currently offers free use without registration or a subscription. This describes the current product offer, not a guarantee of permanent pricing or that every external wallet operation is free.
Open management and select Links. Share Payment link with customers. POS display is for your counter device, and the private management URL is for managing the setup. They are separate access surfaces for the same receiving setup.
The full creation guide includes the current form and link handoff.
Explain the customer flow accurately
Tell customers the price in USDC and that Base is accepted. After opening the payment link, they follow the wallet flow shown by checkout. They should inspect the amount and authorization before signing; connecting a wallet alone is not payment.
Do not promise compatibility with every wallet, a fixed settlement time, or a conversion from any token. If a customer's wallet or funding network does not fit, resolve that before asking them to sign.
Confirm payment before delivery
In management, find the matching record and check its status, amount, network and transaction reference. An Awaiting payment attempt is not a completed receipt. Confirming means the existing operation needs reconciliation; it is not an instruction to collect twice.
For unresolved transactions, use the reference and the appropriate network explorer to inspect the actual USDC transfer and recipient. A customer's screenshot or a wallet's signature request does not establish receipt. See how to verify a USDC payment.
A reusable payment link does not assign transactions to orders automatically. If two customers owe the same amount, keep your own order reference and match the confirmed payment before fulfillment.
Before sharing widely
Check the title, amount mode, complete receiving address and public link on your intended devices. For an in-person counter, use the tablet POS guide. Do not publish the management link or embed the POS credential in a customer-facing QR.
For implementation reference, Base's network and bridging documentation explains moving assets onto Base. Those operations are separate from PayIn link creation and have their own requirements.