PaymentSessionInitializationResponse
QR code version of the `paymentWindowUrl` in base64, which can be displayed for quick device-to-device link sharing such as from a POS device where the customer can scan the code and complete the payment on their own phone. Is only present if `generateQrCode` is set to `true`.
URL for ePay Checkout. If you are using Checkout and not Blocks, then you must redirect the customer to this URL.
uriFor merchants implementing Blocks, load this script to use the ePay.js client
uriFor merchants implementing Blocks, this is the client secret used to allow the ePay.js client to interact with the payment session
The ID of the payment session
uuidThe subscription id related to the session, this can either be a new ID for new subscriptions or the given ID of a previous subscription which needs to be updated.
uuidThe transaction amount in minor units (e.g., 1095 = 10.95 DKK)
Pass-through data which will be returned back to the merchant in any webhook.
List of exemptions to apply when available. Note exemptions may cause liability shift from the issuer to the merchant.
List of allowed payment methods to use for this session. If left empty, all payment methods will be allowed. This is useful for controlling which payment methods are visible in the payment window. If only 1 payment method is allowed and it is redirect-based, such as `VIPPS_MOBILEPAY`, the user will be automatically redirected from the payment window to the MobilePay payment page, without the user having to click anything. If the user then cancels the MobilePay payment, they will be redirected back to the `returnUrl` (Or the `failureUrl` if the `returnUrl` is not specified) instead of going back to the payment window.
[
"CARD",
"VIPPS_MOBILEPAY"
]The currency of the payment. For Danish Kroner defined as DKK.
^[A-Z]{3}$The expiration time of the payment session. After this time the session can no longer be used and a new session must be created.
date-timeThe instant capture mode.
"OFF""VOID""NO_VOID"The maximum number of transaction attempts allowed for the session
The current number of transaction attempts so far.
The minimum age required. If not null and ePay Verify is enabled on your account, the cardholder will be prompted to verify their age using local online IDs such as MitID in Denmark.
Is true once the customers age has been verified to be at least equal to `minimumAge` parameter.
Boolean flag to enable / disable receiving webhook notifications for failed transactions.
Boolean flag to enable / disable receiving webhook notifications for sessions that reach the expired state.
Boolean flag to enable / disable dynamic amounts, allowing the client to determine the transaction amount. This is generally not recommended for most merchants.
The URL to receive webhooks related to transaction attempts
uriOptional URL to receive a webhook just before authorization is attempted. Can be used to update or reject the transaction. This is often used by merchants integrating external risk tooling to trigger 3DS challenges depending on the payment.
uriThe URL to redirect the client on successful payment attempts
uriThe URL to where the browser is returned, when clicking the `back` button in the Payment Window. This overrides the default defined in the payment window configuration and supports url templating. Max length is `1024`. <div class="theme-admonition theme-admonition-info alert alert--info"> Only used in Payment Window integrations. </div>
uri1 <= length <= 1024The URL to redirect the client on failed payment attempts when no more attempts are possible.
uriThe URL to redirect the client on failed payment attempts when more attempts are possible. If null, then failureUrl is used instead.
uriThe ID of the cardholder. This field is required to enable stored cards. Do not use any "guest" customer ids. Customer ids must be unique for each customer and secured behind authentication.
The ID of the associated point of sale
uuidThe transaction reference - Typically the order id.
The state of the transaction
"PENDING""PROCESSING""COMPLETED""EXPIRED"The text to display on the cardholders bank statement
1 <= length <= 39The chosen SCA mode. This can be used to control the level of cardholder authentication performed before the transaction is authorized.
"SKIP""NORMAL""FORCE"The number of minutes the session is available.
The time of creation
date-time