For developers building on Circle products, post Q&A, best practices & SDK/API insights. Use Tags

Circle Products & Developer Toolings

, but a few good questions deserved cleaner answers than I was able to give in the moment. This follow-up pulls those together in one place.

If you are new to Gateway, the short version is: you deposit USDC once, wait for that deposit to finalize on the source chain, and then use that unified balance to route USDC across supported chains much faster than starting a fresh crosschain transfer each time.

If there are more questions you want us to cover in a future session, drop them in the thread.

Esther Daka asked: What makes Arc's payment flow more reliable or efficient than existing onchain payment solutions?

Arc and Gateway complement each other well for payment flows.

Arc gives you deterministic finality and very fast settlement, so deposits can become available in Gateway much faster than on chains that require longer confirmation windows. Once that balance is established, Gateway can mint on the destination chain in under 500 milliseconds.

faster source-side settlement into Gateway

faster crosschain availability after the balance is established

more predictable fees on Arc because gas is denominated in USDC

The right mental model is not that Arc removes every wait in the system. It front-loads the finality wait into the deposit step, then makes later routing much faster.

Prakash | AI & Web3 Builder asked: For someone new to chain-agnostic apps, what's the best mental model for Gateway and how do they get started quickly?

The simplest mental model is: deposit USDC once, then treat it as a unified balance you can access across supported chains.

Instead of managing separate USDC balances chain by chain, Gateway lets you deposit into Gateway Wallet contracts on a supported source chain and then mint on a supported destination chain from that balance. The deposit still needs to finalize first, but after that the routing step is much faster.

make a test deposit on a supported source chain

transfer to a supported destination chain

add the Gateway Forwarding Service if you want Circle to handle the destination-chain mint for you

Justin T Roy asked: In Circle Wallets, what do we actually use as gas to deposit to Gateway?

On Arc, the native gas token is USDC, so deposits use USDC-denominated gas. On most other EVM chains, you still pay network fees in that chain's native token unless you are using a sponsored flow such as Gas Station.

So Gateway moves USDC, but the gas model comes from the source chain and wallet setup.

henry . asked: Does Circle Wallets support Monad?

Sena I. asked: After a burn intent is signed on Gateway, is the user's balance locked until the attestation is returned, or does it remain available during that window?

Only the portion needed for that transfer is committed.

If a wallet has 100 USDC available and a valid burn intent is issued for 10 USDC, then that 10 USDC plus the associated fees should be treated as committed while the attestation is active. The rest of the balance remains available for other activity.

If the attestation expires without being used, that committed amount is released back into the available balance. So the whole wallet is not locked. Only the amount reserved for that transfer, plus fees, is temporarily committed.

Light Gabriel asked: Does the new version of CCTP make it possible to request gas from the destination chain?

Not as a generic "destination-chain gas request."

What is closer to that mental model is the 

, where Circle handles the destination-side mint transaction for you. That means you do not need to run destination-chain infrastructure yourself for that mint step, and the fees are accounted for up front.

So the better framing is not "CCTP gives you destination gas." It is "the CCTP Forwarding Service can handle the destination-side mint flow for you."

thefirst Nomad asked: Would a normal user need to sign a transaction just to see their overall balance?

No. Reading balance is a lookup, not a spend action.

Users sign when they are authorizing movement of funds, such as a burn intent for a transfer. They do not need to sign just to read their balance.

abdelaziz moussaoui asked: What exactly does the balance endpoint return? Is it one unified number, or does it break down balances by chain? And does it include pending deposits?

The balance APIs expose chain-aware balance data rather than one opaque total.

 flow returns balances tied to the requested sources, and the response shape is 

. In other words, you can reason about balances per source chain.

Pending deposits should be treated separately from available balance. The docs do show 

 specifically for pending deposits, and the Unified Balance Kit documents 

 as returning confirmed and pending balance state across chains.

If you are building out a UI, it is better to show available balance and pending deposits separately rather than collapsing them into one number.

DeSeti DeSeti asked: If I'm building a payroll bot, does Gateway auto-handle destination gas when routing USDC from Arc to Solana, or do I need to fund it manually?

, Circle handles the destination-chain mint step for you, so you do not need native tokens on the destination chain for that mint flow. The relevant fees are included up front at burn time on the source side.

For Solana, there is one important caveat: the destination recipient must be a USDC token account, not just a wallet address. In supported flows, the Gateway Forwarding Service can create the Associated Token Account automatically when you include the right recipient setup options.

So the short answer is: with the Gateway Forwarding Service, Gateway can handle the destination-side mint path, but you still need to account for correct Solana recipient setup.

DeSeti DeSeti also asked: For multi-recipient payouts like payroll, does Gateway support batching natively, or do we need to build a custom relayer?

Gateway supports batching at the protocol level, but it is not a complete payroll abstraction out of the box.

On EVM, Gateway supports something called 

 with up to 16 burn intents when the source chains share the same signature scheme. That gives you a native batching primitive.

But a real payroll product still needs application logic around orchestration, retries, recipient management, and status tracking. So the right framing is: Gateway gives you batching primitives, while the payout workflow still lives at the app layer.

abdelaziz moussaoui also asked: Can an AI agent use the Unified Balance Kit to autonomously move USDC between chains based on where it needs to pay, without human approval for each transfer?

Circle Wallets explicitly position Developer-Controlled Wallets for backend payment flows, automated treasury operations, and AI agent wallets. That makes autonomous routing possible when your backend is allowed to authorize those actions.

That is different from user-controlled flows. In user-controlled setups, the user must authorize signing, so you would not describe those as autonomous crosschain movement without human approval.

Thank you all once again for spending your precious time with us, learning and geeking out over building actual USDC flows together. We will continue to do these technical Arcshops so please stay tuned.

Gateway FAQ Follow-Up: Answers We Didn't Get to Live

Home

Forum

Events

Content

Courses

People

Contributors

Albums

Groups

Chat

Channels

Not being used

Help

Join the global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make the economy work for everyone.

Arc House

Profession

Join a global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make that economy work for everyone. 

Arc House | Build the economic OS for the internet with us

Copyright

Terms of Service

Privacy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via noreply@arc.network if you need support.

Pending Approval

Login to the The Arc Community Hub community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community complete your profile using verifiable and real information.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Arc House.

Thanks for your interest in joining Arc House. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via noreply@arc.network for any questions.

Accounts are unapproved when profile information cannot be verified or when activity patterns indicate spam, inorganic participation, or behavior that undermines trust in the program.

To strengthen your profile for future consideration, sign in with a verified LinkedIn account, use real and current profile information, and participate constructively in other community spaces.

Commercial customers should raise concerns through their support channel.

https://www.arc.network/community-guidelines