Events - Finogates API Documentation

Finogates sends each event as a JSON POST to your webhook endpoint. Every event uses the same envelope; the event-specific fields are in data.

Example

{
  "id": "6f1d2c8e-4b7a-4e0f-9a51-2c3d4e5f6a7b",
  "type": "payment_intent.succeeded",
  "event_type": "payment_intent.succeeded",
  "created_at": "2026-10-13T09:15:22.481203+00:00",
  "data": {
    "intent_id": "5cd7a3c1-4b45-4148-b383-299553699745",
    "user_id": "b3a9b622-cc63-4d3c-aad6-2d8e29e6f9d4",
    "amount": 100.0,
    "currency": "USD",
    "status": 4,
    "status_code": 4,
    "status_name": "succeeded"
  }
}

Envelope Fields

string

Unique event id (UUID). The same id is sent on every retry — use it to de-duplicate.

string

The event, as listed in Event Types.

string

Equal to event_type, except for payment events, where it reflects the payment’s current status. See Payment Events.

string

When the event was created (ISO 8601, UTC).

object

Event-specific fields. Fields may be added over time; ignore any you don’t use.

Naming

Event names use dot notation: <resource>.<action>, or <resource>.<sub-resource>.<action>. For example, user_kyc.approved and payment_method.bank.added.

Delivery

Finogates sends the event to every active endpoint subscribed to it.
Your endpoint verifies the signature.
Your endpoint responds with a 2xx status. Any other result is retried — see Retry Behavior.

Events may arrive more than once or out of order. Use id to de-duplicate and created_at to order.

​Example

​Envelope Fields

​Naming

​Delivery

Example

Envelope Fields

Naming

Delivery