Stored credential transactions
Learn about Zuora's support for stored credential transactions, which can enhance authorization approval rates by indicating stored payment credentials.
In compliance with the Stored Credential Transaction framework, Zuora includes support for stored credential transactions for credit card, debit card, Apple Pay and Google Pay payment methods. Stored credential transactions enable you to indicate if transactions involve payment credentials that are stored on file. This can increase authorization approval rates.
To use stored credential transactions in a compliant way, you must establish a consent agreement with each of your customers. Zuora does not provide assistance with this. Instead, Zuora supports you to create and manage stored credential profiles within payment methods. Stored credential profiles represent the consent agreements that you have established outside of Zuora’s system.
How Zuora uses stored credential profiles
A stored credential profile represents the consent agreement between you and your customer for future use of a saved payment method.
When you use a payment method in a transaction, Zuora uses the stored credential profile to send the appropriate stored credential indicators to the payment gateway and associates the transaction with the existing consent agreement.
Zuora also stores the network transaction identifier (NTI) that the payment gateway returns. Zuora uses this value in later transactions when the gateway and transaction flow support stored credential transactions.
For supported Mastercard stored credential transaction flows, Zuora can also store the Mastercard Transaction Link Identifier (TLID) that a payment gateway returns. Zuora stores this value with the stored credential profile and can use it in later related Mastercard transactions when the gateway and transaction flow require it.
The TLID complements the existing network transaction identifier behavior. Some gateway flows continue to require the existing network transaction reference together with the TLID. If a payment method does not already have a TLID, a later qualifying transaction can return one that Zuora then stores for future use.