fee routing for pump launches

Pick where the fees land.

Flume launches your coin on Pump and lets you choose where its creator fees go before the first trade. Send them to a wallet, an X account, a PayPal email, a TikTok profile, an inbox, or split them. The route is public from the start, and every state after that is shown as the backend reports it.

wallet = baselineroute = publicprotocol fees = untouched
SIGNAL...
SHARE—

Wallet: checking. No fees are flowing.

Illustrative device. The coin, recipients and moving dots are examples, not live transactions. Only the status readout comes from the API.
How it runs

Three steps, one route.

You decide the destination once, at creation. After that the page for your coin shows where fees are pointed and what has happened to them.

  1. 01

    Launch = a coin on Pump

    Name the coin, give it a ticker and a picture. It is created on Pump like any other launch.

  2. 02

    Choose a route = one destination or a split

    Pick where the creator fees go before the coin exists. The route is on the token page from the first trade.

  3. 03

    Get paid = claimed, not pushed

    Fees accrue as the coin trades. The recipient claims them, and every state on the way is shown as reported.

Destinations

Six places fees can go.

A wallet is the baseline. The rest depend on a payout provider, and each one shows the status the API reports right now, nothing more optimistic.

  • Checking

    Wallet

    Fees go straight to a Solana address. The baseline route.

  • Checking

    X

    Fees are held for an X account until its owner claims them.

  • Checking

    PayPal

    A Solana wallet is reserved for a PayPal email.

  • Checking

    TikTok

    Claimed later by putting a code in the profile bio.

  • Checking

    Email

    Fees are held for a recipient who has been onboarded by email.

  • Checking

    Split

    Fees are divided between several destinations by percentage.

Status is polled from the API and shown unchanged. A destination that is not reported as available cannot be chosen at launch. Protocol and liquidity fees are never redirected. Wallet fees accrue to the creator vault and are claimed by the recipient; they are not sent automatically.

Board

What the API reports.

Counts and recent routing events, straight from the backend. A figure that has not been reported stays a dash; it is never filled in with a zero.

Coins launched—through this launchpad
Routes active—active or paid
Routing events—recorded so far
Destinations open—reported available
Latest routing eventsall activity

—Loading routing events

Simulator

Split it and see.

Set a day of creator fees and divide it. This is arithmetic on numbers you choose, to show how a split behaves. It is not a forecast.

4.0 SOL

Split

  • %
  • %
  • %

total 100%

Each destination receives, per day

  • Wallet2.000 SOL
    share50%
  • X1.200 SOL
    share30%
  • Email0.800 SOL
    share20%
per day4.0 SOL
per week28.0 SOL
largest shareWallet

simulation · illustrative, not live data. Real creator fees depend on trading and arrive unevenly. Protocol and liquidity fees are not part of this number.

FAQ

Questions.

Are fees sent to the recipient automatically?

No. For a wallet route, creator fees accrue to the creator vault and the recipient claims them. Nothing is pushed to a wallet on its own.

Which fees does a route cover?

Creator fees only. Protocol fees and liquidity fees are never redirected, whatever route is chosen.

What does “unavailable” mean on a destination?

The backend is not reporting a working payout provider for it. It cannot be chosen at launch until that changes. The status shown is whatever the API last answered.

How does someone claim fees routed to X, TikTok, email or PayPal?

A Solana wallet is reserved for that identity. The owner proves the identity on the Claim page: by signing in to X, putting a code in a TikTok bio, or confirming an email or PayPal address.

What if the recipient never claims?

Unclaimed fees stay where they accrued until the recipient claims them.

How does a split work?

You list two to six destinations with a percentage each. The percentages must total exactly 100, and every destination in the split must be available.

Is what I see on this site live?

Not in this build. The coins, amounts and transactions are fixtures from a mock API, and launching, claiming and payouts are not implemented. The device and the simulator are illustrations in any build.

Ready

Set the route before block one.

The destination is part of the launch, so there is no period where fees go somewhere unannounced. Launching and trading tokens carries a risk of total loss. Nothing on this site is financial advice.