Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The payment flow has 2 possible scenarios (these are also 2 possible ways how to integrate the Everifin Paygate API):

...

can be described by the picture below.

Drawio
mVer2
zoom1
simple0
inComment0
custContentId2601451661
pageId2467561491
lbox1
diagramDisplayNameEverifin_Redirect_integration.drawio
contentVer1
revision1
baseUrlhttps://everifin.atlassian.net/wiki
diagramNameEverifin_Redirect_integration.drawio
pCenter0
width1933
links
tbstyle
height513
  • embedded (full API) flow - your web page is used to process the payment (no Everifin GUI is used, purely the API calls). This flow is supported only in API version 2

...

Both scenarios have similar steps in the payment process (API v1 supports only redirect flow, API v2 supports both flow types).

Steps

The payment flow has these steps:

...

  1. Order initialization - redirect URL and payment ID are present in the response

  2. Order processing

    1. Redirect flow - Redirecting to URL obtained in step 1. Details of the redirect flow can be found here: Redirect Flow

    2. Embedded flow - Calling Process Order endpoint until the payment is processed (and react on specific responses like inputs requests etc.). Details of the embedded flow can be found here: Embedded Flow /wiki/spaces/~5dd3fb319def2a0ee974c384/pages/2467561560

  3. Checking status

    1. Either by getting the order detail (Get Order endpoint) - it provides detail of the order together of details of all its payments

    2. Or by getting the detail of the specific payment in the order (Get Order Payment endpoint)

...