Stage 5: Payment Simulatorinteractive
- 0 · Roadmap
- 1 · Receipts & warranty
- 2 · Creator royalties
- 3 · B2B invoices
- 4 · Payments bridge
- 5 · Simulator
- 6 · Devnet: repeat it
- ✓ · Trust chain
- ★ · Benefits & use
Models become useful when they meet real numbers. Enter your shop's volume, card terms and chain costs, and the simulator compares the monthly cost and the money waiting for settlement. Every formula is shown, nothing is sent anywhere: the calculation runs in your browser.
Your numbers
Change any field. The defaults are illustrative, not a quote from any provider: replace them with your own contract terms and today's prices.
| Per month | Cards | On-chain (Solana Pay) |
|---|---|---|
| Revenue | ||
| Payment fees | ||
| Chargeback costs | ||
| Total cost | ||
| Cost per order | ||
| Money waiting for settlement |
The formulas
- Revenue = orders × average order.
- Card payment fees = revenue × card fee % + orders × fixed fee.
- Chargeback costs = orders × chargeback rate × (average order + fee per chargeback).
- On-chain fees = orders × network fee in SOL × SOL price + revenue × conversion %.
- Money waiting for settlement = revenue ÷ 30 × settlement days.
What the simulator leaves out
- Setup, integration, compliance and licensing costs.
- How many of your customers already hold a Solana wallet.
- The buyer-protection value of chargebacks, which is real for customers.
- Price movement of non-stable tokens between payment and conversion.
The point is not that one rail always wins. The point is to replace opinions with numbers you can check, and then test the winner on devnet with Stage 4.
Wen in pictures
Where Wen fits in this model
If a shop accepts WEN as one payment option, volatility matters: set the conversion field to your real conversion cost and remember that the value of a WEN payment can move between receipt and conversion. Stable pricing belongs to stablecoins; WEN brings community and attention to the checkout.
The Wen thread: one contract, everywhere
Every model in the Lab is free and open, and every one carries the same signature: the $WEN token contract. Copy it, repeat it in your own docs, and always verify it against an explorer before use.
WENWENvqqNya429ubCdR81ZmD69brwQaaBYY6p3LCpk
Open use policy
- Free and open. All Lab code is released under the Apache License 2.0, the same license as the Wen Program Library. Use it, change it, ship it, commercially or not; keep the license notice.
- Open tools only. Built on public, documented tools: Solana SPL Token-2022 (Token Extensions), the token layout of the Wen New Standard (WNS), Solana Pay, and LiteSVM for local testing.
- The rule: always verify your own model. Run the tests, start on devnet, read the official documentation, review every account and amount, and get an independent audit before any mainnet use. A model that is not checked is not a model, it is a guess.
- Not audited, not advice. These are educational examples. They are not financial, legal or tax advice, and not a licensed payment or banking product. Payments, stablecoins and acquiring are regulated activities in most countries.
- Security. Never paste a private key into a website. Do not install the npm package
@wen-community/wen-new-standard: npm removed it as malicious. Build from official sources.
Spoken by Wen, for the community. More in our editorial and data policy.
Wen Open Lab · roadmap · all code · Wen Program Library on GitHub