Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kryptopay.xyz/llms.txt

Use this file to discover all available pages before exploring further.

KryptoPay webhook flows are part of production-grade reconciliation and event-driven processing.

​
Receiver design

Your webhook endpoint should:
  • Accept POST JSON payloads
  • Verify signatures before processing
  • Return 2xx quickly
  • Process events idempotently

​
Delivery model

Webhook systems can produce retries and replayed events. Build handlers so the same event can be received more than once without double fulfillment.

​
Payment events

KryptoPay currently emits these payment lifecycle events:
  • payment.succeeded
  • payment.mismatch
payment.mismatch means a payment was detected on-chain for the expected wallet, but the amount did not match the intent. The intent moves to review_required and should be handled manually by the merchant.
  1. Verify signature and timestamp.
  2. Persist raw event and delivery metadata.
  3. Acknowledge quickly (200/204).
  4. Process asynchronously in a job queue.
This keeps webhook availability high under burst traffic and partial downstream outages.