How the PayKrypt hosted checkout works, from Payment Intent to confirmation
A practical walkthrough of Payment Intents, hosted checkout, and confirmation webhooks.
- Published
- 2026-07-12
This guide explains the checkout flow PayKrypt exposes publicly today: create a Payment Intent, redirect the customer to hosted checkout, and update your own system after the signed confirmation webhook arrives.
The merchant server owns order creation and fulfillment state. The hosted checkout collects the crypto payment on gate.paykrypt.io, then PayKrypt sends payment.confirmed.v1 to the configured webhook endpoint.
Use idempotency keys for retries and verify webhook signatures from the raw body. The browser return is useful for user experience, but the webhook is the payment-confirmation signal.
Source citations
- docs.paykrypt.io/quickstart
- Webhooks docs
- Idempotency-Key docs
FAQ
What confirms an order?
The signed payment.confirmed.v1 webhook confirms the order. Do not use the browser redirect alone as payment evidence.