Content Comparison

...

• Client has access to Everifin Paygate API (details can be found here: Authentication)

• Client has the bank account connected to Everifin system Paygate (Everifin representative provides details on the connection process)

• Webhook is implemented on client' side (public URL that can be called by Everifin)

• Webhook of type payment.statusChange is configured in Everifin Paygate Back Office

...

1. Client gets access token by calling Everifin Paygate’s token endpoint

2. Client initiates payment in Everifin Paygate using specific field isExternalPayment set to true. (https://everifin.atlassian.net/wiki/spaces/EPAD/pages/2562228372/Payment+Orders#Order-initialization). This way Everifin gets the details of the client’s anticipated transaction which is used to search for the related transaction on the client’s bank account (e.g. reference, date, IBANs etc.).
   The client receives and stores ID of the Everifin payment entity.

3. Everifin sends notification to client by calling its client’s webhook once related transaction is found. Client can easily associate the data received to particular order using the payment ID which is provided together with other data in webhook call request body. Details of the data structure can be found here: https://everifin.atlassian.net/wiki/x/C4Baow

...