Checkout they can finish. Refunds that work.
Customers shouldn’t bridge, swap, or learn your stack just to pay you.
- Bridge to our chain first
- Hold the one token we accept
- Paid means final
- Pay in whatever you already hold
- The business always gets USDC
- A refund button that works
Embed Zap on your site.
Register your shop in the dashboard, paste the snippet, and you're live. Hosted checkout—no keys on your site.
<!-- 1. load the component --> <script src="https://[YOUR-ZAP-HOST]/pay.js" defer></script> <!-- 2. drop the button --> <pay-button merchant="your-business.near" amount="24" product="Pro plan" color="#111111" radius="999px"></pay-button> // 3. listen for payment events, then fulfil the order button.addEventListener('uc:paid', showThanks)
A refund button that works.
Customers open a refund flow from their receipt. The assistant asks follow-ups, checks your policy, and routes clear cases — inside your guardrails.
- 24.00 USDC in escrowHeld by receipt NFT #1042
- Business veto windowYour business can still step in
- 1Click swap backQuote ID logged on chain
- ETH on EthereumTo 0x8f3a…c21a, the refund address
The AI proposes. Your rules decide.
Guardrails apply to every refund — on chain, not just in the assistant. Adjust the controls to see how a $24 request is handled.
The same thresholds, caps, and deadlines are enforced in the escrow contract. Read how refunds work →
Don't trust us. Verify.
Look up a receipt by number—no login. See attribution, refund routing, and whether escrow still covers the balance.
No NEAR wallet. No gas.
Customers manage their receipt, and ask for refunds, without ever setting up NEAR.
Receipt key in the browser
Customers get a private key for their receipt on the device they paid from.
Sign actions locally
Refund requests are signed in the browser. Secrets never leave the customer.
No gas for customers
Zap relays the signed action and covers NEAR gas. No wallet setup required.
Your business