Set up and configure a Qvalent Quick gateway instance
Set up and configure a Qvalent Quick gateway instance by using the information in this article, including configuration procedure, descriptions of the configuration fields, and reference for testing the payment gateway.
Perform the following steps to set up and configure a Qvalent Quick gateway instance in Zuora:
- Click your username in the upper right and navigate to Settings > Payments > Setup Payment Gateway.
- On the Configure Gateway Instance tab, select Qvalent(QuickGateway) from the Gateway Type drop-down list.
- Click Create Gateway.
- On the gateway settings page, specify values for the configuration fields. See below for more information on the fields.
- Click Save Gateway Information.
Common configuration fields
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:
- Use Gateway Test Environment
- Cards Accepted
- Default Authorization Amount
- Verify new payment method (optional)
- Verify updated payment method (optional)
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:
User Name and Password
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.
Electronic Commerce Indicator
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.
- Call Center Transaction: The payment transactions originate from a call center.
- IVR Transaction: The payment transactions originate from an interactive voice response (IVR) system.
- MOTO Transaction: The payment transactions originate from mail order/telephone order (MOTO).
- Channel Encrypted Transaction (SSL or other): The payment transactions originate from an encrypted transaction.
- Recurring payment: The payment transactions originate from a recurring payment.
- ECI value 5/6/7 for 3D Secure transaction: The numeric ECI values are available only when the transaction contains the 3D Secure
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.
Test the configuration
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.
Accessing Your Gateway's Test 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.
Accessing the Qvalent QuickGateway Test or Production Environment from Zuora
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.
If you selected Use Gateway Test Environment, Zuora will direct payment transactions to the Qvalent QuickGateway certification environment at
If you have not selected Use Gateway Test Environment, Zuora will direct payment transactions to your Qvalent QuickGateway production environment at
Test Credit Cards and Testing scenarios
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.
General Testing Information
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.