The payment flow for payment has 2 possible scenarios:
redirect flow - Everifin Paygate web page is used to do the payment
embedded flow - your web page is used to do the payment and you call only Everifin Paygate API
Both scenarios have similar steps in the payment process, just the initialization is different.
The payment flow has these parts:
Authentication - first your system needs to be authenticated to Everifin Paygate. See Paygate Authentication
Payment initialization - this step is different for both scenarios:
Redirect flow - see Paygate Redirect Flow
Embedded flow - see Paygate Embedded Flow
Payment update - optional step to update payment data or cancel the payment. See Paygate Payment Operations
Payment processing - optional step for embedded flow, see Paygate Embedded Flow
Hooks - optional step, all changes of the payment can be send to you by a hook. See Paygate Hooks
Get payment(s) - you can get payment data for single payment or payment list. This can be used to check payment status in case you do not use hooks. SeePaygate Payment Operations
Payment statuses
During the payment process the payment changes its status. The status defines not only state of the payment, but also possible operations - payments in some statuses cannot be updated or cancelled.
Status | Final | Withdrawable | Flow | Description |
---|---|---|---|---|
CREATED | no | yes | ALL | Payment is created and waiting for the user. |
SEEN | no | yes | REDIRECT | User opens the Everifin Paygate web page. |
FINISHED | yes | no | ALL | The payment has been successfully paid. |
REJECTED | yes | no | ALL | The payment has been rejected by user. |
WITHDRAWN | yes | no | ALL | The payment has been withdrawn by you. |
PROCESSING | no | no | ALL | The payment is in processing (the user is authorizing payment on bank`s page or authorization is done and the payment is being processed in the bank). |
FAILED | yes | no | ALL | Payment has failed. |