anypayCapital flow
The contract records allocation; the operator handles withdrawal and provider funding. Read the contract rules and settlement explanation →
- Trades on pons 1% fee + creator tax
- pons escrow 70% of fee + tax
- AnyPay contract harvest and split
- Funded fiat off-ramp
- Payment provider settlement
- Recipient account
- AnyPay treasury
Tokens launch on pons.family through the AnyPay contract, which is set as each token's permanent creator fee recipient. pons only lets the current recipient hand fees on, and AnyPay has no function that does.
Every trade pays pons' 1% fee. 30% goes to pons and 70% is credited to AnyPay in the pons escrow, along with any creator tax the launcher chose (up to 10%, all of it to AnyPay).
Harvest sweeps each token's pending fees, claims the escrow and splits it once: 80% to the contract payout pool, 20% to the AnyPay treasury. Per-token allocations emit FeesAttributed; pre-swept escrow fees emit UnattributedClaimed for keeper reconciliation. Blocked aliases have their future attributed share redirected to treasury.
The owner withdraws payout funds for an approved off-ramp. Fiat provider balances must be funded before payments can complete.
At a payout milestone, the keeper uses the selected provider and a stable request ID. A payment is completed only after provider confirmation.
Accrued fees, claimed funds, conversion and completed payouts are separate stages, and each is recorded against the claim that produced it.