Key Configurations and Limitations of the MockPI Sandbox Environment
The MockPI sandbox environment is designed to simulate merchant and transaction processing scenarios. Below are the key configurations and limitations to be aware of when using this sandbox:
Sandbox Data Structuring
Merchant ID (MID) and Terminal ID (TID) Formation
MID Structure: In the MockPI sandbox, any 8-digit number can be used as the Merchant ID (MID). This provides flexibility for testing purposes.
TID Structure: Terminal IDs (TIDs) are derived from the MID by appending two additional digits to the end of the MID. For example, if the MID is 12345678, a valid TID could be 1234567811. This structure ensures consistency and simplicity in sandbox testing environments.
Simulating outcomes
Mock PI supports magic numbers which allows you to simulate various outcomes as well as triggering specific functionality. Documentation can be found on https://developer.softpay.io/softpay/sandbox-testing.html?p=payment-integrator-mock#transaction-response-mapping
Sandbox Limitations
Masked Card Data
Non-Meaningful Masked Data: When using the Mock acquirer or processor in the sandbox, masked card data may appear unusual or non-meaningful. This is a known limitation of the Mock acquirer setup, and the masked values do not resemble real Primary Account Number (PAN) patterns. Users should be aware of this limitation when testing scenarios that involve masked card data.
Summary
The MockPI sandbox provides a flexible environment for testing merchant and transaction processing setups. While it allows for customizable MID and TID structures, users should note the limitations regarding masked card data, which may not reflect real-world patterns.
Related Topics
Setting up merchant credentials in the sandbox
Understanding sandbox limitations
Testing transaction flows in MockPI