Versions Compared

Key

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

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

  • redirect flow - Everifin Paygate web page is used to process the payment (supported by both API versions 1 and 2)

Drawio
mVer2
zoom1
simple0
zoominComment10
inCommentcustContentId02601451661
pageId2467561491
custContentIdlbox26014516611
diagramDisplayNameEverifin_Redirect_integration.drawiolbox1
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

Drawio
mVer2
zoom1
simple0
zoominComment10
inCommentcustContentId02602008636
pageId2467561491
custContentIdlbox26020086361
diagramDisplayNameEverifin_Full_API_integration.drawio
lbox1
contentVer1
revision1
baseUrlhttps://everifin.atlassian.net/wiki
diagramNameEverifin_Full_API_integration.drawio
pCenter0
width1923
links
tbstyle
height502.5

...

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 partssteps:

Common step Authentication - first your system needs to be authenticated to Everifin Paygate. See Authentication

...