1. Fee flow

A token is associated with a social identity (X) at launch or afterwards. When that token generates creator fees on-chain, an indexer records a fee event: source mint, transaction signature and the amount credited to the recipient. PAY deducts no protocol share.

Each event is keyed by its transaction signature. Re-delivery of the same signature is ignored, so replays and indexer retries cannot double-credit or double-pay a recipient.

2. Routing

A recipient's routing configuration is a set of destination splits that must total exactly 100%. The destinations available today are holding in SOL, withdrawing to a Solana wallet, a charity, or another recipient handle for creator/artist/community splits. Token buyback, burn and X Money payouts are not offered; they remain in the data model only so historical records stay readable.

Routing is evaluated per fee event. Changing routing never rewrites already-processed events.

2b. Who owns creator fees

PAY takes 0% of creator fees. 100% of the creator-fee amount credited to PAY goes to the selected social recipient. Network and pump.fun protocol costs are charged on-chain and are outside PAY's control — PAY cannot waive them and does not add anything on top.

• Launching a coin for someone does not give the launcher any claim on its creator fees, unless the launcher is also the selected recipient.
• The PAY launch wallet is infrastructure that signs and funds launch transactions. It is never the beneficial owner of creator fees.
• Unclaimed creator fees stay attributable to the canonical social identity indefinitely. They are never swept to PAY.
• Claiming requires proving ownership of that social account through the platform's official sign-in, then settling to a wallet the owner controls.

3. Payout statuses

• Pending — attributed and queued for a rail.
• Processing — handed to a payout adapter.
• Paid — the adapter confirmed delivery.
• Claimable — the rail failed or isn't configured; the funds stay attributed to the recipient.
• Failed — a terminal adapter error; the balance becomes claimable, never swept.

4. Claims and fallback

If an off-chain payout cannot be delivered — no X Money account, a rejected transfer, a disabled adapter — the amount remains attributable to the intended recipient. It is never redirected to the protocol treasury.

To claim, the recipient signs in, verifies ownership of the handle, connects a Solana wallet and requests settlement of the claimable balance to that wallet.

5. Security assumptions

• PAY never asks for, stores, logs or displays private keys or seed phrases.
• Withdrawals are user-signed, or executed by explicitly configured server infrastructure — never by pasted keys.
• Row-level security scopes recipient data to its owner; admin actions require an assigned role and are written to an audit log.
• Event ingestion and payout execution are idempotent and replay-protected.

6. Launch pricing

PAY charges a 0 SOL platform fee to create a coin and adds no surcharge on top of pump.fun, which itself lists coin creation at 0 SOL.

Every launch is funded by the launcher: you send your dev buy — SOL spent buying your own token at launch — to PAY's launch wallet, as an exact amount unique to your launch. For a larger dev buy you also give a Solana address for delivery; the purchased tokens are yours and PAY takes no cut of them. The deposit also includes 0.02 SOL to cover the Solana network cost of creating the coin, so PAY pays nothing toward your launch. Creator fees stay separate and belong to the social recipient identity.

7. Economics

PAY's creator-fee cut is 0%. Creator fees detected for a coin are credited to the selected social identity in the exact amount detected, with no protocol share deducted. The protocol fee column that appears on older historical ledger rows is legacy data and is not applied to live creator-fee settlement.

8. Status of this deployment

Payments, launches and creator-fee records shown in PAY are real Solana mainnet activity — nothing is simulated. See integrations for the exact status of each adapter.