Checkout behavior
Confirm the customer payment page, wallet handoff, expiry behavior, and confirmation messaging.
Free testnet evaluation
Test XPayr crypto checkout before mainnet
Create a test payment session, complete a testnet checkout, and verify the payment status before moving real funds. XPayr testnet helps merchants evaluate checkout, API/webhook records, fee math, and settlement behavior before mainnet review.
Last updated: June 29, 2026
Direct answer:
XPayr testnet lets merchants evaluate crypto checkout without live funds. A merchant can create a payment session, complete a test checkout, review payment status, check fee records, and confirm whether the flow fits checkout, deposits, recurring billing, or payout preparation.
What to validate
Start with one payment flow, not every feature.
A useful first test proves that payment creation, checkout, status tracking, fee records, and settlement details are understandable for your team. Advanced modules can be evaluated after the first successful flow.
Status records
Check whether the merchant dashboard and payment session status are clear enough for operations.
API and webhooks
Validate the technical route for creating sessions and receiving payment status events.
Fee and settlement logic
Review gateway fee records and settlement details before deciding on production routes.
4-step checklist
The shortest path to a useful test
Use this sequence before discussing a full integration or mainnet activation.
Create or open a payment session
Start with one payment session through a payment link, widget, button, or API route. Use a realistic amount and a use case that matches your first production flow.
Complete a testnet checkout
Run the hosted checkout with a test wallet or test route. The goal is to confirm the customer-side payment experience before moving real funds.
Check status, fee, and settlement records
Verify the payment status screen, fee record, transaction reference, and settlement details so your operations team knows what will be reconciled.
Choose the next setup path
After the first successful test, decide whether the next step is API/webhooks, player deposits, recurring billing, payout preparation, or mainnet review.
Use-case paths
Choose the test path that matches your first real workflow.
| Use case | Best first test |
|---|---|
| Checkout payments | Create a sample invoice or payment link and confirm payment status, fee math, and settlement details. |
| Player or user deposits | Test account-style payment mapping and confirm that the payment record is easy to match to a player or user. |
| Recurring billing | Create a subscription-style payment record and review how reminders, invoices, and payment status should be tracked. |
| Payout preparation | Use the test environment to review how merchant-side batch preparation, transaction references, and records should be organized. |
| API and webhooks | Create a payment session through the API and confirm status changes, webhook delivery, and reconciliation fields. |
What testnet does not prove yet
Testnet confirms product and integration fit. It does not automatically approve live payment processing.
- Mainnet wallet, route, token, and business setup still need to be reviewed.
- Regulated or high-risk sectors may require additional merchant review.
- Network gas, liquidity, and production route behavior depend on the selected chain and token.
When to request mainnet review
Request review after your team understands the test flow and can describe the first production use case.
- Target networks and tokens.
- Settlement wallet requirements.
- Expected checkout type and monthly volume.
- Business model and any regulated category flag.
FAQ
Questions before your first test payment
Can I test XPayr without real crypto?
Yes. XPayr testnet is designed so merchants can evaluate payment sessions, checkout behavior, status records, fee math, and integration flow before moving live funds.
What should I check during a testnet payment?
Check whether the payment session is created correctly, the checkout is understandable, the payment status updates, the fee record is clear, and the settlement details match your expected workflow.
Does testnet mean mainnet is approved?
No. Testnet helps evaluate product fit and technical flow. Mainnet activation can still require route, wallet, business, and risk review before live payments are enabled.
Can developers test API and webhook behavior?
Yes. Developers can use the API documentation to create test payment sessions and review status behavior, webhook delivery, and reconciliation fields.
What should I send after completing a test?
Send the intended use case, target networks and tokens, settlement wallet requirements, API or widget preference, and whether you want to continue with testnet evaluation or mainnet review.