Non-payment authentication (NPA) offers the option to authenticate the customer even when there is no payment transaction happening or when the transaction amount is unknown. For example, the customer may want to store their card for future payments without making a purchase, or you might want to perform a (zero-amount) card verification transaction. NPA provides an easy way for you to authenticate the customer in these scenarios.

Authentication during registration

To perform a 3-D Secure authentication before you've tokenised the card, Peach Payments must enable the feature on the back-end. Contact support to enable this functionality.

Once activated, when the customer registers their card details, the system triggers a 3-D Secure authentication before the card registration.

📘

If you're performing a preauthorisation (PA) where sending createRegistration=true enables registration, the system triggers 3-D Secure authentication for the payment transaction, not for the registration.

For further information on how to tokenise cards, refer to the tokenisation guide.

Non-payment authentication for a payment transaction

It is possible to perform an NPA for a payment transaction, such as for an account verification transaction (zero-amount authorisation). You don't need to configure any extra settings or parameters, however, you must enable 3-D Secure. NPA is then triggered automatically for zero-amount PA transactions.

You can force NPA via an extra parameter. Even if the amount is not zero, sending the parameter threeDSecure.npa=true triggers an NPA instead of a regular 3-D Secure payment authentication with the payment amount. Be aware that the authenticated amount should always be the same as, or higher than, the payment amount.

📘

If you send amount=0.00 but threeDSecure.amount is greater than zero, the 3-D Secure authentication uses the amount from the threeDSecure.amount field.