Trusted agentic payment. Coming soon on Arc
ARC
Joined June 2026
- Tweets53
- Following7
- Followers159
- Likes84
You're selling API calls to agents and getting paid in USDC.
Now explain to your finance team how that becomes money in the company bank account.
Most x402 sellers don't have a clean answer. Revenue sits in a wallet. Someone manually bridges and off-ramps it. The audit trail breaks exactly at the boundary where finance needs it to hold.
Screening tells you the payment was safe to take. The rail is what turns it into banked revenue with the record intact.
That whole loop is on testnet now.
We're making the KYA attestation format open.
Any facilitator can verify @a402finance attestations for free. Any third-party service can query the Identity API.
The trust layer compounds in value when it's shared.
3/ What stays as the business:
Settlement fees. Fiat on/off-ramp. Premium KYA tiers with manual EDD.
The network effect is the product. Identity is the public good. Liquidity is the revenue engine.
2/ What's open:
→ The attestation format (published, free to verify)
→ The Identity API (public REST + GraphQL, queryable per wallet, no integration fees)
→ Any third-party facilitator can verify our attestations without touching @a402finance's settlement
1/ Why open it?
The same reason DNS works: a passport means nothing if only one country accepts it.
KYA IDs issued by @a402finance should be recognizable across the entire agentic payment ecosystem not locked to our settlement flow.
One month in, and our Early Access is officially OPEN!
Here is what you get right now when you build with @a402finance:
✦ Trust layer for AI agent payments on Arc
✦ KYA (Know Your Agent): verified identity for every agent wallet & on-chain Trust Tiers
✦ Cross-chain ingestion: Ethereum, Base, Arbitrum → Arc via CCTP V2
✦ Seamless Fiat loop: corporate bank → agent wallet → Arc revenue → bank again
✦ Open KYA attestations: queryable by any facilitator on @arc
If you're building a paid API or deploying an agent that spends money, claim your Early Access spot today👇
a402.finance/
a402 retweeted
Every builder we've met is standing in the same spot, great product, real agents paying them, and a launch held up by one question: who are we taking money from?
We built A402 so you never have to answer that with "we don't know."
You've done the hard part. Let us handle this one.
→ Early access is f open: a402.finance/
Every builder we've met is standing in the same spot, great product, real agents paying them, and a launch held up by one question: who are we taking money from?
We built A402 so you never have to answer that with "we don't know."
You've done the hard part. Let us handle this one.
→ Early access is f open: a402.finance/
Every payment through @a402finance produces an immutable audit log.
Wallet attestation ID. AML screen result. Source chain + tx hash. Beneficial owner (hashed). Travel Rule flag if triggered.
Exportable in under 30 seconds. FATF Recommendation 16 schema.
For the compliance officer who has to sign off on agentic payments: this is the paper trail.
The agentic payment loop has a fiat problem on both ends.
Developers fund agent wallets from corporate bank accounts.
No clean way to do that into a crypto wallet.
API providers accumulate USDC micro-revenues.
No purpose-built off-ramp for that pattern.
@a402finance closes both:
→ On-ramp: fund agent wallets via ACH, SEPA, or wire through Circle Mint
→ Off-ramp: set a payout schedule. USDC settles to your bank automatically same-day, next-day, or weekly.
Crypto comes in. Regular money lands in your bank.
No exchange detour. No manual withdrawal. Just revenue.
3/ If a cross-chain payment fails mid-flight, agent funds stay safe on the source chain.
No funds lost. Merchant notified. Clean retry path.
2/ The timing problem: cross-chain can't complete inside a synchronous 402 window.
So we ship a two-step model:
→ USDC burns on source chain
→ We issue the API provider a signed escrow commitment immediately burn proof included
→ API returns 200. Agent keeps running.
→ Arc mint completes in the background. Under 25 seconds.
1/ A402 closes this with CCTP V2 Fast Transfer.
Agents pay from USDC on any supported EVM chain.
We ingest, route cross-chain, settle on Arc.
The agent doesn't manage any of it.
How A402 Trust Tiers work:
🔹 Tier A Full KYC, volume thresholds, long clean history.
🔹 Tier B Wallet age >180 days + counterparty diversity.
🔹Tier C 90 days clean history.
🔹Tier D New wallet. Sanctions + AML screening passed. Probationary.
Every wallet starts at D. Every tier is earned on-chain.
API providers set the minimum tier they'll accept.
The middleware enforces it before payment signature is requested.
No more unknown callers.
x402 hit 165M transactions in 9 months.
69,000 active agents. ~$600M annualized volume.
The hard part is:
❓Who’s actually paying?
❓Is the wallet clean?
❓ How do we get the money back to fiat safely?
This is the missing trust layer for agents on @arc.
We’re building it with A402.
Early access is open at a402.finance/
5/ For agent developers, you verify once. That's it.
Your KYA ID travels with your wallet across every Arc-native API, automatically.
Higher trust tier = more APIs unlock. Better rates. No friction on every new integration.
Reputation compounds. Just like it should.
This is the trust layer @arc needs.
Early access is open. Come build the trust layer with us. → a402.finance
