There are three basic types of payments use-cases supported by Everifin Paygate service:
One-time payments - for every payment the user must select a bank, log-in, select a bank account and authorize the payment.
Payments from returning customers who saved bank accounts - users connect their bank accounts to Paygate with limited permissions only to perform payments at merchants vetted and trusted by Everifin
Payments from Everifin accounts - the user is already using another Everifin service (Multibanking or Wallet) and has already at least one bank account connected there. These bank accounts are not limited for a specific payment use-case and therefore can be re-used in Everifin Paygate with user’s consent.
...
Use cases
In all cases above the integration can be done using Everifin UI (recommended) or Everifin API. The following table shows which combinations are allowed for which serviceuse case:
One-time payment | Returning customers who connect Payments from saved bank accounts limited to paymentsEverifin customers (existing Everifin users with already connected bank accounts) | Payments from Everifin accounts | |
|---|---|---|---|
User registration/login | not applicable | not applicable, the merchant is logged-in via API | Everifin UI (Multibanking or Wallet) * |
Connecting bank accounts | not applicable | Everifin UI (Paygate Redirect flow) | Everifin UI (Multibanking or Wallet) * |
Payment initiation | Everifin UI (Paygate Redirect flow) / Everifin API (Paygate Embedded flow) | Everifin UI (Paygate Redirect flow) | Everifin UI (Paygate Redirect flow) / Everifin API (Paygate Embedded flow) |
...