Webhooks

The Enfuce platform is event-based. Every change in your card program generates an event: a card is created, updated or closed, a cardholder is created or updated, a token is created or updated, and a transaction moves through its lifecycle. Enfuce delivers these events to you in real time through webhooks. Webhooks are the primary way to integrate with Enfuce. They let you act on what is happening in your program as it happens, without polling the API for changes.

​

How webhooks work

You host an endpoint, and Enfuce sends each event to it as an HTTP POST request. Each webhook has a defined payload, described in the API reference. Webhook notifications describe events that have already occurred. Where Enfuce needs a decision from you, such as approving or declining an authorisation, it uses a separate synchronous request instead. See the Authorisation Request API. Your webhook subscriptions are agreed with your Onboarding Manager as part of your onboarding.

​

Available webhooks

​

Authentication

Enfuce authenticates the requests it sends to your endpoints. See Authentication for Outgoing Endpoints and Webhook Notifications.

​

What you can do with webhooks

Use webhooks for anything that should happen immediately, such as:

• notifying a cardholder about a transaction or a change to their card
• updating your app or internal systems
• triggering an operational action, such as a review or a follow-up
• building and maintaining your own databases: store each event as it arrives, and your data stays current throughout the day

​

Webhooks and Data Files

Webhooks and Data Files are built from the same underlying events. Webhooks deliver each event in real time. Data Files delivers the same activity as structured daily files, for periodic processes such as loading a data warehouse, daily reconciliation or regulatory reporting. You can use either or both.