Knowledge Center

Knowledge Center > Billing and Payments > Payment Gateways > Supported Payment Gateways > Merchant e-Solutions > Merchant e-Solutions Payment Gateway

Merchant e-Solutions Payment Gateway

Merchant e-Solutions is a full service payments provider that offers gateway, processor, and merchant acquiring services. Zuora is pre-integrated with the Merchant e-Solutions payment gateway.

Enable the Merchant e-Solutions Gateway for Your Tenant

Begin by contacting Zuora Global Support to enable the gateway in your tenant. 

Request a Test Profile (Optional)

If you would like a unique Merchant e-Solutions Test Profile for use with the integration, please submit this request to Zuora Global Support along with your support ticket for enabling the gateway in your tenant. Zuora Global Support will work with Merchant e-Solutions to establish this account and provide you an ID for the test environment. Review the section below on Accessing Your Gateway's Test Environment for more information on the available options for test accounts. 

Configure the Merchant e-Solutions Gateway

Once the gateway is enabled for your tenant, configure your gateway by going to  Z-Payments Settings > Setup Payment Gateway page. When selecting a Gateway Type, choose Merchant e-Solutions.

MeS Configure Gateway Type.jpg

Common Fields for Configuration

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:

  • Name
  • Use Gateway Test Environment
  • Credit Cards Accepted
  • Default Authorization Amount
  • Verify new credit card (optional)
  • Verify updated credit card (optional)

MeS Production Config.jpg

Credentials

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. 

Profile

A 20 digit number that identifies the source of the transaction requests. This is similar to a merchant ID in that it identifies which merchant account payment transactions are coming from.

Profile Key

A 32 character, alphanumeric password for the Profile ID..

IP Address

This is the IP address from which the payment transaction is sent to Merchant e-Solutions.

Use the Zuora IP address that corresponds to the Zuora environment (Production or API Sandbox) that you are using. If you are accessing your tenant using www.zuora.com (Production), use the IP address: 64.75.3.137. If you are accessing your tenant using www.apisandbox.zuora.com (API Sandbox) then use the IP address:  64.75.3.247. 

Moto eCommerce Indicator

Moto stands for non-card-present Mail/Telephone Order. From the pick list, select the method of acceptance for which your payment transactions are originating. This is a requirement from credit card networks as different methods of acceptance may 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) may have lower transaction fees than a card not present (telephone, online) transaction since the former has a lower fraud risk. The default to use is "eCommerce Transaction" however, when in doubt, check with your Merchant e-Solutions account manager or support team:

  • Not a Mail/Telephone Order Transaction
  • One Time Mail/Telephone Order Transaction
  • Installment Payment of a Mail/Telephone Order Transaction
  • Secure Electronic Commerce Transaction: A sale conducted through the internet using secure socket layers (SSL) with encryption strength of at least 128-bit.
  • Non-Authenticated Security Transaction at a 3-D secure-capable merchant
  • e-Commerce Transaction (Default): A sale conducted through the internet
  • Non-secure e-Commerce transaction: A sale conducted through the internet that is not secure. MeS documentation states that all e-Commerce transactions should be processed securely. 

Testing Your 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 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. To access the Merchant e-Solutions test environment, you have a couple of options: 

  1. Request access to a Merchant e-Solutions test environment that is shared with other Merchant e-Solutions merchants. To make this request, complete the certification request form online and Merchant e-Solutions will process the request and provide you with a test ID.
  2. Request a test profile linked to Zuora's merchant account which can be used with the integration.
    This profile is a unique test account that is not shared with other Merchant e-Solutions merchants. 
    As a Zuora customer using the integration, you can request a Merchant e-Solutions test profile that is linked to Zuora's merchant test account by logging a case with Zuora Global Support. A set of credentials will be provided for you to configure your Merchant e-Solutions test account in Zuora.

Accessing Test or Production (Live) Mode from Zuora

When configuring the Merchant e-Solutions payment gateway in Zuora, you can indicate whether you would like to use the Merchant e-Solutions test environment or the Merchant e-Solutions production environment. 

If Use Gateway Test Environment is selected, Zuora will direct payment transactions to the Merchant e-Solutions test environment.

The credentials used for this test environment are unique and different from the credentials used to access your Merchant e-Solutions production environment. If you are configuring the test account in API Sandbox, please use the Zuora API Sandbox IP address (64.75.3.247) in your configuration.

If Use Gateway Test Environment is not selected (disabled), Zuora will direct payment transactions to the Merchant e-Solutions production (live) environment. 

MeS Sandbox.jpg

Test Credit Cards and Testing Scenarios

Test credit cards and test scenarios are available here.

For additional guidance on testing, feel free to contact your Merchant e-Solutions Support team for assistance. 

General Testing Information

Integration Testing

Zuora has been certified with Merchant e-Solutions as an integration partner and maintains the integration on an ongoing basis, thoroughly testing the integration with every new release. The Merchant e-Solutions integration documentation is helpful if you are integrating the gateway directly with your website, however, you do not need to perform any integration or certification testing to submit transactions to the Merchant e-Solutions gateway via the Zuora application. The intended audience for the integration guides are technical integrators, however, these documents can be helpful to non-technical integrators who can refer to it for information on testing and troubleshooting gateway errors (as described below).

Performance and Volume Testing

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.

Troubleshooting Gateway Errors

There are several ways to obtain information on gateway errors:

  1. See Merchant e-Solutions Payment Gateway Testing for information on the payment gateway error codes. 
  2. Look up the transaction by the transaction ID number (in the Zuora payment detail page, this is the Reference ID and Secondary Reference ID numbers) in virtual terminal to see if more information is provided; often you will see more than just the response (reasons) code and response message in Zuora.
  3. For further assistance with gateway errors, you can contact the Merchant e-Solutions Support team for assistance. 

Make Sure You Are Not Re-Trying an Invalid Card Too Many Times

Zuora recommends 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 merchant has been flagged, the error received on the payment may be not state the reason why, instead it might be a generic error decline error. In this case, the merchant (Zuora customer) should work with Merchant e-Solutions 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.

Last modified
19:18, 7 Jan 2016

Tags

Classifications

(not set)