...
Both scenarios have similar steps in the payment process, just the initialization is different.
Steps
The payment flow has these parts:
...
Order initialization - redirect URL and payment ID are present in the response
Order processing
Redirect flow - Redirecting to URL obtained in step 1. Details of the redirect flow can be found here: Redirect Flow
Embedded flow - Calling Process Order endpoint until the payment is processed (anmd and react on specific responses like inputs requests etc.). Details of the embedded flow can be found here: Embedded Flow
Checking status
Either by getting the order detail (Get Order endpoint) - it provides detail of the order together of details of all its payments
Or by getting the detail of the specific payment in the order (Get Order Payment endpoint)
...
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 | yesALL | Payment is created and waiting for the user. | |
SEEN | no | yesREDIRECT | User opens the Everifin Paygate web page or processing via Process Order endpoint is started. | |
PROCESSING | no | no | ALL | The payment is being processed (user is authorizing payment on bank`s page or authorization is done and payment is being processed in the bank). |
CONFIRMED | yes | noALL | The payment has been successfully authorized in the bank by the payer. | |
BOOKED | yes | no | ALL | The payment has been booked (settled) in the bank. |
WITHDRAWN | yes | noALL | The payment has been withdrawn by merchant. | |
FAILED | yes | noALL | Payment has failed. Field | |
EXPIRED | yes | noALL | Payments that stay in CREATED or SEEN for a long time are eventually moved to this state. |
...