Before you go live
Test the paths that matter to buyers before switching to production.
Access and setup
- Production credentials are stored on your server, with staging credentials kept separate.
- The intended raffles are attached to your platform.
- Your buyer IDs remain stable across purchases and webhook notifications.
- Your HTTPS webhook endpoint and, if used, redemption website origin are registered with Verity.
Purchases
- A buyer can reserve, pay and see confirmed ticket codes.
- Your transaction uses the returned mint, destination, exact amount and exact checkout memo.
- A duplicate click or HTTP retry does not create a second payment.
- A reload during processing resumes the same checkout.
- Sold-out, closed and expired checkouts show a clear result.
- Refund pending and refund completed are displayed differently.
Webhooks and prizes
- Invalid webhook signatures are rejected.
- Duplicate and out-of-order events do not duplicate notifications or regress status.
- All seven event types are handled.
- A winner can see their prize and the appropriate shipping action.
- No Keep Item, Mint, or unavailable partner buyback action is shown.
Optional redemption
- The holder can sign in, select items, review shipping and approve redemption.
- Full street and apartment details are preserved.
- Insurance is not added twice, and estimated import charges are separate from checkout totals.
- Multi-step approvals can be interrupted and resumed without another order or duplicate payment.
- Tracking reflects shipment status, not merely successful payment.
When these checks pass, coordinate the production key and raffle access with the integration team.