Your Testing Pays account provides features for you to test all aspects of your payments integration. You can concentrate on building the best payment features for your customers.
Check out some of the features:
Testing Pays has powerful simulators for many API endpoints and operations. For example, there's a simulator for Stripe charges, a simulator for Realex 3D secure flows, a simulator for PayPal Express, etc.
With a simple copy&paste, you can point your development and test environments at your team's account, then you're ready to send test transactions to the simulators - they'll respond as if your code is talking to the real thing.
And the icing on the cake? Your simulators are just for you (and your team). Unlike traditional sandboxes, your simulators aren't shared with other merchants. Even better, you have control over the simulator settings, such as latency settings.
Each API simulator has a table of all possible API response codes. The table maps the response codes to request values. If you send in a value in your test request, then it will trigger the simulator to send back the response code it maps to in the table.
The default trigger parameter is usually related to the transaction amount (i.e. "charge_total" for Authipay's APIs) - you can trigger specific response codes with the decimal value in the transaction amount. You also have the option to use the CVV or the Cardholder name fields as trigger parameters - just select the trigger value you want in the Settings of the simulator you're testing.
Say goodbye to crappy test cards. Enjoy testing any response you need when you need. Your imagination is your limit.
Every simulator comes with integration guides, tips and links to sample apps. The instructions come in multiple coding languagues.
Create your Testing Pays account, open up the API simulator you want, and select the "Integrate" tab to see integration instructions."
We regularly build and update our own example applications. And we believe in sharing what we've learnt. You can check out the code for our examples on our Testing Pays GitHub account.
Each simulator also comes with its own test report. As you and your team hit the simulator with test transactions, the reports will tell you what you've tested, what you haven't tested, the amount of response codes you've covered
Use the test reports to: firstly capture how much coverage you're achieving with your current test plans, then to drive higher levels of coverage in your testing.
Live Log gives you a window into each simulator as it processes your test requests. In real-time, you can see each transaction as it hits. The Live Log gives you visibility into how your request is treated, and the response being assembled and sent back. If the simulator finds a problem with your request, you'll also see verbose explanations in the Live Log.
Everything is clearly timestamped so that you can be confident in the simulator roundtrip time for your testing. Simulator response time is consistently under 100ms - unless of course you've activated its 'latency' setting to introduce artificial overhead!
Ever played Pong? Tail your local logs on your dev machine, and in a browser window start the Live Logs on the simulator, then fire off some test requests. Sit back and watch your requests hitting the simulator, and responses bouncing back to your local logs.
Your checkout should never go down during Cyber Monday, Christmas sales or any peak sale event. So testing your store under load is vital. Our load test simulators can support your efforts.
Use our load test simulators in conjunction with a load test tool to test your checkout. The simulators can handle millions of requests for overnight or weekend test runs, providing a constant response time of less than 100ms and concurrency up to 80 transaction per seconds.
Our load test simulators must be booked in advance. To book, log into your Testing Pays account, go to your "CURRENT TEAM" menu and complete the simple booking form. The team will respond within an hour with connection details.
Find out some of the things you can do with Testing Pays.