Was this article helpful?

How do I control when Zuora will authorize the Payment Method?

Overview

In Zuora, you can control whether Zuora sends a Payment Method Authorization to the gateway when adding a new payment method or when updating an existing payment method.

Solution

When you configure a payment gateway in Zuora, you can choose to send a Payment Method Authorization to validate a payment method when you create a new payment method, update a payment method, or in both cases. If you do not select either of these options, Zuora will not send the Payment Method authorization to the gateway.

Best Practices

Zuora recommends that you configure your payment gateway to authorize both new and updated payment methods. If you have Zuora validate at these times, the payment method you have on file will have been authorized when you attempt a payment.

If you choose not to validate a payment method,  the record in Zuora is created but has not been validated for accuracy by the gateway. There is a gateway cost associated with the authorization, and advanced users may decide that the benefit of performing this validation does not outweigh the cost for their specific use case.

Multiple Authorization Settings

You can configure different authorization settings for groups of customers by using Zuora's multiple payment gateway functionality. For example, you can have your business-to-consumer (B2C) customers authorize on both new and updated payment methods and your business-to-business (B2B) customers authorize only on newly-created payment methods. Follow these steps:

  1. Create two gateways in Zuora with the same credentials but using different validation settings for B2B and B2C customers. 
  2. Associate the appropriate Zuora Gateway to a customer account, and Zuora will perform Payment Method Authorizations based on the value you have defined in each Zuora gateway.

Related

Topics
Payment Method
Zuora offers three payment method options: Z-Payment Method, External Payment Method, or None. See Payment Methods for more 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.
Payment Methods
The payment method refers to the form of payment customers are using. For online purchases, they usually take the form of electronic payments like credit cards, debit cards, bank transfers, third-party processors (such as Paypal), or non-electronic payments like checks and cash.  The customer's method of payment can be created and edited in the customer account. To learn more, and to configure payment methods, see Define Payment Methods.
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.
Customer Notifications for Direct Debit
Some countries require you, the merchant, to provide the customer with advance notice before debiting the customer's account for payment, while other countries may not require it but consider it a best practice. Advance notice is especially important when the recurring fees have changed, for example, the customer purchased an additional product this month.
Payment Gateways
A payment gateway is an online service provider that connects an electronic shopping cart or virtual terminal/POS to an electronic payment processor. It is your gateway to the rest of the payments infrastructure that allows you to accept electronic forms of payment. The main function of a gateway is to pass authorization and settlement data securely to and from the merchant's website to the merchant's processor. The merchant processor in turn connects to the card association (or "network"), which connects to the card issuing bank. The articles in this section explain more about the participants in the payments ecosystem, and put gateways in the right context.
The Payments Value Chain
The payments ecosystem is very fragmented, due to a high degree of specialization, and any given payment transaction typically passes through at least five or six different parties, which we may call the payments value chain. See the following sections to learn about the various participants in the payments ecosystem, and the sometimes subtle differences in their functions.
Supported Payment Gateways
Zuora currently supports the following payment gateways: Authorize.net  Chase Paymentech Orbital (Salem Platform) Chase Paymentech Spectrum (controlled release) CyberSource  GlobalCollect Litle  Merchant e-Solutions  Moneris (eSelectPLUS Canada) PayPal Adaptive Payments PayPal Payflow Pro Verifi  Note: Support for the Chase Paymentech Spectrum is a Controlled Release feature, and is a premium service offered by Zuora. Contact Zuora Global Support for information about using this payment gateway.
Managing Payment Gateways
After you are done selecting a payment gateway, you will need to do a certain amount of configuring in order to set up your gateway and get going with accepting payments. This section of the documentation will guide you through configuring common Zuora-supported payment gateways, then going live with these gateways, and even disabling and troubleshooting if things go wrong. Finally, we will show you when you might need to use multiple payment gateways, and how to make it work.
Required Configuration Fields By Gateway
You can set up Z-Payments to use one preferred payment gateway. Because each gateway has different requirements, the setup screen for each of these payment gateways varies. Contact your payment gateway to obtain the information required to configure the gateway in Zuora.
Verify Credit Card Gateway Options
Z-Payments provides options to verify new and updated credit cards. These settings are applied at the gateway level, and can be different for different gateways, but they apply to all cards that are authorized through that gateway.
Tutorials
Troubleshooting
References



 

Was this article helpful?
Page statistics
631 view(s), 9 edit(s) and 2877 character(s)

Tags

Comments

You must to post a comment.

Attach file

Attachments