Crypto payments.
Your way to connect.
Explore payment links, WooCommerce and a custom API integration. Choose the setup that fits your website.
Add a payment link to your website
Payment links are the simplest way to preview hosted checkout without building an API integration. Each visit to a reusable link can start a separate test invoice.
- Sign in to your approved merchant account and open Integrations.
- Under Reusable payment links, choose a title, a fixed USD amount and a checkout expiry.
- Create the test link. Copy its URL to a website button, or use the generated button code.
- Open the link and create a test checkout. In Payments, use the sandbox controls to simulate an outcome.
Keep test buttons on a preview page. A sandbox checkout does not collect cryptocurrency or complete a real order. For automated order handling, use the plugin or API and verify payment events on your server.
Connect a WooCommerce store
The Sellpay sandbox plugin lets you test checkout and signed order updates on a staging WordPress store. It includes classic checkout and Checkout Blocks support.
- Download the plugin from your dashboard's Integrations page and install its ZIP through WordPress → Plugins → Add New → Upload Plugin.
- Activate it, then open WooCommerce → Settings → Payments → Sellpay.
- Follow the dashboard's WooCommerce instructions to create a test API key, register the plugin's webhook URL and enter the matching signing secret.
- Place a test order while signed in as an administrator or shop manager. Customer test purchases are restricted in this release.
- Simulate a paid invoice in Sellpay. Confirm the signed webhook updates the matching test order once, including when an event is retried.
Use a staging store and test products. Never use a simulated payment to deliver a real product. Before live release, verify checkout, order transitions and webhook delivery with your own theme and plugins.
Build a custom crypto checkout integration
Your backend creates an invoice and receives a hosted checkout URL. Your customer opens that URL; your server processes signed status events. API keys stay on your server.
- Reliable invoice creation: reuse an idempotency key when retrying the same order attempt.
- Verified updates: validate the raw webhook body, signature and timestamp before changing an order.
- Duplicate protection: record event IDs and handle repeated or out-of-order events safely.
- Delivery diagnostics: inspect webhook attempts and replay a test event from Integrations.
Read the API and webhook guide → for request examples, event states and PHP, Node.js and Python starter files.
Before you choose
Do I need a merchant account to test an integration?
Yes. Creating test invoices, links and credentials requires an approved merchant account. Public registration is not available yet. Join the waitlist for access updates.
Can I use the sandbox to accept real payments?
No. Test invoices only simulate status changes. They do not receive real funds and must not trigger fulfillment of real orders.
Should my website trust the checkout return page?
No. A browser redirect is not proof of payment. Use verified server-side events and match the invoice, order, amount and currency before updating your own records.