Migration guide

Use this when moving from manual crypto address collection or another payment flow to Tempest Pay’s charge + hosted checkout + webhook model.

Key differences

Server-created charges: create charges from your backend using a secret key and Idempotency-Key.
Hosted checkout: redirect users to hosted_url instead of managing raw payment UI/address lifecycle yourself.
Webhook truth: fulfill only after verified charge.paid (or verified server-side paid status), not browser redirects.
Status model: handle pending/processing/partial/paid/overpaid/underpaid/expired/cancelled/late payment as applicable.

Map your internal order ID to Tempest Pay reference and metadata.
Implement idempotent charge creation and webhook processing.
Run end-to-end tests in test mode/sandbox.
Deploy webhook endpoint with raw-body signature verification and durable event dedupe.
Switch keys/URLs to live, monitor first transactions, and keep manual reconciliation procedures.