A webhook is a notification system that allows you to receive alerts and notifications about important business process flows. You can register to events and choose to receive real-time event messages to your secured application endpoint. Such messages may save you time and effort to track the key activities that are crucial to your business.

Fusion Webhooks

A fintech can subscribe to a webhook to receive a payment event message during the payment lifecycle. The payment events are invoked when processing Acquirer, Issuer and Fusion Payment Engine communicate with each other internally to process online or card payments. Using webhooks, you can also register for various business process flows, for example, account holder on-boarding, account transfer, KYC status, card capabilities and status, and so on.

Fusion webhooks are designed to send notifications to your application when a fintech-defined event occurs as a result of business flow. You can subscribe to various account- and transaction-related events and take necessary actions when they occur. Fusion sends a secure message containing the webhook payload in JSON format. For example, you can notify an account holder about a payment failure (using SMS/email) when a transaction at an apparel store declines due to insufficient balance. 

Webhook flow

You can get started with webhooks using the following basic steps:

1. Set up a webhook endpoint and the environment to handle the webhook data on your platform.
2. Share this endpoint with Zeta. Zeta will register the webhook endpoint in Fusion platform and share a secret token with you to validate the incoming webhook messages.
3. Using Fusion APIs, subscribe to an event and receive the notification to your webhook endpoint.

Supported events

The table below lists all payment and A2A transfer events that you can subscribe to and receive the event notification using Webhooks. Keep watching this page for more supported events that you can add into your webhooks based on the business process flow.

Event structure

A typical incoming webhook notification contains the following event attributes.

Below is an example of a standard event structure:

{
	"topic": "Fintech specific object", 
	"name": "event name",
	"eventId": "event identifier",
	"source": {
		"uri": "entity source URL emitting the event", 
		"tags": [ 
			"tag://vbo/v0001",
			"Fintech tag that has access to the source objects"
			],
		"state": "object state when an event is triggered"
		},
		"data": {event details covering the key changes},
		"origin": {
            "instance": "app URL emitting the event", 
            "time": "event generation time in epoch millis",
            "flowId": "uuid of flow from which the event is emitted."
       }             
}

Related articles