How Simpriest protects checkout and delivery
Understand the controls that are present—and the security products that are not.
Current availability
Payment details are entered in Stripe’s Payment Element. Simpriest receives payment status and limited order data, not full card numbers. Provider provisioning starts only after a signed Stripe event confirms payment.
What is available now
Each order uses a protected status token. Provider and admin credentials stay server-side. Payment and email webhooks require cryptographic signatures, and repeated events are handled idempotently.
- HTTPS protects data in transit.
- Rate limits and validation reduce abuse.
- Activation details are shown only on the protected order page and delivery email.
Before you rely on it
Customers must still protect their email, receipt, QR code, activation code, ICCID, and protected order URL. No technical control can make a forwarded activation credential private again.
Contact and updates
There is no automatic enrolment or unpublished benefit attached to this page. For a documented business or support question, email support@simpriest.com. Simpriest will publish eligibility, pricing, privacy, payment, and cancellation details here before accepting applications or redemptions.
Next step
Review the destination, allowance, validity, coverage, and server-confirmed price before paying. Provider provisioning begins only after Stripe confirms payment.
Browse eSIM plans