Sandbox testing
Use staging, Test Shop, and Test Center to rehearse the full lifecycle.
Sandbox testing is where merchants prove checkout, webhooks, refunds, settlements, chargebacks, and payout dry-runs before any production traffic.
Browser Test Shop
Test Shop is a non-production browser harness for checkout testing. It is useful for non-developer stakeholders and for verifying webhook delivery without wiring a complete storefront first.
- Log in to staging or test as a merchant.
- Open Test Shop from the portal.
- Create or select the built-in webhook capture endpoint.
- Use a staging/test secret key only.
- Create a checkout and open the hosted checkout URL.
- Refresh payment and webhook status until the event arrives.
- After completion, try a merchant-session refund if needed.
Merchant Test Center
Test Center is for owner/admin users in non-production environments. It helps your team rehearse operational outcomes before live traffic.
- Send sample signed webhook events to subscribed endpoints.
- Send sample encrypted webhook events and verify your receiver can decrypt them with the one-time private key.
- Create sandbox chargebacks on completed test payments.
- Generate sample settlement and reconciliation outcomes for test payments.
- Move staging payout requests through sample outcomes without Alpha support.
- Jump directly to payments, webhooks, settlements, chargebacks, payouts, and Test Shop.
Sandbox expectations
Sandbox testing should reinforce practical merchant expectations: hosted checkout sessions expire, sandbox responses should mimic production errors, asynchronous payment methods rely on webhook-style notifications, and payout success can be asynchronous rather than immediate. Merchants should build for pending, retry, expiry, and asynchronous final confirmation.
- Checkout sessions can expire; create a fresh payment if the buyer misses the window.
- Some payment methods stay pending until a final notification arrives.
- Payout API acceptance is not the same as delivered funds; wait for Alpha payout status.
- Sandbox credentials and test payment details are not production approval.
Checkout testing
- Use the checkout URL returned by the staging or test payment API.
- Verify the buyer can complete, cancel, abandon, or retry checkout without your order system fulfilling too early.
- Confirm your webhook receiver handles pending, completed, failed, expired, refunded, and disputed states.
- Keep real customer payment details, production customer PII, and live beneficiary credentials out of sandbox tools.