AuthRequestRecieved

The initial status of 3D Secure, as long as Zuora receives the request.

N/A

InvalidAuthRequest

The authentication request was invalid. The request was invalid mainly because basic validation on Credit Card fields failed. The 3D Secure process was stopped.

The validation includes but not limited to:

• Required fields are not specified.

• The expiration date has passed.

The error is displayed on the Payment Page so that consumers can modify their input.

GatewayNotSupported

The payment gateway does not support 3D Secure.

Adjust the HPM integration to use payment gateways that support 3D Secure.

EnrollCheckAttempt

An attempt was conducted to check whether the credit card was enrolled with 3D Secure.

If the card issuer, card range, or cardholder is not enrolled, this value will be returned. For more information, see the Worldline Global Collect documentation .

Authorization is performed if possible. The authorization result is displayed in the AuthorizeResult parameter.

If the AuthorizeResult parameter shows that authorization succeeded, you can decide whether to go on the shopping flow and capture payments eventually or to block the shopping. If you block the shopping, void the authorization by using Zuora’s Cancel authorization REST API with AuthTransactionId as the parameter.

If the AuthorizeResult parameter shows that authorization failed, stop the shopping flow and provide information to consumers.

EnrollCheckFailed

An issue occurred in the attempt to check whether the credit card was enrolled with 3D Secure. For example, the card issuer was unable to authenticate or did not respond.

For more information, see the Worldline Global Collect documentation .

Same as above.

AuthenticationFailed

Zuora attempted to perform authentication for a credit card enrolled with 3D Secure, but the payment gateway responded that authentication failed.

Same as above.

AuthenticationException

An unexpected exception occurred while preparing or during 3D authentication.

Same as above and contact Zuora Global Support .

PendingRedirect

The credit card was enrolled, and Zuora received the issuer bank’s URL and rendered it in the HPM iframe to ask for 3D Secure credentials. The 3D Secure flow was pending on waiting for consumer actions.

Wait for consumer inputs.

IssuerCallbackRecieved

Consumers entered 3D Secure credentials and submitted the Payment Page. The issuer triggered the callback, and Zuora received the callback.

Wait for the HPM callback of Zuora.

Zuora will validate the issuer callback first and then query the 3D Secure result with the payment gateway. At last Zuora will send the HPM callback by calling the callback function that you provided when rendering Payment Pages.

InvalidIssuerCallback

The issuer callback did not pass Zuora’s validation. The URL could be attacked, or other issues happened.

Stop the shopping flow and contact Zuora Global Support .

ValidatePassed

The issuer callback passed validation and Zuora sent a request to the corresponding payment gateway, and confirmed that consumers passed 3D Secure authentication.

Go on the shopping flow. If the AuthorizeResult parameter shows that authorization succeeded, call Create Account to create a billing account and a subscription and generate an invoice. However, you cannot collect money in this call. After making a call to Create Account , you obtain the invoice ID and account ID. Then, call Create a payment with the authTransactionId parameter to collect the money.

ValidateFailed

The issuer callback passed the validation and Zuora sent a request to the corresponding payment gateway and confirmed that consumer doesn’t pass 3D authentication.

Stop the shopping flow and provide feedback to consumers. Usually, the AuthorizeResult parameter is not Approved , indicating that the money is not authorized yet. However, if it is Approved , void the authorization by using Zuora’s Cancel authorization REST API with AuthTransactionId as the parameter.

AuthenticateValidationException

The issuer callback passed the validation and an unexpected exception occurred when Zuora tried to query the 3D Secure result with the corresponding payment gateway.

If the AuthorizeResult parameter shows that authorization succeeded, you can decide whether to go on the shopping flow or to stop it and void the authorized money. If the AuthorizeResult parameter shows that authorization failed, stop the shopping flow and contact Zuora Global Support .

Unknown

The issuer callback passed the validation. Zuora sent a request to the corresponding payment gateway to query the 3D Secure result, but did not receive any response because of network issues or other issues.

If the AuthorizeResult parameter shows that authorization succeeded, you can decide whether to go on the shopping flow or to stop it and void the authorized money. If the AuthorizeResult parameter shows that authorization failed, stop the shopping flow and contact Zuora Global Support .

ZeroAuthAmount

You provided 0 as the authorization amount or does not provide any value. Zuora 3D Secure for Payment Pages 2.0 does not support such situations.

Modify the HPM integration to provide a value greater than zero.