How Stripe Money works

Stripe Money turns a token's creator fees into a payment to a website. pump.fun pays creator fees in SOL, so fees arrive as SOL on Solana and are never exposed to the price of the token that earned them.

1. 1

   The token is launched on pump.fun

   The creator's wallet launches the token on pump.fun with its creator fee recipient set to a fee vault that belongs to that coin alone.
2. 2

   The creator names a website

   Only the domain. The website claims its payouts once by verifying the domain and choosing where the money goes.
3. 3

   Fees: we claim on a schedule

   pump.fun accrues the creator share in SOL, credited to the coin's vault. The vault claims it into the payout wallet.
4. 4

   Every claim is split

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

   Sending, then Delivered

   The SOL is swapped to USDC and paid to the destination the website chose: its bank account through Stripe Global Payouts, its Stripe account, or a SOL wallet. It counts as Delivered once it arrives. See From SOL fees to the website.

Tokens launch and pay out on Solana. Network fees are paid in SOL. Fees are collected in SOL; payouts to Stripe leave as USDC on Solana.

Solana

Mainnet-beta. Network solana:mainnet, explorer Solscan.

Fee asset

SOL, 9 decimals (lamports). Creator fees are native SOL, never the launched token.

Launchpad

pump.fun. Other launchpads are coming soon.

Payouts

SOL swapped to USDC on Solana with Jupiter, then paid to the website's bank (Stripe Global Payouts), Stripe balance (Global Payouts) or SOL wallet.

Every token on Stripe Money is launched on pump.fun, the launchpad on Solana. A launch sells from a bonding curve; when the curve completes it graduates to PumpSwap with the liquidity locked. Stripe Money doesn't run its own launchpad; the only programs it adds are the fee vaults.

Deploy

The creator's wallet creates the token on pump.fun with its name, ticker and image, and with the creator fee recipient set to the coin's fee vault.

Fees

Each trade pays the pump.fun fee in SOL. pump.fun takes its protocol share first; the creator share goes to the creator fee recipient, on the curve and after graduation.

Claiming

One instruction, collect_creator_fee, is signed by each vault and forwards the SOL to the payout wallet, which runs the payout pipeline below.

Existing tokens

A creator can point an existing pump.fun token at a website by setting its creator fee recipient to the vault address the Register tab gives them.

Stripe Money is not affiliated with pump.fun or Solana.

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 the live check shows

Stripe on the site

We fetch the site and look for Stripe.js, Checkout, Payment Links or pricing tables. It is shown as evidence, alongside a Stripe customer story where one exists.

402 endpoint

Whether the site answers 402 Payment Required. Shown for information; payouts don't depend on it.

Who gets paid

Neither check pays anyone. Money only moves once the website claims its payouts. See How a website claims its payouts.

Every coin's money moves through three stages, shown on every token and website page: Fees, Sending, Delivered. Delivered means the money has arrived where the website chose to be paid: its bank account, its Stripe account or its SOL wallet. Every step leaves an ID that is stored against the payout.

1. Fees: collected and claimed on Solana

1. 1

   Launch

   Before signing, Stripe Money allocates the coin a fee vault: a program-derived address that is known before the token exists. The creator's wallet creates the token with that vault as its creator fee recipient.
2. 2

   Accrue

   Each trade pays the creator share in SOL to the vault's creator account, on the bonding curve and on PumpSwap after graduation.
3. 3

   Claim

   Anyone can crank collect(coinId); each vault claims its creator fees and forwards everything to the payout wallet, emitting Forwarded(coinId, SOL, amount). Only the treasury multisig can change the one payout wallet all vaults forward to. A claim is booked once its slot is finalized, keyed by signature so it can never be counted twice.

2. Sending: SOL to USDC

Banks and Stripe take dollars, not SOL, so each batch is swapped to USDC on Solana in one transaction. There is no bridge and no wait for finality on another chain.

1. 1

   Batch

   Payouts are batched once a day per website, and only once the website's balance clears the minimum payout.
2. 2

   Swap to USDC

   The payout wallet swaps the batch through Jupiter. The output amount is quoted before the transaction is signed, and the batch is skipped if the quote is below the slippage limit.
3. 3

   Route by payout method

   A website paid in SOL gets it straight from the payout wallet with no swap. Everything else is deposited to Stripe Money's Stripe financial account deposit address on Solana and credited to its USDC balance, usually within minutes.

3. Delivered: paid to the destination the website chose

Bank account

The default. Stripe Global Payouts sends dollars from the financial account with POST /v2/money_management/outbound_payments to the website's recipient account. US banks: typically 0 to 1 business days. 160+ other countries: local currency, typically 1 to 7 days. The website doesn't need a Stripe account.

Stripe account

For websites that want the money next to their sales. Where Stripe offers it, they pick their Stripe balance in the same Stripe-hosted form.

SOL wallet

SOL on Solana, sent straight from the payout wallet. Seconds, with no Stripe step.

Delivered

Marked when the outbound payment is posted, or when the SOL transfer to the wallet is finalized. The ID is shown on the payout.

# feesaccrue      Solana tx 5Kx… · creator fee → vaultclaim       vault.collect() · Forwarded(coinId, SOL, 0.500) · 0.400 to the website# sendingswap        Jupiter 3Fq… · 0.400 SOL → 79.94 USDC on Solanadeposit     Stripe financial account · 79.94 USDC credited# deliveredpayout      outbound_payment obp_… → recipient acct_… · bank ••6789

Timing

Claims and swaps settle in seconds. SOL wallets are paid within minutes of the batch. Stripe deposits take minutes; bank payouts arrive in 0 to 1 business days in the US and 1 to 7 days elsewhere.

Costs

Solana network fees, the swap price impact, and any Stripe payout or FX fee come out of the batch. That is why payouts under 0.05 SOL wait.

Failures

Each step saves its ID before the next one runs, and Stripe calls use the batch ID as the idempotency key, so a retry never pays twice. A failed swap leaves the SOL in the payout wallet; a returned bank payout goes back to the financial account and the website is asked to fix its details.

Nobody can push money into a Stripe account by knowing its account ID, and naming a domain doesn't prove who owns it. So a website claims its payouts once. Until then its share is recorded as Owed and stays in SOL.

1. 1

   Prove the domain

   Add a DNS TXT record striped-verification=… to the domain, or serve the same value at /.well-known/striped.txt. This stops anyone other than the site's owner from claiming its money.
2. 2

   Choose where to be paid

   Either a Stripe-hosted form collects the payout details (a bank account, debit card or Stripe balance through Stripe Global Payouts; no Stripe account needed), or the website enters a Solana wallet address. Stripe Money never sees bank numbers.
3. 3

   Get paid

   The whole owed balance goes out in the next daily batch, and every later claim follows automatically.

x402 is an open standard for paying over HTTP: a server answers 402 Payment Required with its terms, the client signs a payment and retries. It moves stablecoins; it doesn't convert them to dollars. Stripe Money doesn't pay websites over x402, for the reasons below.

Stripe's x402

The merchant runs the server. Its 402 response names a Stripe deposit address, the payment settles through a facilitator, and the merchant records it in Stripe as a PaymentIntent. Stripe accepts USDC on Base, Solana and Tempo for this.

Why we don't use it for payouts

An x402 endpoint charges its own price for its own resource. A fee batch is an arbitrary amount, so it can't be paid through someone else's endpoint without buying something. Global Payouts and wallet transfers send the exact amount.

On Solana

x402 works with USDC on Solana, but not with SOL. Stripe doesn't accept SOL, so fees must be swapped to USDC before they can land in a Stripe account.

Any website can be named. What happens to its share depends on what the website has set up.

Bank

Domain verified, bank account added through Stripe Global Payouts. Paid in its local currency after each daily batch.

Stripe

Domain verified, Stripe balance chosen in the hosted form. Paid into its Stripe balance.

SOL

Domain verified, Solana wallet added. Paid in SOL within minutes of each batch.

Owed

Not claimed yet. The share stays in SOL and is listed on the site's page until the site claims it.

These are the approvals and accounts the payout pipeline depends on. pump.fun is live today. Fee vaults and payouts start once all of these are in place.

Stripe Global Payouts

A US or UK entity with a Stripe financial account, approved for this use case. Payouts from a USDC balance are in public preview in the US.

Money transmission

Holding and forwarding other people's fees is regulated. The operating entity needs the registrations and licences its lawyers confirm, such as FinCEN MSB registration and state licences.

pump.fun

Creator fee claims depend on pump.fun's creator fee instructions remaining available.

Infrastructure

A production Solana RPC provider (the public endpoint is rate-limited), a multisig treasury with a limited payout wallet, sanctions screening on every recipient and wallet, 1099 or equivalent tax reporting, and an idempotent payout ledger.

Each token carries a payment note, up to 250 characters. It is stored with the coin and shown on its page. When a website's daily payout comes from a single coin, the payout carries that coin's note as its Stripe description; a payout that combines several coins uses the default note, Creator fees via @StripeMoneyApp.

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

80% · website

Paid to the named website's bank, Stripe balance or wallet, or held as owed until the website claims it.

20% · buyback

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

Creator fees do not arrive continuously. They accrue on the token and each coin's vault is claimed every few minutes. Each claim appears in the ledger with its Solana transaction and its split.

Payouts under 0.05 SOL wait. A site's share keeps building across claims until it reaches 0.05 SOL, because the network and swap costs of sending less would eat most of it.

Tokens are launched from the Launch page with a connected wallet. The coin's creator fees go to its own fee vault from the first trade and are paid on to the website it names.

Website

Required. The website that receives the coin's share, picked from the directory of 597 merchants or typed as any domain.

Name and ticker

Required. Up to 32 characters for the name and 10 letters or digits for the ticker.

Image and description

Optional. Shown on pump.fun and on the token's page.

Social links

Optional: website, X and Telegram, passed to pump.fun with the token's details. With no website, the token's Stripe Money page is used.

Payment note

Optional. Up to 250 characters. Used as the payout's Stripe description when a payout comes from this coin alone.

Dev buy

Optional. Buys your own token at launch, before anyone else, paid in SOL.

Fee vault

Set automatically as the creator fee recipient. Fees credited to any other address can't be traced to a website and aren't paid out.

Register

For a token already on pump.fun. Name the website, enter the token's mint address, then set its creator fee recipient to the fee vault. Check confirms the vault is receiving the fees.

A wallet is needed to launch a token. Any Solana wallet works.

Chain

Solana mainnet.

Connection

Installed wallets are detected; Phantom, Solflare, Backpack and WalletConnect are offered.

Network fees

Paid in SOL. Launching a token needs a small amount of SOL.

The 20% share of every claim goes to the buyback wallet, which buys $STRIPED on Solana with SOL and burns it. Buys in progress show as Buying; completed ones show the amount burned and link to the transaction. Totals are on Analytics.

Token

$STRIPED · mint address coming soon

Funded by

20% of every claim, in SOL.

Split

80% website, 20% buyback and burn.

Minimum payout

0.05 SOL. Smaller shares wait for later claims.

Payment note

Up to 250 characters.

Network fees

Paid in SOL on Solana, plus swap price impact, out of each batch.

Stripe fees

Stripe's payout and FX fees on the payout method the website chose.

Pointing a token's creator fees at a Stripe Money fee vault 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 Solana, pump.fun, Jupiter, Stripe and each website claiming its payouts, none of which we control. Nothing here is investment advice, and $STRIPED is not an investment product.

Stripe Money is not affiliated with, endorsed by or sponsored by Stripe, Inc., Solana, pump.fun or Jupiter. Stripe, Solana and pump.fun are trademarks of their respective owners.

Directory and figures. Websites in the merchant directory are real businesses and people listed because public evidence shows they take payments with Stripe; none of them have opted in. Tokens, payments, claims, buybacks and totals show zero until the indexer is connected.