- Overview
- Prerequisites
-
How does Test Mode work?
- How to toggle an active gateway account to Test Mode?
- Flush Test Transactions
- Can I move transactions that were processed in Test Mode to Active Mode?
- As the partner, how can I check to see when a merchant account was put in Test Mode?
- If the account is an Active account and we put it in Test Mode, is it still billable?
- When the account is in Test Mode, do the AVS and CVV data get passed?
- Is there a sandbox account for the payment gateway and test credit card/account number that we can use for testing?
- How do you trigger errors in Test Mode?
- Virtual Pin Pad Testing via the Virtual Terminal
- Can I test Payer Authentication 2.0 transactions in Test Mode?
- What cannot be tested in Test Mode?
- Video Tutorial
Overview
Test Mode allows the merchant to toggle their entire active gateway account into and out of Test Mode. While in Test Mode, merchants can submit test transactions to the Payment Gateway. Test transactions that are submitted while the account is in Test Mode are not live and do not charge real credit cards.
Prerequisites
The merchant's user will need the 'Access Administrative Options' permission to be able to toggle into and out of Test Mode. Primary users have this permission set by default and cannot be removed.
Navigating to Test Mode settings page - in the Merchant Portal, on the left side panel → click on Options → Settings → under Transaction Options click on Test Mode or from the homepage My Settings → All Settings → under Transaction Options click on Test Mode.
How does Test Mode work?
Test Mode is a helpful gateway feature for merchants who are setting up their website to accept payments so they can test functionality before starting to accept transactions. Keep in mind that if an account is in Test Mode, the gateway will simulate all valid credit cards to be approved but no charges will actually be processed and nothing will be sent to the credit card or ACH processor. Customers will not see charges on their accounts. The Gateway is simulating responses rather than reaching out to the Processor or Card Issuer for a real response. Test Mode is not user-specific (e.g. if one user puts the account in test mode then it is set for the entire account and every user who logs in will see it in test mode) and does not apply to specific sources.
***IMPORTANT*** Transactions run in test mode DO NOT process at the Bank and the Merchant will NOT be funded. Once you are done using Test Mode and ready to process live transactions, you MUST change the account back to 'Live Mode' by going to the Options menu in the Control Panel and disable Test Mode.
Any transactions, recurring subscriptions, customer vault IDs, or invoices that you create in Test Mode will not appear in live mode and any transactions, recurring subscriptions, customer vault IDs, or invoices created in live mode will not appear in Test Mode.
An account in Test Mode will have a pink pop up upon logging in, and a Test Mode notice will ‘hover’ in the upper right-hand corner once you close the popup.
How to toggle an active gateway account to Test Mode?
First, inform the merchant that by changing their live account to Test Mode will cause real transactions to NOT process and the merchant will NOT be funded.
Log in to the Merchant Portal, on the left side panel → click on Options → Settings → under Transaction Options click on Test Mode, from here click on the "Enable Test Mode" button; or from the homepage under Utilities → click on Settings → under Transaction Options click on Test Mode, from here click on the "Enable Test Mode" button.
You will follow the same steps when you are ready to disable Test Mode.
Flush Test Transactions
Test Transactions can be purged, or ‘Flushed’, using the tools in the Test Mode section. Simply select the type of record you wish to flush (Transactions, Subscriptions, Vault Records, Invoices, and Product Manager) and the Date Range, and click the "Flush Test Transactions" button.
This action is not reversible, and the information is NOT recoverable. Flushed records are purged from our databases.
Can I move transactions that were processed in Test Mode to Active Mode?
No. Transactions that were done in test mode CANNOT be moved to the Active Mode. Those transactions will have to be ran again in Active Mode. Please warn your merchants about this prior to activating Test Mode.
As the partner, how can I check to see when a merchant account was put in Test Mode?
To check when the merchant account was put into Test Mode, log in to your Partner Portal and head over to ‘List Accounts’ → click on the merchant account → under ‘Merchant Status’ click on ‘Edit’. This section will display a 'History' log where you can see when the status of the account was changed, by which user, and the date and time from oldest to newest. Test Mode status is Test
.
If the account is an Active account and we put it in Test Mode, is it still billable?
If you take an active account and put it into Test Mode, the account is still billable. However, the per-transactions fees are not. Meaning, when you are running a test transaction in Test Mode, the merchant is not being billed for the per transaction fees.
When the account is in Test Mode, do the AVS and CVV data get passed?
The AVS and CVV status will not be updated since that data is not being passed in a test account. This is a default setting.
However, if the merchant wants to test the AVS and CVV status we can enable a flag (listed below) that will allow the merchant to do so. We will need this request in an email. Please include the merchant's business name, their gateway ID, the request, and send it to support@nmi.com.
The flag is called 'Use New Test Mode Responses'.
Is there a sandbox account for the payment gateway and test credit card/account number that we can use for testing?
Transactions can be tested using one of two methods. First, transactions can be submitted to any merchant account that is in Test Mode. Second, the Payment Gateway Demo Account can be used for testing at any time. This account is always available and allows testing in a completely sandboxed environment. For more information, please visit our integration portal under the Dedicated test account section. The integration portal contains Test Data that you may use for either method.
You may also use the following username and password in your message for testing with this account:
username:demo
password:password
How do you trigger errors in Test Mode?
More information on triggering errors in Test Mode can be found in our integration portal - Testing Information, at the bottom of the page.
Virtual Pin Pad Testing via the Virtual Terminal
The Virtual Pin Pad (VPP) can be used for testing the Customer-Present Cloud API without a device and via the Virtual Terminal. To do so, use our virtual registration codes which can be submitted to any Test Gateway Account or a gateway account that is in Test Mode.
Use the T00001
code in the License Manager, and your virtual "fake" device will pop up into the Virtual Terminal Sale, Auth, and Credit pages. This registration code returns a valid “virtual” POI Device ID which will only work in test mode or a test account.
To use this code, in the Merchant Portal (while the account is in Test Mode) go to the left side panel → click on 'Options' → 'Settings' → under 'General Options' click on 'License Manager' → go to 'Registered Devices'* → enter this code in the 'Registration Code' field → click the 'Register' button.
*the 'Registered Devices' section is only available on merchant accounts that have the Value-added Service "Encrypted Devices" active.
- The virtual POI Device ID will be randomly generated, except for the last section, which will be all zeroes.
Example: XXXXXXXXX-XXXX-XXXX-XXXX-000000000000 - If developers wish to generate a failed registration, they can send
T00002
. This will simulate an invalid registration code error.
For more information on using the Virtual Pin Pad for testing the Customer-Present Cloud API without a device, please visit our Integration Portal → VPP Testing Information.
Can I test Payer Authentication 2.0 transactions in Test Mode?
Yes. Payer Authentication 2.0 can be tested when a merchant account is in Test Mode AND the merchant account has the Payer Authentication 2.0 service active on their merchant account. When a merchant toggles themselves into Test Mode, they can run test transactions that will use test credentials for the Payer Authentication 2.0 service they have active.
What cannot be tested in Test Mode?
- The Miura M0x0 will not work when the account is in test mode. When attempting a transaction with a Miura, the gateway account will need to be in live mode.
- Test Mode does not simulate Level III data entry. It will display the information entered, but will not display the 'Level III Data Success' line in the transaction history at the bottom of the detail, or in general reporting.
- Production Cloud Terminals will not work in Test Mode.
- Transaction Routing will work on a Test Gateway Account, but not a live account when the account is in Test Mode.