Qvalent QuickGateway provides payment gateway services that provides online credit card payment processing. This gateway is pre-integrated with Zuora and is both easy to configure and use.
Customers domiciled in Australia and New Zealand can use the Qvalent QuickGateway to process credit card transactions. Qvalent QuickGateway supports Visa, MasterCard, and American Express credit cards.
To set up Qvalent QuickGateway as your gateway, enter your Qvalent credentials in the Z-Payments Settings > Setup Payment Gateway page. When selecting a Gateway Type, choose Qvalent.
There are some common fields you must complete for every gateway configuration. We recommend reviewing our Setup Payment Gateway documentation for information on these common fields:
In addition to the common fields, every gateway has unique requirements and information (such as credentials and certain rules) that you must provide to configure the gateway in Zuora.
Your credentials will be obtained from Qvalent and configured in Zuora. To configure the Qvalent QuickGateway payment gateway in Zuora, you must enter the following information:
The user name that identifies your company. This value is assigned by QuickGateway.
The password is provided to you with your username.
The merchant identifier to use for the transaction, this allows you to have multiple merchant accounts. This is provided by QuickGateway.
The certificate file is provided by QuickGateway. A password is required to open the file.
The Electronic Commerce Indicator (ECI) is used by acquirers/issuers to determine the type of transaction being processed. The ECI value should represent the source of the transaction request. That is, the environment that the cardholder used to provide the payment card details to the merchant. It is important that merchants set the correct ECI value during transaction processing to ensure that appropriate merchant service rates are received.
in the Electronic Commerce Indicator list, select the channel through which your payment transactions are originating. This is a requirement from credit card networks, because different methods of acceptance can result in higher or lower transaction fees. For example, card present transactions (where the magnetic stripe on a card is read by a card reader) might have lower transaction fees than a card not present (telephone, online) transaction because the former method has a lower fraud risk.
order.cavvfields. Depending on your 3D Secure MPI software, you might need to convert the MasterCard ECI values to Visa ECI values.
Most of Zuora’s customers will likely use Recurring, but your specific selection should depend on where you are creating the payment. Check with your QuickGateway account manager or support team for the appropriate value.
If you select Channel Encrypted Transaction (SSL), there’s a chance that recurring transactions (which don’t have the CVV available to them) could fail for some credit cards because the card issuing bank might reject transactions that don't have a CVN/CVV value. If you find that occurring in your setup, consider setting the ECI Indicator to Recurring, which does not require the CVV value.
We recommend testing your selected payment gateway using both your payment gateway's test and production (live) environments. Once you have completed testing in the gateway's test environment, it is recommended that you perform a test in your live production environment with a real credit card. If there are any differences in the configuration of your testing and production accounts, testing in production ensures your production merchant account is set up properly and can successfully connect to the production environment.
Some payment gateways provide separate credentials for merchants to access their testing (or certification) environment, some gateways use the same credentials for testing as for the production (live) environment but direct test transactions to a different URL, and other gateways do a little of both. Qvalent QuickGateway provides you the ability to both test your transactions using a developer's test account as well as testing your transactions in your live account in test mode.
When configuring the Qvalent QuickGateway payment gateway in Zuora, you can indicate whether you would like to use the Qvalent QuickGateway test environment or the Qvalent QuickGateway production environment.
Zuora recommends that you contact your Qvalent implementation manager, account manager, or Qvalent support to request a set of test credit cards and testing scenarios.
Do not use real credit card information in your gateway's test environment.
In general, gateway testing environments are intended to give merchants the opportunity to test their gateway and integrations to their gateway, in order to work out any bugs before going to the production environment. Some gateway test environments are shared amongst multiple merchants, and other gateways provide unique testing environments for each merchant. Additionally, gateway test environments (also referred to as certification or sandbox environments) do not have the same high availability or performance capability as production environments. As such, they are not intended for load testing. Merchants performing high volumes of load testing that puts a stress on a shared test environment may receive a warning from the gateway or have their access to the testing environment suspended.
For failed payments processed using the Qvalent QuickGateway payment gateway, Z-Payments will provide the gateway Response Reason Code (for example, 44) and Response Reason Text (for example, This transaction has been declined).
To find more information on Qvalent QuickGateway payment gateway errors:
We recommend that you check the payment in Zuora to see how many times the same payment method has been retried for payment and failed. If there have been several retries, check the error messages from the beginning with the first failure and the more recent failures to determine if the error message is the same. If a merchant tries to process a payment against the same credit card too many times despite receiving errors, this could trigger warnings to the card issuing bank. The card issuing bank may place an alert on the account and not allow any further transactions from the merchant using that payment method. When a mechant has been flagged, the error received on the payment may be not state the reason why, instead it might be a generic error such as 2 - Declined. In this case, the merchant (Zuora customer) should work with their merchant acquirer/processor to see if they can identify the problem with the payment method. If the processor does not know, then the merchant and/or the card holder can try calling their card issuing bank to look into the issue
customer.orderNumbervia GatewayOptions through the Zuora API, you must ensure that your application prevents duplicate payments. Zuora and QuickGateway do not check to make sure that you have not sent a duplicate
customer.orderNumber, Zuora will generate a 32-character random alphanumeric value to Qvalent QuickGateway. This can help prevent duplication.