There are two basic types of payments:
One-time payments - for every payment the user must select a bank, log-in, select a bank account and authorize the payment. These payments are initiated by using Everifin Paygate service.
Payments from connected bank accounts - the user must be onboarded (he registers and performs a bank login to one or more banks) and then for every payment he chooses which of the connected bank accounts should be used and authorizes the payment. These payments are initiated by using /wiki/spaces/PCBA/pages/2467659777 service or Everifin Paygate+ service.
Integration scenarios
In both cases above the integration can be done using Everifin UI (recommended), Everifin API or in a hybrid way - some steps with Eveirfin UI and others with Everifin API. The following table shows which combinations are allowed for which service:
Everifin Paygate (one-time) | Everifin Paygate+ (connect bank accounts to Paygate within the payment process) | Everifin Payments (existing Everifin users with already connected bank accounts) | |
|---|---|---|---|
User registration/login | not applicable | not applicable, the merchant is logged-in via API | Everifin UI |
Connecting bank accounts | not applicable | Everifin UI | Everifin UI |
Payment initiation | Everifin UI (Paygate Redirect flow) / Everifin API (Paygate Embedded flow) | Everifin UI (Paygate Redirect flow) | Everifin API |
Everifin UI
Everifin UI is the simplest method of integration. It takes the user to a trusted and licensed payment services provider Everifin (e.g. using a redirect or a modal window). The user can safely authorize the payment and return back without sharing any sensitive data with the original client application (an accounting system, an ERP, an e-shop, etc). The UI can be customized to match the look & feel of the client application.
Everifin API
Everifin API is a more complex integration method which requires the client application to take care about the specifics of the payment authorization process itself. E.g. it must store the list of connected bank accounts, monitor the status of each connection, handle different types of payment authorization processes supported by the banks (redirect to a bank, embedded in the application and decoupled) each with multiple types of authorization factors (push notification, SMS, one-time code, QR code scan, etc).