TransactionResponse

The ID of the transaction

The ID of the associated subscription

The ID of any associated subscription billing charge. Will be null if the transaction was not an automatic charge made on a billing agreement.

The current state of the transaction. See our <a href="/get-started/core-concepts">Core Concepts</a> page.

If the transaction has failed, this contains the associated error code explaining what went wrong.

A nullable object containing any known external status codes, such as the status code from the acquirer or the network. This can be useful for merchants who want to be able to react to very specific rejection reasons.

The time of creation

The ID of the associated session. This will be null for any MIT transactions.

The ID of the associated payment method

The type of the payment method.

The sub type of the associated payment method. For card based payments, this will contain the name of the scheme, such as `Visa` or `Mastercard`. The card scheme name formatted with a uppercase starting character. For non-card based payments the field vary depending on the requirements of the payment method.

The expiration date of the associated payment method. Although payment cards are specified by a month and year (MM/YY), this value is returned as a full date (YYYY-MM-DD) representing the **last day of the expiration month**. Example: `"2030-05-31"` for a card expiring in May 2030.

A cardholder friendly text to help them identify the payment method. For cards this will be a masked version of the card number.

Contains the entered cardholder name of the optional "name" field. Will be null if the field is not rendered.

The SCA mode of the transaction.

The merchant customer id of the transaction. This field is required to enable advanced features such as storing a card for later reuse. Do not use any "guest" customer ids. Customer ids must be unique for each customer and must be protected by authentication.

The transaction amount in minor units (e.g., 1095 = 10.95 DKK)

The applied transaction fee in minor units. The fee is included in the `amount` field. To get the original amount you must subtract `fee` from `amount`. Fees are only applied if surcharge is configured in the ePay backoffice. <br/><br/> Fees are calculated during transaction processing and as such is always 0 when initially created during MIT transactions.

The currency of the transaction in ISO 4217 alpha-3. DKK for danish kroner.

The instant capture mode.

The URL to receive webhook notifications of any transaction attempts. May contain templating variables.

The ID of the associated point of sale

The merchant reference of the transaction, this is often used for the order id.

The text to show on the cardholder bank statement

The list of exemptions to apply when possible. Note that exemptions may shift liability from the issuer to the merchant.

A list of pass-through parameters that will be sent back to the merchant for following any webhooks

The ip (ipv4/ipv6) of the cardholder making the transaction. The IP is captured by ePay at the initialization of the transaction client-side. Can be empty.

The detected origin country (Alpha-2) based on the `clientIp` property. Can be empty. - Data derived from GeoLite2 by [MaxMind](https://www.maxmind.com).

The type of transaction.