How Stripe Money works

Stripe Money turns a token's creator fees into a payment to a website. Fees accrue in USDC, the same asset Arc uses for gas, so nothing is converted along the way.

1. 1

   The token is deployed through Argus

   Stripe Money calls the Argus Portal on Arc to launch the token, so the Stripe Money treasury is recorded as the launch's creator and receives its USDC tax share.
2. 2

   The creator names a website

   Only the domain. We request the site and look for a 402 answer backed by Stripe.
3. 3

   We claim on a schedule

   Argus credits the creator share in USDC; the treasury claims it on a schedule.
4. 4

   Every claim is split

   80% to the website, 20% to buy and burn $402.
5. 5

   The website is paid over 402

   An agent pays the site with x402: the site answers 402 with its terms, the agent signs a USDC authorization, and it settles on Arc through Circle Gateway. The money lands in the site's Stripe balance.

Tokens launch and pay out on Circle's Arc chain. Gas is paid in USDC.

Arc Mainnet

Live since September 16, 2026. Chain ID 5042, network eip155:5042.

Launchpad

Argus, through its Portal contract 0xB021Be536808f551b31789422Fd28a6c9c6e97Da.

Payout standard

x402, exact scheme, settled through Circle Gateway Nanopayments.

Every token on Stripe Money is deployed through Argus, the permissionless launchpad on Arc built on Uniswap v4 hooks. Stripe Money doesn't run its own launch contracts; it calls Argus's Portal for you.

Deploy

Stripe Money calls Portal.createLaunch. Argus clones the token, opens its Uniswap v4 pool and locks the liquidity in one transaction.

Creator

Argus records whoever calls createLaunch as the creator, so the Stripe Money treasury is the creator. The website you name is written into the launch's website field.

Fees

A fixed buy and sell tax is taken in USDC on every trade. Argus keeps 10%; the rest goes to the launch's creator allocation.

Claiming

Argus credits the creator share and doesn't push it. The treasury withdraws it with claim(to, USDC), then pays the website over x402.

Argus's contracts and docs are public on GitHub. Stripe Money is not affiliated with Argus.

The website is the only field that decides where money goes. Name, category and description are read from the site itself; the creator does not type them.

Normalization

Whatever is pasted is reduced to a bare domain: lowercased, with the scheme, a leading www., any path, query, fragment and port removed. So https://www.Substack.com/about?ref=x becomes substack.com. Input that isn't a valid domain is rejected.

What discovery checks

Request

We request the site and the paths it may use for payments.

402 answer

Whether it responds 402 Payment Required with payment requirements.

Backed by Stripe

Whether those requirements belong to a Stripe account. That makes the site a Stripe 402 site.

Otherwise

The site is marked no-402 and its share is held as owed. See Stripe 402 vs no 402.

Payouts use x402, the open standard for paying over HTTP 402. On Arc it settles in USDC through Circle Gateway Nanopayments: the payer signs an EIP-3009 TransferWithAuthorization (the exact scheme), so the transfer itself costs no gas. There is no account to connect and no key to share; the site's own endpoint says how it wants to be paid.

1. 1

   Request

   Our agent requests the site's 402 endpoint.
2. 2

   402 Payment Required

   The site answers 402 with a PAYMENT-REQUIRED header: the amount, the asset (USDC), the network (eip155:5042) and where to pay.
3. 3

   Sign and retry

   The agent signs an EIP-3009 TransferWithAuthorization for that amount and retries the same request with it in the PAYMENT-SIGNATURE header.
4. 4

   Settle on Arc

   The site, or a facilitator it uses, settles the authorization in USDC on Arc through Circle Gateway and answers 200 with a PAYMENT-RESPONSE header.
5. 5

   Stripe settles

   The site's Stripe creates a PaymentIntent, with the payment note as its description. The money lands in the site's Stripe balance.

# 1. requestGET https://photoai.com/ # 2. the site answers with its termsHTTP/1.1 402 Payment RequiredPAYMENT-REQUIRED: { scheme: "exact", network: "eip155:5042",  asset: USDC, amount: "5.00", payTo: "0x…" } # 3. sign an EIP-3009 authorization, retry with itGET https://photoai.com/PAYMENT-SIGNATURE: <TransferWithAuthorization, signed> # 4. settled on Arc via Circle Gateway; Stripe records itHTTP/1.1 200 OKPAYMENT-RESPONSE: { success: true, network: "eip155:5042" }{ "payment_intent": "pi_3…", "description": "Creator fees via @stripemoney" }

Any website can be named. What happens to its share depends on what discovery found.

Stripe 402

Paid on each claim, once its share reaches the minimum payout.

No 402

Nothing is sent. The share accrues as Owed on the site's page.

Turning 402 on

The whole owed balance is paid on the first claim after the site starts answering 402.

Each token carries a payment note, up to 250 characters. It becomes the description on the PaymentIntent the site's Stripe creates, so it is what the website sees next to the money. The default is Creator fees via @stripemoney.

Every claim is split the same way, on every token.

80% · website

Paid over 402 to the named website, or held as owed if it has no 402 endpoint.

20% · buyback

Buys $402 and burns it. See $402 buyback and burn.

Creator fees do not arrive continuously. They accrue on the token and we claim them into the treasury on a schedule. Each claim appears in the ledger with its Arc transaction and its split.

Payouts under 5 USDC wait. A site's share keeps building across claims until it reaches 5 USDC, because a 402 round trip for less costs more than it carries.

There are three ways to point a token at a website. All three end in the same place: the creator USDC reaches the treasury and is paid on to the website. Open Launch.

Launch

Stripe Money deploys the token through the Argus Portal, so the treasury is the creator from the first trade.

Register

For a token already launched on Argus. Argus fixes the creator at launch, so you stay the creator, name the website here and claim to the treasury.

Walletless

No sign-in on this site. Put the website line in the token description, then claim the creator USDC to the treasury from the wallet that launched it.

Walletless line

A wallet is only needed to launch or register a token. Arc is an EVM chain, so any EVM wallet works. Walletless mode needs no connection here at all.

Chain

Arc, EVM-compatible.

Discovery

Installed wallets announce themselves through EIP-6963, so each appears by name in Connect wallet.

Gas

Paid in USDC. No separate gas token is needed.

The 20% share of every claim buys $402 on Arc with USDC and sends it to the burn address. Buys in progress show as Buying; completed ones show the amount burned and link to the transaction. Totals are on Analytics.

Token

0x0000000000000000000000000000000000000000

Funded by

20% of every claim, in USDC.

Split

80% website, 20% buyback and burn.

Minimum payout

5 USDC. Smaller shares wait for later claims.

Payment note

Up to 250 characters.

Network gas

Paid in USDC on Arc.

Stripe fees

Whatever the website's own Stripe account is charged on its payments. Set by Stripe and the site, not by us.

Pointing a token's creator fees at the Stripe Money treasury is a choice made by whoever controls the token. By doing so, and by naming a website, they direct those fees to be claimed and split as described on this page.

The site and the protocol are provided as is. Payouts depend on Arc, on each website's 402 endpoint and on Stripe, none of which we control. Nothing here is investment advice, and $402 is not an investment product.

Stripe Money is not affiliated with, endorsed by or sponsored by Stripe, Inc. or Circle Internet Group. Stripe, Arc and USDC are trademarks of their respective owners.

Sample data. Websites, tokens, payments, claims, buybacks and totals shown across this site are fictional sample data used to render the product before the indexer is connected.