How you test depends on which integration path you're building — see Choose your integration method if you haven't decided yet.
Applies to both the Android app and Web POS paths. All external testing uses the same Tap to Pay app.
The payment processing environment is determined by the POS client ID — each POS application should have a POS client ID for each POS environment.
Merchant accounts aren't available for Sandbox. Because of this limitation, you must use a production merchant account to sign into the Sandbox testing app.
| POS | Payments | Merchant account |
|---|---|---|
| Production | Production | Production |
| Sandbox | Sandbox | Production |
Install the appropriate Tap to Pay build on your test device. For the Android app path, the package ID you target is declared in your manifest:
| Environment | Package ID | Manifest value |
|---|---|---|
| Production | com.tyro.softpos | com.tyro.taptopay.client.id=com.tyro.softpos |
| UAT | com.tyro.softpos.uat | com.tyro.taptopay.client.id=com.tyro.softpos.uat |
Tap to Pay offers a demo/simulator mode for development. Ask Tyro to enable it for your POS client ID.
Obtain sandbox credentials and a merchant ID by contacting Tyro. Use your new credentials and merchant ID to test your integration in our sandbox environment.
The following features are supported in our sandbox environment.
- List Embedded Payments Locations.
- Create a Reader. Reader creation is restricted in our sandbox environment. The Reader returned will be preconfigured by Tyro, hence you might receive the same reader webhook notification multiple times per create request, this is expected behaviour. Optionally you can List Readers instead.
- Create a Embedded Payments connection with the returned Reader ID. This connection can be used to submit transactions using our Embedded Payments SDK on the sandbox environment.
- Authorise a Sandbox Merchant Id. This allows you authorise a merchant Id on the sandbox environment so you can test your Account Authorisation Integration.
Our sandbox environment currently provides the TAPTOPAY_READER_CREATED Reader Webhook Event which returns preconfigured readers, and Merchant ID Authorisation Events (via the test endpoint Authorise a Sandbox Merchant Id), other webhook events are currently not supported. As a result, only a subset of the Account Authorisation flow can be tested on sandbox.
Fetching transactions is also not supported on sandbox.
Use any card to test transactions from your mobile device. Transactions on the sandbox environment will not be charged.
- American Express Payment Test App (available on Google Play) — if you have a second Android device you can use this app to perform Tap to Pay transactions to test sandbox payments.
- XP Card 03 appears to trigger a declined transaction from the American Express Payment Test App.
- XP Card 01 can trigger the signature flow for a transaction value over $200.
Once you're testing against the formal test matrix, see Certification.