Skip to main content

Transaction Results

In the IXOPAY platform, 3-D Secure transactions yield result data that provides insights into the authentication process. These fields are set on the results of the transaction and are also included in callbacks for your reference.

Transaction result data​

  • returnData.cardData.threeDSecure: This field represents the 3-D Secure status after considering connector settings, API settings, and risk check settings.
  • returnData.cardData.eci: The ECI is the scheme-specific result code of a 3-D Secure session and plays a role in determining whether your transaction qualifies for a liability shift. You can find detailed information about ECI codes and their implications in the Liability Shift - Electronic Commerce Indicator table on the linked page.

Additional result data in callbacks​

If you have enabled the connector setting Postback: Include 3DS Data, callbacks will provide additional fields directly from the 3-D Secure ARes/RReq. These fields are helpful in understanding and analyzing the authentication process.

  • extraData.3ds:version (Type: string): This field indicates the version of 3-D Secure used in the transaction, such as 2.2.0 or 2.1.0.
  • extraData.3ds:attempted (Type: boolean): This field reflects whether 3-D Secure authentication was attempted during the transaction.
  • extraData.3ds:eci (Type: string): The ECI is the scheme-specific result code of a 3-D Secure session and plays a role in determining whether your transaction qualifies for a liability shift. You can find detailed information about ECI codes and their implications in the Liability shift - Electronic Commerce Indicator table on the linked page.
  • extraData.3ds:challengePerformed (Type: boolean): This field is set to true if a 3-D Secure challenge flow was performed during the transaction. For details, refer to Authentication flows.
  • extraData.3ds:transStatus (Type: string): The transStatus field represents the outcome of the 3-D Secure authentication flow. Further details can be found in the Authentication flows section.
  • extraData.3ds:exemptionFlag (Type: string): Certain transactions may qualify for a 3-D Secure exemption, and this flag indicates whether an exemption was applied.
  • extraData.3ds:authenticationTimestamp (Type: string: date-time (YYYY-MM-DDTHH:mm:ssXX)): This timestamp reflects when the 3-D Secure authentication occurred. It can occur at the end of a challenge flow or during a frictionless flow.
  • extraData.3ds:transStatusReason (Type: string): The transStatusReason field provides an error code related to the 3-D Secure session.
  • extraData.3ds:xid (Type: string) Deprecated: This field is specific to 3-D Secure v1 and is no longer in use.
  • extraData.3ds:dsTransId (Type: string): Tge dsTrandId represents the transaction ID of the 3-D Secure Directory Server (DS).
  • extraData.3ds:acsTransId (Type: string): This field contains the transaction ID of the issuer's 3-D Secure Access Control Server (ACS).
  • extraData.3ds:cardholderInfo (Type: string): Information from the issuer's 3-D Secure Access Control Server (ACS) to the cardholder during a frictionless transaction, e.g., "Additional authentication needed, contact (Issuer Name) at xxx-xxx-xxxx." Display to the customer if available.
Last updated on