Alevo
HelpOpen Alevo
technical·Product guide

Payment links and settlement events

Understand the flow from a customer payment page to a verified payment allocation.

Last reviewed: 21 October 2026

  1. 01Alevo creates a payment request
  2. 02Customer opens the hosted checkout
  3. 03Gateway processes the selected method
  4. 04Webhook is verified and made idempotent
  5. 05Alevo allocates the payment to the invoice

The gateway is the payment authority

Alevo should record and reconcile gateway outcomes; it should not treat a browser redirect alone as proof of settlement.

Integration boundary
payment request → provider checkout → signed webhook → idempotent allocation → invoice timeline

Need the product screen?

Open Alevo Help for a short path back to the relevant workspace.

Open help
Payment links and settlement events · Alevo Docs | Alevo