Every fee has a destination

A token creates the opportunity. The contract records the allocation. A payment provider completes the journey to the recipient.

M Recipient@maria_k
Recipient allocation · example
$80.00
Payout route
PAYPALUSD · PayPal Payouts
Payout route
VENMOUSD · by phone
Payout route
WISEEUR · SEPA
Register Launch Harvest Paid
Recipient pool
$80.0080%
Protocol
$20.0020%
The journey01

From a token to a payment, in five stages.

Recipient01-1

A recipient, with a defined route.

Start with the person you want to pay, then pick a route. PayPal and Venmo use account identifiers; bank and debit-card routes use provider-issued references.

  • Private details stay in an encrypted off-chain vault.
  • The contract stores an alias, a method ID and an opaque reference.
  • Accounts are reviewed before live payouts.
Register a recipient
Recipient registration⋯
PayPalVenmoWise
maria@example.com

Recipient details are encrypted and kept off chain.

struct SettlementRoute { uint8 method; bytes32 recipientRef; }
Saved recipientsSave recipient
Token01-2

Your token. A lasting fee route.

Choose the name, ticker, artwork and an optional creator tax. The contract calls the pons factory and becomes the token’s creator fee recipient for good.

  • creatorFeeRecipient: address(this)
  • No function exists to transfer that destination.
  • Launch fee 0.0005 ETH plus gas; first buy optional.
Create token
Launch summary⋯
MMaria Fund$MARIA
Recipient
maria@ex…com
Settlement method
PayPal
Trading fee
1% + 2.0% tax
Recipient earns
2.16% of volume
Recipient80%Protocol20%
Allocation01-3

The 80/20 rule, in the contract.

A harvest claims available creator fees from the pons escrow. Anyone can call it. It moves funds into the contract and updates its accounting; it does not send a fiat payment.

  • uint256 r = amount * RECIPIENT_BPS / BPS;
  • A do-not-pay alias sends its share to treasury.
  • Unattributed sweeps get the same split.
Read the rule
M Recipient@maria_k
Recipient allocation · example
$80.00
Payout route
PAYPALUSD · PayPal Payouts
Payout route
VENMOUSD · by phone
Payout route
WISEEUR · SEPA
Register Launch Harvest Paid
Recipient pool
$80.0080%
Protocol
$20.0020%
Payment states02

Two records, two different meanings.

A contract event proves fees were allocated on chain. A confirmed provider payment records the outbound settlement.

01 — Allocated

Credited on chain

Fees have been booked. Some or all of the balance may still be waiting for the next payout milestone.

02 — Pending

Funds reserved

A payment has reserved its funds and awaits a confirmed outcome. Provider acceptance alone is not completion.

03 — Paid

Provider confirmed

The provider confirmed the outbound payment. Simulation and sandbox runs are labelled apart and never counted.

Settlement03

An allocation becomes a payment.

When it becomes eligible

Paid at each milestone

The keeper values collected fees in USD and tracks each alias’s lifetime credits. $5, $10, $20, $50, $100, $250, $500, $1,000, then every $1,000. Crossing one makes the full unpaid balance eligible.

Read the guide
Next milestone$
Credited$7.00Milestone$10.00
Who funds it

The operator pays out

Only the owner can withdraw the recipient pool. They convert it through an approved off-ramp and fund the provider. Recipients rely on the operator; there is no self-withdrawal.

Capital flow
Recipient pool—Held in ETH80%
FAQs10

Questions,
answered clearly.

Fees, recipients, routes and payouts, explained before you launch.

The split applies to creator fees actually collected by the contract. Trade volume, token price and supply are separate quantities. Fees depend on trading activity and the launch terms; launching a token does not guarantee revenue.

The contract fixes a settlement method and recipient reference for each alias when it is first used. Later launches with that alias must match the same route. A different destination needs a new reference and alias for a new launch; it does not reroute fees from existing tokens.

No. The payout goes to the recipient’s approved provider account. The creator connects a wallet to register the recipient and launch. A creator’s signature does not prove ownership of someone else’s payment account, so recipients are reviewed before live payouts.

The next lifetime milestone may not be reached yet, the recipient may be awaiting review or suspended, or the provider may lack funding or eligibility. A payment in progress also reserves its allocation until its outcome is reconciled.

Each method shows its live status. A listed route still depends on provider setup, country, currency and account approval. PayPay is simulation-only for now. Simulation and sandbox activity never count as real payouts.

The keeper keeps the request and reserves the funds for reconciliation. Retries use the same request identity. An uncertain response is never treated as proof that no money moved, and it does not release those funds to the treasury.

Get startednow

Give your token
a destination.

One alias
One fixed route
Every harvest

Starting from

2% tax

Charged on every trade on top of the 1% pons fee, and paid to the contract. The recipient earns 2.16% of volume.

No wallet needed on the other endpons launch fee 0.0005 ETH + gasPayouts from $5 after verification
Create token
MRecipient@maria_k
Recipient allocation · example
$80.00
Payout route
PAYPALUSD · PayPal Payouts
Payout route
VENMOUSD · by phone
Payout route
WISEEUR · SEPA
RegisterLaunchHarvestPaid
Recipient pool
$80.0080%
Protocol
$20.0020%