3DS - Notifications

Introduction

In order to notifiy merchants about the results of the 3DS authentication, e.g. if a challenge is finished, a new notification event is required.

This event will only be supported for the Payengine Notifications Version 2 and is only available via the Webhook.

Event	Webhook	Email
3ds.result	yes	no

Parameters

Parameters	Description
notificationApiVersion	version of the notification service, always set to 2.0
notificationId	Payengine notification identifier
globalTrackId	Payengine global tracking id (for debugging)
eventType	Type of the event, e.g. trx.debit.success
createdAt	Timestamp of the event
merchantId	Payengine merchantId
threeAuthenticationId	Identifier of the 3DS authentication transaction generated by the Payengine if transaction was triggered through dedicated authentication service
orderData	Order object in case the authentication was triggered as part of an order
orderData.transactionId	Payengine transactionId
orderData.orderId	Payengine orderId
orderData.merchantOrderId	Merchant order reference
authenticationResultDto	Object containing the result of the 3DS authentication transaction (final results will be available only in case of frictionless flow)
authenticationResultDto.version	Parameter indicating the version of the 3DS (1.0 or 2.0)
authenticationResultDto.status	Enum:Y N A U R, Indicates whether a transaction qualifies as an authenticated transaction or account verification. Y = authentication successful / N = not authenticated; transaction denied / U = authentication could not be performed; technical or other problem / A = attempts processing performed; not attempted / R = authentication rejected; issuer is rejecting
authenticationResultDto.transactionId	The transaction identifier from the 3DS authentication 3DS 1.0: This will be the XID 3DS 2.0: This will be the dsTransID
authenticationResultDto.authenticationValue	The authenticationValue returned in the 3DS authentication CAVV: Visa, AMEX, JCB, Diners/Discover UCAF: Mastercard
authenticationResultDto.eci	The Electronic Commerce Indicator (ECI) provided by the ACS or DS to indicate the results of the attempt to authenticate the cardholder. The ECI values might differ depending on the card scheme. For all fully authenticated or authentication attempted transactions the liability will be shifted to the card issuer. Mastercard: 00 - no authentication available / 01 - authentication attempted / 02 - fully authenticated / 07 - fully authenticated (Mastercard distinguishes between fully authenticated recurring payments (flagged with ECI 07) and all other fully authenticated transactions (flagged with ECI 02)) All other card schemes: 05 - fully authenticated / 06 - authentication attempted / 07 - no authentication available
authenticationResultDto.errorDetails	Object containing error information in case of error
authenticationResultDto.errorDetails.providerCode	Original error code from the 3ds server or mpi
authenticationResultDto.errorDetails.providerMessage	Original error message from the 3ds server or mpi
type	Enum:PAYMENT_TRANSACTION RECURRING_TRANSACTION RECURRING_CARDCHECK"ADD_CARD / The type of the authentication requested. / PAYMENT_TRANSACTION: authentication with payment; the authentication is used for a normal payment transaction, RECURRING_TRANSACTION: authentication with payment; the authentication is used for an initial recurring payment transaction, RECURRING_CARDCHECK: authentication without payment; the authentication is used for a card check representing the initial recurring payment transaction, ADD_CARD: authentication without payment; the authentication is only used for the verification of stored card credentials, e.g. within a wallet
paymentInstrumentId	Identifier of the payment instrument used for the 3DS authentication.

Sample 3ds.result event message

{
                    "notificationApiVersion": "2.0",
                    "notificationId": "notification_ewnozkeo6z",
                    "globalTrackId": "XLg5rFkDCps-XAAa-qpMuwAAAAQ",

Subscription

You can subscribe for a 3ds.result event either via Merchant Center configuration or via the API in the corresponding 3DS authentication request.

Subscription via Merchant Center

The subscription of the 3ds.result event can be enabled in Notification settings in the Merchant Center.

The event will only be available for Notification Type=URL and Version=V2.

Subscription via API

The subscription of the 3ds.result event can be enabled via the API as part of the async.notifications-object in the 3DS authentication request.

Sample 3ds.result event message

"async": {
                  "notificationUrl": "https://{someurl}",
                  "successUrl": "https://my.success.url",
                  "failureUrl": "https://my.failure.url"

3DS - Notifications

Introduction

Parameters

Sample 3ds.result event message

Subscription

Subscription via Merchant Center

Subscription via API

Sample 3ds.result event message

What was your feeling about it?