Testing Your Solution

1. Test Credentials

When testing, your code should use the following test credentials:

POST: https://ippostest.moneris.com/v3/Terminal/
{
 "apiVersion": "3.0",
 "apiToken": "example_apiToken",
 "storeId": "example_storeId",
 "istConfigCode": "example_istConfigCode",
 "postBackUrl":"https://ippostest.moneris.com/v3/Terminal/",
 "dataId": "example_dataId",
 "dataTimestamp": "example_dataTimestamp",
 "data": {
 "request": []
 }
}

2. Test Cards

Please contact Moneris Client Consulting team to request test cards. Client Consultant contact information may be found in Getting Help . Due to security and compliance reasons, the use of live credit and debit card numbers for testing is strictly prohibited. Only test credit and debit card numbers are to be utilized.

3. Test and Development Devices

Moneris can provide test and development devices to support the development and testing of Moneris Go integrations. The appropriate device depends on your integration type and the development or testing capabilities you require.

Test Devices

Test devices are configured to support functional testing of Moneris Go payment flows in the Moneris test environment and are designed to closely represent the expected behaviour of a production device.

Test devices are generally suitable for Cloud and Direct integrations, where your application runs separately from the Moneris Go device and communicates with the Moneris Go application through a supported external connection, such as IP over Wi-Fi or Ethernet.

Test devices can be used to:

• Test payment transactions and transaction flows
• Validate communication between your application and Moneris Go
• Perform functional and QA testing
• Test using Moneris test credentials and test cards

To maintain a configuration representative of a production device, standard test devices do not provide access to Android development and debugging capabilities. This includes the ability to sideload applications or use Android Debug Bridge (ADB).

If your testing approach requires these capabilities, such as using ADB to automate interactions with the device, a development device may be required even when testing a Cloud or Direct integration.

Development Devices

Development devices provide additional access to the underlying Android operating system to support application development, debugging and more advanced testing requirements.

A development device is required for App-to-App integrations, where your application runs directly on the Moneris Go device and must be installed and tested alongside the Moneris Go application.

Development devices also support use cases that require capabilities not available on a standard test device, including:

• Sideloading applications onto the device
• Using Android Debug Bridge (ADB)
• Debugging applications running on the device
• Automating testing or other interactions with the device screen using Android development tools
• Using other development or testing tools that require access to the underlying Android operating system

Development devices may be configured differently from standard test and production devices. Depending on your use case, you may therefore use a development device while building and automating your solution and a standard test device for functional testing in a configuration more representative of production.

Get a Device

Ready to start testing your integration or building an application? Review Supported Devices to explore the Moneris Go devices available for development and testing.

Once you've selected the right device for your integration, visit Order Devices to get started.

4. Simulator Host

The test environment has been designed to replicate our production environment as closely as possible. One major difference is that we are unable to send test transactions onto the production authorization network and thus Issuer responses are simulated. The test environment will approve and decline transactions based on the penny value of the amount sent.

For a list of all current test environment responses for various penny values, please see the Test Environment Penny Response Table.