SEPA Secure withdrawal initiation

A full SEPA Secure withdrawal flow includes the following steps:

1. Create a customer account and KYC applicant for a new customer

2. Pass KYC, if the customer has not passed it yet

3. Create a Destination Bank Account (DBA), where the funds will be sent to

4. Trigger a withdrawal

In order to provide a maximum flexibility, the XGateway offers separate API endpoints for each of the actions as well as an option to pass through the flow using UI.

VPN usage may block a customer from passing KYC checks. It is highly recommended to warn customers not to use VPN (including Apple Private Relay).

SEPA Secure withdrawal flow via API (host-to-host)

SumSubSDK KYC part remains UI-only. Check the host-to-host option to omit this step

The flow can be used if a merchant already has the majority of customer information or wants to build their own UI.

Step 1 needs to be finished only once and only if SumSub token sharing is not implemented.

Step 2 also includes API endpoints for DBA management.

Steps for host-to-host withdrawal flow

1. KYC module

   1. Create SEPA Secure user account

   2. Create KYC applicant

   3. Trigger KYC module checkout link to get the page with SumSub SDK to show to the customer

   4. Complete KYC via UI

2. DBA module

   1. Create and activate DBA via API

3. Trigger a withdrawal

   1. Initiate a withdrawal

   2. Check the callback and confirm the transaction received

SEPA Secure withdrawal flow through UI

The UI-based flow includes all the steps from host-to-host flow. The data needs to be manually input by a customer.

Steps for UI flow

1. DBA module

   1. Trigger DBA management link

   2. Complete the KYC and setup the DBA via UI

2. Trigger a withdrawal

   1. Initiate a withdrawal

   2. Check the callback and confirm the transaction received

Testing the withdrawal callback

The Demo Environment provides and API to simulate a deposit.