Null Checkout
Create a reusable payment page, track separate customer orders and export verified receipts.
One public page, separate payment orders
Checkout is a reusable page for project payments, services or community support. Choose the asset and network you want to receive, enter a receiving wallet and add a name and description. Each payer starts their own Receive request, so multiple customers can use the same public link.
The destination and receiving asset cannot be edited after creation. Create another page if either changes. The recipient does not need to connect or sign with the receiving wallet.
Create your checkout ↗What a customer does
- Open the page and check its name, asset, network and destination. Creator identity is not verified by Null Cash.
- Select Choose how to pay. A separate seven-day payment request is created for this browser session.
- Choose an available sending asset, review the route and fees, and follow the funding instructions on that order.
- Save the order and track the final receiving transaction. Do not send funds to the page QR.
Repeated clicks and retries reuse the same session. Returning to the checkout offers Continue your payment. After a completed, returned or expired session, Start a separate payment deliberately creates a new one. Do not use a new browser to retry a payment already funded.
An optional suggested amount is a reference, not an enforced price or guaranteed payout. This release is not a shopping-cart integration, automatic subscription or invoice reconciliation system. Confirm the actual received amount before fulfilling goods or services.
Read verified receipts, not promises
The dashboard refreshes saved activity every 20 seconds while open. Background refresh checks up to three outstanding orders per visit, using the same on-chain delivery verification as Receive. Provider or network delays can leave old snapshots visible; Last verified shows when an order was actually checked.
| Metric | Meaning |
|---|---|
| Verified received | Sum of final amounts for verified delivered requests, in this page’s receiving asset. |
| Delivered payments | Requests with verified final delivery. Provider completion or intermediate ETH alone does not count. |
| Orders in progress | Reserved or ongoing orders, including ones that need attention. |
| Sessions started | All requests created from the page, including unpaid and expired requests. This is not a unique-customer count. |
CSV exports all sessions with UTC timestamps, status, verified amount, destination and transaction link. Returned or incomplete orders are not included in received totals. A page currently accepts up to 2,000 sessions; create another page after reaching this limit. The dashboard shows 50 rows per page.
Pause new sessions without stranding existing orders
Pause prevents the creation of new payment requests. Existing sessions can still be resumed, funded or completed. It does not cancel orders, reverse transactions or refund money. Resume enables new sessions again. There is no page fee on top of the existing exchange fees; the payer sees route-specific charges before funding.
Checkout inherits current exchange availability, limits, service-fee eligibility, provider processing and automatic final-token delivery rules. It does not guarantee anonymity, instant settlement or delivery on every asset pair. The public page reveals its configured receiving address and asset; other customers’ orders and aggregate revenue remain available only in the management dashboard.