...
Standard process consists of the following steps.
Getting or refreshing existing new API access token
Calling Create Order Endpoint (providing payment data, redirect URL). Storing received Payment ID (and Order ID as it is needed later to get payment detail) and redirecting customer to received redirect URL for payment authorization.
The customer authorizes the payment via her/his bank and finally is redirected back to merchant’s redirect URL. During the payment authorization process, merchant’s webhooks are being called (merchant is getting payment status updates).
Once redirected back to merchant’s web site (or application), the merchant should proceed with the following actions:
Only if Webhooks are implemented - Merchant should check the status of his entity (it might have been updated via webhook call and already in final status - success or failure).
If payment is not in the final status yet (via webhooks), the endpoint to get payment detail https://everifin.atlassian.net/wiki/spaces/EPAD/pages/2562228372/Payment+Orders#Order%E2%80%99s-payment-detail should be called (certain polling interval should be set up as backup for webhooks).
Customer is presented with web page informing about payment success and further information about order processing.
in case of failed payment, customer should be presented with page where he can restart checkout procedure (i.e. kept goods/services in the shopping cart and possibility to choose again from payment methods).
...