anypayTHE ANYPAY GUIDE
From a trade to a payment.
A clear record of where creator fees come from, how they are divided and what happens before they reach a recipient.
Read the illustrated guide with contract excerpts →
Launch
A token is created on pons.family with anypay as its creator fee recipient. The creator chooses any third-party recipient, a settlement method and an immutable private account reference. Only tokens launched through anypay appear here.
Fees and the 80/20 split
pons credits the creator portion of trading fees to its escrow. anypay harvests that balance into two on-chain pools: 80% for recipients and 20% for the protocol. These funds stay in the contract until the owner withdraws them. The split applies to collected creator fees, not to total trade volume.
Recipient details
PayPal email addresses and Venmo phone numbers are stored in an encrypted private vault. Bank and debit-card routes use payment-provider account references. Raw card numbers and bank details are not collected here. Public activity uses an opaque recipient alias. A new destination or method requires a new reference.
Settlement
The keeper values harvested fees in USD. Milestones begin at $5, $10, $20, $50, $100, $250, $500 and $1,000, then every $1,000. The complete unpaid balance, rounded down to cents, is allocated when a milestone is crossed. Provider processing fees and currency conversion can reduce the amount received.
Payment states
Pending means funds are reserved and the provider has not confirmed completion. Paid means the provider has confirmed the outbound payment; bank availability can still depend on the destination. Simulation and sandbox results are labelled and excluded from real payout totals. Unknown outcomes stay reserved for reconciliation, with the same request ID on retries.
Supported methods
PayPal, PayPay, Venmo, ACH, bank wire, SEPA, local bank transfer, debit card and Wise. PayPal/Venmo use PayPal Payouts; bank routes use Wise; eligible debit cards use Stripe Connect. PayPay is simulation-only until a separate payout partnership is integrated. Availability requires country, currency, business and recipient eligibility.
Funding
Smart contracts cannot send fiat payments. The operator withdraws the payout pool, converts funds through an approved off-ramp and funds the provider balance. The existing Kraken adapter is optional and requires an eligible deposit network, verified account and withdrawal destination. The platform does not automatically bridge Robinhood Chain ETH to another network.
Owner controls
The owner can pause new launches, disable launch methods, manage keepers, block recipient aliases, withdraw either ETH pool and recover any ETH or ERC-20 token in an emergency. Emergency ETH withdrawals consume unaccounted ETH, then treasury and then recipient funds. These powers are visible on chain; this is a custodial settlement model.
Before production
Contract deployment, a running keeper, verified merchant accounts, funded fiat balances, recipient verification and provider acceptance tests are all required. Simulation is the default. No provider is activated merely by deploying the contract. Keep production and simulation ledgers separate.
Stop payments
The operator can suspend a recipient in the admin console. Existing do-not-pay contract controls redirect future fees to treasury. Recipient inquiries must be handled through the operator’s published support channel before launch.