For a USDC deposit on Aptos, verify the exact asset identifier and whether the receiving service supports its Fungible Asset transfer flow. Do not treat Coin-to-FA migration as conversion of bridged USDC into Circle-issued USDC. The token’s identity, its storage representation and the service’s deposit support are separate checks, even when the wallet displays the same familiar dollar symbol.
Start with Circle’s Aptos asset identifier
Circle’s current USDC address directory lists Aptos mainnet USDC at 0xbae207659db88bea0cbead6da0ed00aac12edcdda169e591cd41c94180b46f3b. Check that entry against the asset details in your wallet or explorer, not against the destination address you plan to fund. An asset metadata address identifies a token; it is not your exchange deposit address.
A recipient saying “Aptos supported” has not necessarily answered which assets it accepts on that network. Ask for the supported USDC identifier and deposit procedure. Keep the response with the deposit instructions, especially if an old help page still describes a different asset or a different way of detecting incoming transfers.
The Circle launch announcement identifies native USDC separately from lzUSDC, a bridged representation. That historical announcement is evidence of the distinction, not a current deposit policy for every exchange. It does not make a transfer accepted by a service merely because the network is correct.
Coin versus FA is a different axis from native versus bridged
Aptos’s Fungible Asset documentation describes FA metadata and asset stores, and a pairing mechanism for migrated Coin assets. Pairing concerns representations of a particular asset. Two unrelated tokens do not become paired assets because they share a symbol, a price target or the word USDC in their name.
| Question | Evidence to inspect | Conclusion it does not establish |
|---|---|---|
| Which token is this? | The mainnet identifier and issuer’s directory | That every exchange accepts it |
| How is the balance represented? | Coin type, FA metadata and any verified pairing | That a bridged asset became a native asset |
| Where is this holder’s balance? | The holder and relevant store or indexed balance | That the metadata object is the deposit recipient |
| Did this transfer deliver the asset? | Committed outcome, recipient ownership and asset movement | That a receiving service has posted internal credit |
| Will the service credit this deposit? | Its supported asset and transfer instructions | That an unsupported transfer can always be recovered |
For a fictional comparison, a wallet can display “USDC” next to Asset A and “USDC” next to Asset B. If the service accepts only A, a correct network and a familiar label do not make B acceptable. Likewise, two rows representing the verified paired forms of one asset need a different accounting treatment from two unrelated assets with matching labels.
The metadata object and your balance store have different roles
The Aptos exchange integration guide distinguishes the asset’s FA metadata address from the primary fungible store linked to a holder. It also explains that balance and transfer tracking must handle the relevant asset standard. A system that only looks for the old resource or event shape can require an integration update rather than another payment from the user.
The separate Move resources overview describes how resources and object-based storage differ. For a user diagnosing a missing display, this means an absent old-style CoinStore is not enough to establish that the balance is zero. Ask which asset and representation the interface is querying before deciding that funds need to be restored.
Keep an account address, metadata address and store address clearly labelled in a support note. They can all look like hexadecimal values, but they answer different questions. Copying the address beside an asset name into a withdrawal form can therefore be a serious category mistake. Use the receiving service’s actual deposit instructions for the destination.
A deposit check that does not rely on the logo
- Confirm Aptos mainnet on both sides, rather than a testnet or a different chain with a similarly styled address.
- Open the asset details and compare the full identifier with the issuer’s current directory.
- Ask the receiving service whether it accepts that exact asset and the intended FA transfer flow.
- Use the service-provided recipient and review any minimum, restrictions and current deposit status in its own instructions.
- Review the proposed transfer’s actual asset and recipient before signing, then retain its hash.
- After submission, verify the committed outcome and the relevant asset movement before treating the deposit as complete.
A small trial can limit exposure only after those checks and the service’s minimum have been considered. It does not repair unsupported asset identity. Do not split an unknown representation across repeated deposits in the hope that one will appear; you would create additional transfers without resolving the acceptance question.
If the transfer is already complete, investigate credit separately
Start with the hash and actual recipient in the committed transaction. Identify the asset moved, and distinguish a successful transaction from the specific balance effect you expected. A transaction can concern another action or another asset. A screenshot of a wallet total omits the details the receiving service needs to reconcile a deposit.
A useful request is: “This transaction delivered this asset identifier to this recipient on Aptos mainnet. Your instructions list this supported asset. Please confirm whether the transfer representation is supported and whether manual review is possible.” Include the service’s deposit reference if it supplied one, and state honestly if you used a different asset. Do not give support signing keys or a wallet backup.
If the wallet and an explorer disagree, compare their asset filters and observation point. For verified migrated assets, use a balance source that accounts for the relevant paired forms; do not add the same aggregate balance to its component again. If the issue lies in a service’s detector, the service must assess it. No general protocol description promises that it will credit or return an unsupported deposit.
A migration label is not permission to sign a conversion
Circle’s bridged-to-native migration guide treats the two USDC representations as distinct assets and recommends identifying them clearly. That is different from Aptos’s framework-level Coin/FA pairing. If someone asks you to connect a wallet for “mandatory USDC migration,” establish which of those operations they mean before considering any signature.
A genuine conversion can have a separate route, cost and output; a renamed row is not proof it happened. Reject explanations that claim all USDC labels are interchangeable or that importing a recovery phrase is needed to update a token standard. If the objective is simply to display an existing balance, ask for a read-only explanation first.
The general native-versus-bridged USDC guide covers the wider distinction, and the USDC asset page provides context. Before a simple swap, check the live asset and network choices rather than assuming every Aptos representation is available. This diagnostic guide does not assert that a particular USDC-on-Aptos route is supported by KOT.CASH.
FAQ
Is the Aptos USDC contract address my deposit address?
No, the issuer-listed identifier identifies the asset. Send only to the recipient supplied by your wallet or receiving service after verifying its instructions.
Does an Aptos USDC bridge balance automatically become native USDC through FA migration?
No, the framework’s Coin/FA pairing and conversion between distinct bridged and native assets are different processes. Verify the exact identifier rather than inferring conversion from a wallet label.
Why can Aptos USDC appear in a wallet but not as an exchange deposit?
The service may not accept that exact asset or may need to inspect how the transfer is represented and detected. Establish the committed transfer and ask the service to reconcile it; a wallet display alone does not prove internal credit.