Journey 1
Notification with Confirmation via Webhook
In this journey, FitBank sends a request via webhook to the Business Unit (BU), which is responsible for organizing and managing the notification (e.g., a pop-up or SMS) sent to the end user through the app or another configured communication channel. The user must respond to this notification to authorize Automatic Pix.
-
How it works: FitBank sends a confirmation request to the BU via webhook. The BU uses the appropriate API to confirm or reject the request based on the user’s response.
-
API Integration:
WebhookConfirmPixAutomatic
(endpoint for receiving requests) andConfirmPixAutomatic
(to confirm or reject the request),NotifySuccess
(endpoint when the recurrence is approved) orNotifyFailure
(endpoint when the recurrence is rejected).
More details:
WebhookConfirmPixAutomatic: Allows the payer to receive the confirmation request for Automatic Pix via webhook.
ConfirmPixAutomatic: Allows the payer to confirm the authorization of an automatic payment recurrence.
NotifySucess: This webhook notifies that the recurrence has been approved.
NotifyFailure: This webhook notifies that the recurrence has been rejected.
Updated about 4 hours ago