🏪 Receive (merchant)
- 1Enter your receiving wallet address
- 2Pick the amount, token and chain
- 3Print the QR for the register, or show it from a phone / tablet screen
Start with just one wallet address
JPYC / USDC QR payments
Smooth wallet payments for stores. The merchant shows a QR with the amount baked in, and the customer just scans and signs. Cross-chain USDC payments arrive automatically too.
📱 Pay (Scan)
Connect a wallet, scan a merchant QR, and pay instantly.
Scan to pay →🏪 Receive (Create payment QR)
Just enter a recipient address and amount — generates a printable payment QR.
Create a QR →Market rate (reference)Fetching rate…
Why OpenPay
No sign-up, no custody. A payment experience that needs nothing more than a wallet.
Gasless payments
When the merchant picks gasless mode while building the QR, customers can pay with just JPYC / USDC — no POL or ETH needed. For JPYC, OpenPay bears the network fee in full and collects nothing from the customer or merchant. For USDC, the customer pays gas in USDC via the paymaster (OpenPay collects 0). For cross-chain payments from a different source chain, the source chain's network fee is still paid by the customer.
Technical detail: Pimlico / ERC-4337 paymaster
Multi-chain
Receive JPYC on Polygon / Kaia, USDC on Base / Arbitrum / Optimism / Polygon / Ethereum / Avalanche. Circle CCTP V2 handles cross-chain USDC payments automatically.
Non-custodial by design
Funds flow straight to the merchant's wallet — OpenPay never holds your balance. No server-side ledger means no withdrawal approvals.
Why merchants & customers choose OpenPay
Real value for merchants, simplicity for customers.
- Merchant
0%
Zero transaction fee
OpenPay does not take any percentage of your transaction amount. Unlike credit cards (~3%) or typical QR payment services (1.5–3.25%), there is no payment fee — no matter how large the payment is.
- Merchant
¥0
Zero setup cost
No POS terminal, no contracts, no upfront fees. Just one wallet address — go from start to a printed QR the same day.
- Merchant
Seconds
Instant settlement
Sales land in the merchant wallet the moment the on-chain transaction confirms. No month-end closing, no 2–3 business day waits (non-custodial: OpenPay never holds funds).
- Customer
No sign-up
No sign-up
Customers pay with just a wallet — no address, phone or email registration required. No KYC either.
Why stores need OpenPay
Wallet transfers are handy for people who can already send crypto, but they fall short as store payments: you type the recipient and amount by hand, you can pick the wrong chain or token, the store can't easily confirm what a payment is for, and you need a separate token for gas. OpenPay is an open-source payment tool that removes the friction of using wallet transfers at the point of sale.
Fewer payment mistakes
The store bakes the payment conditions into a QR up front, and the customer just scans it. No hand-typing the recipient, amount, chain or token — so the slip-ups that plague raw wallet transfers go away.
The store sets the amount
Set a preset or any billed amount and present a clear "pay this amount" QR. Customers don't enter the amount themselves, which makes it practical at a counter or an event.
Common use cases
From merchant payments to creator support and community ops.
🏪 Merchants & event booths
Show one QR at a real store, flea market, or event booth — receive JPYC / USDC instantly. No POS terminal, no contract.
🎪 Web3 event sales
Direct wallet-to-wallet payments at ETHTokyo, Devcon, and other Web3 conferences and meetups.
🎨 Creator tip widget
Embed the Tip widget (single-line iframe) on blogs, portfolios, or stream pages — receive JPYC / USDC tips from fans.
🏛 DAO & community fees
Simplify DAO member fees, community sponsorships, and recurring collections with a single QR. On-chain receipts persist.
🎁 Pop-up & micropayments
Start same-day micropayments for exhibitions, pop-ups, or pubs — no contracts or POS hardware required. Viable at price points where credit cards aren't economic.
How it works
Three steps each, for both the receiving and paying side.
📱 Pay (customer)
- 1Connect a wallet from the top-right "Connect"
- 2Scan the merchant QR at the register
- 3Sign in your wallet — done
FAQ
Are payments truly gas-free?
In gasless mode, customers don't need POL or ETH — they pay with just their JPYC or USDC balance (that's what "gasless" means here). For JPYC payments, OpenPay bears the gas in full and collects no equivalent from customers or merchants; the full payment amount reaches the merchant's wallet (the customer simply signs the transfer in JPYC). For USDC payments, the customer pays gas in USDC to the paymaster, so OpenPay does not collect a gas-equivalent.
Can I receive both JPYC and USDC?
Yes. JPYC is a good fit when you want JPY-denominated receipts; USDC is better for Web3-savvy or international customers. JPYC (JPY-pegged) is supported on Polygon and Kaia; USDC on Base / Arbitrum / Optimism / Polygon / Ethereum / Avalanche. Pick the chain in the QR builder. If the customer holds the token on a different chain, Circle CCTP V2 settles cross-chain automatically.
What if the customer has no wallet?
Direct them to a browser wallet (MetaMask, Rabby, etc.) or a mobile wallet (MetaMask Mobile / Rainbow / Coinbase Wallet). OpenPay auto-detects multiple wallets via EIP-6963.
Where is transaction history stored?
History is kept only in your browser's LocalStorage — never sent to OpenPay servers. You can export to CSV from the history page. Transaction hashes are recorded so you can verify on Etherscan / Polygonscan.
About OpenPay fees
OpenPay will never charge a payment fee tied to the transaction amount (a percentage fee). The overall service is free during the alpha period; future monetization is being explored as a volume-independent model such as a monthly subscription or usage license for peripheral features.
If you'd like to help keep OpenPay running, a tip is hugely appreciated. You can support us from the buttons below (also handy for a quick try).
Open stack & transparency
OpenPay is built on a non-custodial design (funds are never held by OpenPay) and open-source stablecoin payment technology. All source code is MIT-licensed and public on GitHub — anyone can verify how the payment flow works.
Source code (GitHub) ↗Tech stack: ERC-4337 (account abstraction) / ERC-7702 (EOA → smart account delegation) / Pimlico bundler/paymaster / permissionless.js / viem / wagmi