webhook URL you gave at creation as an HTTP POST with a JSON body and an HMAC signature. Webhooks are the way to learn about renewals: they happen while your customer is not on your site, so there is no redirect to catch.
Delivery
One-off payments use the same
X-Flouci-Signature header. By default a payment created with Generate Payment receives a signed GET <webhook>?payment_id=<id>&success=<True|False>; with "webhook_version": 2 it receives the same signed JSON POST as subscription events. See Payment Webhooks.Payload
One of the event names below.
The charge concerned, when the event is about a charge.
null for lifecycle-only events such as subscription.updated.Events
A single charge can produce two events (for example
subscription.charge.succeeded then subscription.reactivated). Each carries its own event_id.
Verifying the signature
The signature isHMAC-SHA256 over the string "<t>.<raw body>" — the timestamp from the header, a dot, and the exact bytes of the request body — keyed with your app’s private token (the second half of your Authorization: Bearer <public>:<private> credential). Compare it to v1 in constant time and reject timestamps older than a few minutes.
Handling events safely
1
Acknowledge fast
Verify the signature, store the event, answer
200, then process. Slow handlers are retried and produce duplicates.2
De-duplicate on event_id
Retries and the occasional double delivery mean you must treat
event_id as the idempotency key.3
Trust the status, confirm the money
status is authoritative for access. For accounting, confirm a charge with Verify Payment using its payment_id — the same rule as for one-off payments.