Generating a Nonce for 3-D Secure Authentication

Generate a nonce from a registered payment method for 3-D Secure credit card verification.

Using the SubMan APIs, request that a payment one-time token is created based on a subscriber/group payment method. The call can specify the payment method and can include Payment Gateway Provider-specific fields. If a payment method is not specified, the default is used. The Payment Gateway Provider returns a nonce and any extensions in MtxResponsePaymentOneTimeToken. The 3-D Secure authorization data is included in MtxBraintreeResponseExtension.

Note: If you have configured the MtxBraintreeChargeMethodExtension to require 3-D Secure verification by setting ThreeDSecureRequired to true, you can generate a nonce from a registered payment.
MtxBraintreeResponseExtension 3-D Secure Fields describes the 3-D Secure information.
Table 1. MtxBraintreeResponseExtension 3-D Secure Fields
Field Type Flag Description
ThreeDSecureEnrolled String Optional Indicates whether a card is enrolled in 3-D Secure.
ThreeDSecureLiabilityShifted Bool Optional Indicates whether the liability shifted or not.
ThreeDSecureLiabilityShiftPossible Bool Optional Indicates whether a liability shift is possible.
ThreeDSecureRequired Bool Optional Indicates whether to require 3-D Secure verification to succeed before creating a transaction. Defaults to true for all transactions sent through 3-D Secure verification unless you explicitly pass false.
ThreeDSecureStatus String Optional The 3-D Secure status value.

For more information about generating the nonce using the SubMan APIs, see the discussion about managing payment methods.