Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section describes various SCA flows the banks provide and the demo banks we implemented to simulate these flows (these help in development phase of the Paygate integration).

Bank SCA flows

Bank SCA Flow

Description

Redirect

Payer is redirect to the bank’s pages where she/he is asked to log in and handle the second factor.

In some banks the payer selects also the bank account to pay from on the bank’s page (description “Select Account at Bank”), in case of other banks the processing is returned back to Everifin paygate and we provide the list of payer’s accounts for the selection (description “Select Account at Everifin“).

Embedded

The bank requires to provide bank login information via API, therefore the payer is asked to provide login information and handle second factor in Everifin paygate pages.

Decoupled

SCA process (login, second factor handling) are done in mobile banking app. Everifin paygate needs to initiate this flow via API and also getting the status of the SCA process may be obtained only via API (then it is continuously presented to payer on the Everifin paygate page).

Usually decoupled SCA flow is combined with embedded approach (payer needs to first login or at least provide just the bank user ID on paygate page and then the second factor is handled using decoupled approach - i.e. push notification appears in payer’s bank mobile app and paygate page is asking the payer to handle this notification and checks the handling status).

Demo banks

To facilitate the development of Pagate API integration we provide Demo banks in for testing environmentAPI clients. You can find them if you select country “Everifin test” (redirect paygate flow) or in the response of List of banks endpoint (in both redirect and embedded paygate flow).

...

Negative Scenarios

Negative Scenario

Description

Failure

Simulates failure of the payment. Payment did not go through. FAILED status is returned in payment detail endpoint response. Field reasonCode contains code representing specific problem.

Canceled

Simulates payment cancellation by the payer at the bank’s pages. Field reasonCode contains code PAYMENT_CANCELED_BY_PAYER_AT_BANK.