Overview of support for stored credential transactions
To comply with the Stored Credential Transactions (SCTs) framework, Zuora has provided support for SCTs for specific payment methods and payment gateways since 2019. By following the instructions in this configuration procedure, you can create and manage stored credential profiles within payment methods.
When creating a payment method, if you do not implement the support for SCTs on the payment method, the payment method will be created without the stored credential profile.
For payment methods created before Zuora released the support for SCTs, if you have not implemented Zuora's SCTs support on these payment methods, the payment methods do not have stored credential profiles within them.
Payment gateways
The following gateway integrations in Zuora support stored credential transactions.
Note that Chase Orbital Gateway integration supports both recurring and unscheduled stored credential transactions. The other integrations support only recurring stored credential transactions.
Payment gateway | Visa | Mastercard | Discover | American Express | JCB | Diners Club |
---|---|---|---|---|---|---|
Adyen Integration v2.0 | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
BlueSnap Gateway | ![]() |
![]() |
![]() |
![]() |
||
Braintree Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
|
Chase Orbital Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
|
Checkout.com | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
CyberSource, Payment API v2.0 | ![]() |
![]() |
![]() |
![]() |
||
First Data Payeezy Gateway | ![]() |
![]() |
![]() |
![]() |
||
Helix | ![]() |
![]() |
![]() |
|||
Moneris | ![]() |
![]() |
![]() |
![]() |
||
NMI Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Opayo Direct | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
PayPal Payflow | ![]() |
![]() |
![]() |
![]() |
||
Stripe v2 Payment Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Vantiv (Now Worldpay) Payment Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Vantiv Payment Gateway, API v8.10 | ![]() |
![]() |
![]() |
|||
Worldline Global Collect (previous Ingenico ePayments) | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Worldpay Payment Gateway | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
If you use a gateway that is not in the preceding table, Zuora will process payments as usual, but the payments will not comply with the Stored Credential Transaction framework.
Payment methods
Zuora supports stored credential transactions for the following types of payment methods:
- Credit Card
- Apple Pay
The following gateway integrations support stored credential transactions for both Credit Card and Apple Pay payment methods:
- Chase Paymentech Orbital Gateway
- CyberSource Payment API v2.0
- Vantiv (Now Worldpay)
- Checkout.com - For Apple Pay, only support generating stored credential profiles when processing payments if the CIT/MIT configuration is enabled. Generating stored credential profiles for Apple Pay when creating payment methods is not supported.
The other integrations support stored credential transactions only for Credit Card payment methods.
Stored credential profiles
Zuora supports the following types of stored credential profiles:
- Recurring profile: Indicates that you have obtained the customer’s consent to initiate future transactions at regular intervals.
- Unscheduled profile: Indicates that you have obtained the customer’s consent to initiate future transactions that do not occur on scheduled or regularly occurring transaction dates. Only one Unscheduled profile is allowed for each payment method. Currently, the Unscheduled profile is only supported in Chase Orbital Gateway integration.
When configuring your Zuora tenant, the goal is to contain an Active stored credential profile for the payment methods created on the preceding gateway instances.
Limitations
Currently, the following limitations are applicable to the support for stored credential transactions:
- The stored credential profile with the “Unscheduled” type is only supported for Chase Orbital Gateway integration.
- The transactions through the payment methods created using the following API operations are not stored credential transactions by default:
- Subscribe
- Create an account using Create
- CRUD: Create a payment method
- Create an order
- Create an order asynchronously
Related articles
For general information about Visa's Stored Credential Transaction framework, see Visa's guidance for merchants.