A payment method in Zuora can be either electronic or external. An electronic payment method is the actual information, for example credit card number, used to process an electronic payment with a gateway or processor. External payments are payments which occurred through a different system and are recorded in Zuora. Examples of external payment methods include check or wire transfer. Payment methods are stored on each Zuora customer account. You have the option to identify which payment method is default (more than one payment method can be stored in a customer account), but you can use any payment method to process a payment. Each payment method has a unique ID (a token) in Zuora. It is not possible to display the full account information (such as the unencrypted credit card number or ACH account number), however, it is possible to use this unique ID to retrieve and display certain payment method information, such as address and expiration date.
Payment methods can be created via the Zuora user interface, Z-Force, API, or using Zuora's Hosted Payment Pages (a premium feature). Zuora is PCI compliant so you can use our Z-Payments page embedded on your website to allow your customer to enter and store new electronic payment method information directly into Zuora. Regardless of how you enter the the payment method in Zuora, Zuora will provide a unique id/token that you can use to manage the payment methods or create new payments.
For customers that are not PCI compliant, Zuora's best practice is to use PCI-compliant hosted payment method page or Zuora user interfaces to create new payment methods.
For customers that are PCI compliant, best practice is to use Zuora APIs in addition to any of the above means.
Once the Payment Method is created, you can allow your customer to manage their payment method without having to be concerned with PCI compliance. The most common use cases are:
- Update Payment Method expiration date: By using the token to identify a specific Zuora credit card payment method, you can allow your customer to modify that method's expiration date. However, it is not possible to update the credit card number when you update the payment method. Zuora also has added the flexibility to automatically re-validate the payment method with the updated credit card information with your Zuora gateway. By allowing your customer to update their payment method expiration date online, you can increase the likelihood that future payments will be successfully processed for this customer.
- Update Payment Method Address: If you are using the address as part of your validation, by using the Address Verification Service (AVS) with the gateway, it is recommended that you allow your customer to update the address associated with that payment method.
- Select default payment method: For most subscription businesses, changing the default payment method is really replacing the payment method. Unless you have a specific use case, the goal of the default payment method is to have a payment method on file for recurring payments. This is very different from the product based world where you may choose to purchase one order with one credit card (for example, your personal card) and a follow on order with another card (for example, your corporate card). With this in mind, many customers only create new payment methods to replace the existing default payment method. Nevertheless, Zuora supports a model where you can store multiple payment methods and allow your customers to select their own default payment method at any time.
Zuora also supports automated services such as the payment method updater where you can request automatic updates of Visa and/or MasterCard information.
- Configure Payment Method Retry Rules
- Zuora allows you to retry payments on a scheduled basis by using scheduled payment runs which will process any invoices that have not been fully paid for customers who have auto-pay enabled. You can also specify the maximum number of consecutive times a failed payment method (for example, credit card) is retried for payment, as well as the ability to define a time period to not retry a payment. For instance if you define the interval as 8 hours, an automated payment retry will not attempt a payment if the last failed payment was less than 8 hours ago.
- Supported Payment Methods
- This topic describes the payment methods supported by the payment gateways. Empty fields in the tables indicate that the payment method is not supported by that payment gateway.
- Direct Debit for GlobalCollect
- Direct debit is a way of collecting funds for a payment directly from a customer’s bank account. It is a very common method of payment in many countries and is frequently used for payment of utilities (such as telephone bills) or mortgage which occur on a recurring basis.
- Implementing Direct Debit with GlobalCollect
- Although direct debit is treated like any other electronic payment method in Zuora, there are additional steps that you need to perform to implement this payment method. These topics provide an overview of implementing and managing direct debit transactions using the Zuora-GlobalCollect integration. During your integration please contact your GlobalCollect integration manager or Zuora Global Support for assistance.Your GlobalCollect integration manager will provide you documentation and guides to implement direct debit for the specific countries you want to support. For example, direct debit in the United Kingdon has different rules and regulations than direct debit in Germany.
- Direct Debit Mandates
- Unlike credit cards, you (the merchant) must obtain authorization from your customers to debit their bank account for payment. This authorization can be a confirmation page on the your web store in which authorization is confirmed by your customer when they accept your stated terms and conditions. Alternatively, the authorization can be provided using a signed agreement called a mandate.
- Obtaining and Processing Mandates
- Mandates are obtained and maintained by you (the merchant) and not by Zuora or your payment services provider, GlobalCollect. The mandate information along with your customer’s bank account information is submitted to GlobalCollect with each payment transaction request.
- Retaining Mandates
- You, the merchant, are required to keep a mandate up to date for as long as you continue to debit your customer’s account.
- Payment Method Updaters
- Maintaining updated payment methods is important to avoiding loss in revenue due to failed payments. Failed payments can occur due to invalid credit cards; credit cards can become invalid for a number of reasons such as the expiration date has passed or the account has been closed. It is equally important to manage credit card updates with as little interruption to the end customer as possible. Zuora customers who have signed up with either the CyberSource Account Updater or Litle & Co. Automatic Account Updater Service can use Zuora's integration to these payment method updater services to retrieve updated Visa and/or MasterCard information without ever contacting the end customer. Zuora's integrations of the CyberSource Account Updater and the Litle & Co. Automatic Account Updater are different from each other, and thus the use and configuration of each payment method updater also vary. Customers' interested in using the payment method updater feature must first register for the account updater services with the provider of their choice and review the prerequisites. See Configure the CyberSource Account Updater and Configure the Litle & Co. Updater for information about setting up the specific updaters. Note: The Litle & Co. and Cybersource Account Updaters are controlled-release features. Contact Zuora Global Support if you are interested in using this feature.
- Configure the CyberSource Payment Method Updater
- The CyberSource Account Updater is supported by the Zuora payment method updater feature. Each payment method updater (for example, Cybersource Account Updater or Litle & Co. Automatic Account Updater) has different requirements and the setup screens will vary. The following steps below will walk you through the configuration for setting up the CyberSource Account Updater in Zuora.
- CyberSource Account Updater Request File
- When you set up a payment method updater, Z-Billing will start a daily automated scheduler process which searches for Visa and/or MasterCard credit cards which may require updates. This scheduler process will collect all applicable credit card information and send it to CyberSource in a batch request file; CyberSource receives the file, validates it, then sends it to the Visa and/or MasterCard networks checking for updates. The method of preparing the batch request file and which credit cards are included in the batch request file is documented below. Once the batch has been submitted to the CyberSource Account Updater, users can view the status of all files from within the payment method updater console in Zuora.
- Payment Method Updater Console
- Zuora provides a payment method updater console for use with the CyberSource Account Updater. This console helps users track and manage the batch files and payment method information sent to the CyberSource Account Updater service. The console can be accessed by going to Zuora > Z-Payments > Payment Operations > Payment Method Updater.
- Configure the Litle & Co. Updater (Beginner)
- Authorize.net Gateway (Intermediate)
- Chase Paymentech Orbital Gateway (Salem Platform) (Intermediate)
- Chase Paymentech Spectrum (Intermediate)
- CyberSource Payment Gateway (Intermediate)
- Litle Payment Gateway (Intermediate)
- PayPal Payflow Pro, Website Payments Payflow Edition, Website Pro Payment Gateway (Intermediate)
- How do I configure the frequency of the Payment Method Updater?
- Selecting and Signing Up for a Payment Gateway
- How do I bill a customer for a new purchase without using the default payment method in the API?
- How do I handle ACH or Direct Debit payments that are reversed?
- How do I handle closed credit card accounts?
- How do I handle credit cards that have reached the maximum # of retries?
- How do I improve cash collections?
- How do I set up a PCI-compliant page to accept new payment methods?
- How do I support direct debit (such as ACH) payments?
- How do I use the credit card reference transaction payment method in Zuora?
- How do I use the Paypal BAID payment method in Zuora?
- How do I use Zuora with my existing website?
- How should I manage the credit card payment exception handling process?