Hosted checkout first, webhooks always

The shape of an integration

1. Your backend creates a checkout session with the approved transaction or contract context.
2. The browser is redirected to a REVRST-hosted page, where the customer authenticates and completes setup.
3. REVRST receives provider confirmation and records payment, mandate and reward state.
4. A signed webhook is delivered to your endpoint.
5. The customer is returned to your success URL.

Non-negotiables

• Verify the signature on every webhook before acting on it.
• Handle redelivery — events are at-least-once, so consumers must be idempotent.
• Never treat the return URL as confirmation of payment.
• Reconcile against provider references rather than inferring state.

No API is live. This describes the intended contract so integration work can be scoped honestly.

See the lifecycle run

The checkout demo drives the real state machines in the browser.

Open the checkout demo→