1. Server side initialization

Base url: https://payments.epay.eu

Initializing a new payment session is done by making an HTTP request to the Epay Payments API. This can be done using any http client.

Making the initialization request

Initializing a new payment session requires a valid ApiKey, and must be done as a server-side request to make sure the ApiKey is never exposed client-side.

Below is an example of the JSON data, which needs to be transmitted to ePay to initialize a new payment session.

POST /public/api/v1/cit
{
    "pointOfSaleId": "01924737-9c18-71c0-ab1a-88698eaceabf",
    "amount": 1000,
    "currency": "DKK",
    "ageVerification": {
        "minimumAge": 18,
        "country": "DK",
    }
}

Name	Description	Required
`pointOfSaleId`	Id of the point of sale to associate the payment with.	True
`amount`	This is the amount of the payment. The amount must be defined in minor units. E.g. 2,50 DKK must be set as 250. If amount is set to 0 a token will be created only and returned to the integrator.	True
`currency`	The currency code of the payment. For Danish Kroner defined as DKK.	True
`ageVerification`	Optional object. Specifies age verification requirements for the purchase.	False
`ageVerification.minimumAge`	The required minimum age for the payment. Must be between 0 and 99	True
`ageVerification.country`	Country code for the delivery country (ISO 3166 alpha-2 country codes). This code determines which electronic ID (eID) is presented to the user (e.g., MitID in Denmark).	True

Making the initialization request​

Making the initialization request