USDC on Base is Circle-issued USDC on the Base network. Before making a payment, confirm native USDC, Base Mainnet and the recipient's receiving instructions. A token contract identifies the asset; it is not the address to which you send a payment.
A business transfer needs two kinds of confirmation: the right asset reached the right address on the network, and the recipient credited it to the intended account or invoice. Keep both checks in the payment record.
| Check first | What it means |
|---|---|
| Asset | Native USDC; confirm acceptance separately from USDbC |
| Network | Base Mainnet, not Ethereum, Polygon or a testnet |
| Token contract | Identifies which token you hold; verify it against Circle's list |
| Recipient address | The destination supplied by the recipient's Base USDC receiving instructions |
Identify native USDC on Base
Compare the token contract with Circle's current mainnet list. The native Base USDC contract address listed there is:
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
This is the token identifier, not a recipient address. Do not paste it into the destination field of a payment.
USDbC is a separate bridged token on Base, with a different contract. A familiar name or logo does not establish which token you hold. Use the token accepted by the receiving service.
Coinbase's USDbC explanation distinguishes bridged USDbC from native USDC. A platform may support both or combine them in an account balance, but that platform's handling does not establish support at another wallet, exchange or payment service.
| Identity check | Native USDC | USDbC |
|---|---|---|
| What it is on Base | Circle-issued USDC | A bridged representation of USDC |
| How to identify it | Match the Base Mainnet entry in Circle's contract list | Inspect its own token contract and the receiving service's requirements |
| Can the receiving service accept it? | Confirm explicitly for native USDC on Base | Confirm separately; native USDC support alone is insufficient |
| Does the name supply a destination address? | No | No |
Identify the asset → Confirm the receiving route → Copy the recipient address
The token contract answers “Which token?” The receiving instructions answer “Where can this account receive it?” Keep those two checks separate.
Check native USDC separately from the Base receiving route, then retain the transaction and recipient credit confirmation. For the broader distinction between native and bridged assets, see the bridged USDC receiving checklist.
Receive USDC on the Base network
Open the receiving service's USDC receive or deposit screen and select Base if it is available. Check the exact token, recipient address, minimum amount and any additional instructions shown there. Share those receiving details with the sender and ask them to select the same network.
An address beginning with 0x does not, by itself, confirm that the service accepts Base deposits. An address may look the same across EVM networks while the service only supports some of those networks for a particular asset or account.
Before sharing receiving details, check:
- Asset: the service accepts native USDC, rather than only another token version.
- Network: the selected receiving route is Base Mainnet.
- Recipient: the address comes from the intended account's current receiving instructions.
- Amount: the agreed payment meets any minimum or other restrictions shown by the service.
- Reference: the sender knows which invoice or business payment the transfer settles.
A business reference can be retained in your invoice or payment records. Do not assume it must be entered into an on-chain memo field; follow any additional reference instructions the receiving service actually provides.
For AllScale, use the receiving route available in the relevant account screen. A network listed for moving your existing balance is not a blanket statement about every deposit, invoice or checkout flow.
Confirm credit before closing the invoice
Ask the sender for the transaction hash if a payment is not visible. Compare the network, token, destination and amount with the original receiving instructions. Then check the receiving service's balance or payment status.
If the transfer appears successful on Base but the platform has not credited it, retain that distinction in your records. A confirmed network transfer may still need the recipient service's processing or investigation. Do not ask the sender to pay again solely because an invoice still appears unpaid.
Send USDC and check the fee quote
At the sending service, choose USDC and Base, then enter the recipient address and agreed amount. Review the token and network again before confirming. Use the displayed quote and keep the transaction hash. Compare the completed transfer with the recipient's credited balance before closing the payment record.
For an ordinary self-custody transfer, Base network fees are paid in ETH. ETH held on a different network does not provide the Base balance needed for that transaction. Some services sponsor fees or collect their charges differently; follow the actual flow rather than assuming every payment requires a separate ETH top-up.
Base's network-fee documentation explains that costs vary with the transaction and network conditions. Use the current quote instead of a fixed fee quoted in an old tutorial.
| Quote item | What to check before confirming |
|---|---|
| Sending amount | The token amount you intend to transfer |
| Expected recipient credit | Whether the recipient will receive the full agreed amount after any deductions |
| Network fee | The amount, denomination and how it is funded |
| Service fee | Any separate withdrawal, routing or platform charge |
| Total debited | The full amount removed from your balance, including applicable charges |
For example, if an invoice calls for 500 USDC and a service deducts a fee from the entered amount, entering 500 may not deliver 500. Read the quote and resolve who bears the fee before confirming. This is a calculation check, not a claim about how every service charges.
Where appropriate, a small initial transfer can help verify a new route. It must meet the receiving service's minimum and follow its instructions. Confirm that it was credited before sending the rest, and retain both payment references so they can be matched to the same invoice.
If a transfer fails or remains pending, inspect its status before trying again. A second submission can create a duplicate payment if the first one later completes.
Move USDC from Ethereum or another network
A normal same-network send does not move a balance between blockchains. If the funds are on Ethereum, Polygon or another network, choose a service that explicitly supports the source network, Base as the destination and the token the recipient accepts. Review the route, output token, fees and status before proceeding. Matching address formats do not replace a supported cross-chain route.
Use this order of checks:
- Identify where the funds are now, including the exact token version.
- Confirm that the selected service supports that source and Base as the destination.
- Check that the output is the token required by the receiving account, such as native USDC.
- Review fees, minimum received, any additional steps and the status checks for the route.
- Confirm the destination balance before treating the move as complete or sending a subsequent payment.
An exchange withdrawal that offers Base and a cross-chain transfer from a self-custody wallet are different operations. Base's route guide describes several routes and notes that third-party bridges have their own trust models. Do not choose a route solely because its button says “USDC.”
For source-network checks, use the guides to USDC on Ethereum and USDC on Polygon. After any move, verify the output token again on Base. Changing the network selected in a wallet's display does not move funds between chains.
Use the relevant AllScale workflow
AllScale's Wallet Features guide lists Base among the networks available for Move funds, alongside USDT and USDC as supported stablecoins. It describes Move funds as movement between your own wallet addresses. Sending to another person is a separate operation.
Within that flow, select the source balance and destination network/token, then review Fees & timing before approval. The guide describes fees paid through the stablecoin being moved; that is different from an ordinary wallet transaction for which the sender supplies ETH. Check the live quote and resulting balance rather than carrying assumptions from one flow to the other.
The public AllScale USDC wallet page separately lists Base among the Virtual Account USDC networks. A bank withdrawal through an enabled Virtual Account channel is not the same as a wallet move or a payment to an external wallet. Access, receiving instructions and charges belong to the specific operation.
| Your task | Relevant workflow | Check separately |
|---|---|---|
| Rearrange your existing wallet balance | Move funds | Source, destination token/network, fees and amount delivered |
| Send to an external recipient | The relevant wallet sending flow | Recipient's accepted token/network and current receiving address |
| Request a client payment | Invoice | Payment options offered for that particular invoice |
| Withdraw through a bank channel | The enabled Virtual Account withdrawal flow | Account eligibility, current funding instructions, quote and bank-transfer status |
Support in one row does not establish support in the others. In particular, a Base listing for Wallet Move funds or Virtual Account does not mean every Invoice, Checkout, region or USDbC deposit is supported. Use the route shown in the relevant account flow.
Keep the transfer with the invoice or payment record
Save the agreed amount and asset, network, recipient details, transaction hash, quoted charges and the recipient's credit confirmation. For an invoice payment, include the invoice reference so the payment can be matched to the correct balance.
| Field | What to keep |
|---|---|
| Asset | Native USDC; confirm acceptance separately from USDbC |
| Network | Base Mainnet |
| Native USDC contract | The verified token identifier from Circle's Base Mainnet entry |
| Recipient address | The address copied from the recipient's Base USDC receiving instructions |
| Amount and charges | Agreed amount, displayed network and service charges, expected recipient credit |
| Business record | Invoice reference, transaction hash and recipient credit confirmation |
For an illustrative invoice INV-2026-104 for 500 USDC, the record should connect that invoice to the Base transfer and the recipient's confirmed credit. If two transfers settle it, retain both hashes and their credited amounts. A hash alone does not explain which business obligation was paid.
If the transfer appears complete but the recipient has not credited it, compare the asset, network and receiving instructions with the original record before submitting another payment. Contact the relevant receiving service with the transaction details if further investigation is needed; do not assume an unsupported transfer can be recovered.
A bank withdrawal has another status to track. Completing the blockchain portion does not establish that money has reached the beneficiary's bank account. Follow the bank-transfer status in the applicable withdrawal flow.
FAQ
Is USDC on Base the same token as USDbC?
Native USDC and USDbC are separate tokens on Base with different contracts. Confirm which one the receiving service accepts; support for one does not establish support for the other.
Can I use an Ethereum address to receive USDC on Base?
The address format can look the same, but the receiving service must support the selected asset on Base. Use its Base USDC receiving instructions rather than inferring support from the address.
Do I need ETH to send USDC on Base?
An ordinary self-custody transaction uses ETH for Base network fees. Some services handle or sponsor fees differently. Check the actual transfer flow and quote.
Where do I find the native Base USDC contract?
Use Circle's USDC contract-address list and its Base Mainnet entry. Keep that token identifier separate from the recipient address supplied by the receiving service.
Does a completed Base transaction mean a bank withdrawal has arrived?
No. A network transaction and a bank withdrawal have separate status checks. For a Virtual Account withdrawal, track the bank-transfer status in the relevant AllScale flow.
Check the receiving route before sending
Explore the AllScale USDC wallet, choose the operation you need, and confirm its current token, network and receiving instructions. Retain the transaction reference with the invoice or payment record until the recipient's credit is confirmed.
