Real Payments - Summary

Quickly learn about Active and Passive Real Payments

Zorica Micanovic avatar
Written by Zorica Micanovic
Updated over a week ago

What is Real Payments Testing

Real Payment Tests happen when customers need to perform real monetary transactions in production (LIVE) environments to catch bugs not only during the last step of the checkout page but also after the user completes the order. Customers might also want to test the integration with third-party payment service providers, new payment methods or simply check for problems real users might face when completing a payment.

Real Payment Tests require extra attention from our testers since they will use real and valid payment methods to complete the transactions. This article will help you get familiar with common test types under Real Payments tests, use cases, terminologies and best practices to succeed while completing the cycle tasks.

We encourage you to watch the recording from our Real Payments Testing Webinar that explains everything you need to know about this topic.

Distinguishing Passive Real Payments Testing from Active Real Payments Testing

In your Test IO Real Payments journey, you’ll encounter two main types of testing. It’s important to understand the differences between them as your obligations will be completely different, as well as your time commitment for each of them.

Active Real Payments Testing

Active Real Payments Testing involves testers directly engaging in the purchasing flow using real credit card credentials without the direct involvement of the customer. Testers simulate the entire transaction process, from initiating a purchase to finalizing the payment, to assess the system's functionality, security, and performance.

Passive Real Payments Testing

In contrast, Passive Real Payments Testing diverges from the traditional method by incorporating a different approach. Testers don't directly execute the payment process but instead share their payment methods, including full card details or login accesses to e-wallets, through a specialized and encrypted interface with the customer. The actual testing is then managed by the customers themselves. This method aims to mimic a real transaction without the testers directly participating in the payment process.

Using fake or test data

For Real Payment cycles, you will not be allowed to use any dummy data, test cards, or test accounts for third-party payment tools.

Remember, you are testing a production environment so test cards will usually be blocked by apps or websites. You should also not use payment information from other people unless you are authorized by the owner of the information and with written confirmation from one of the Test IO employees. Any attempt to fraud or to cheat the payment system will result in penalties on our platform.

The instructions are not clear, or are you in doubt?

If you're not sure about what needs to be done or find any instructions confusing, please ask for help from the Team Leader (TL), Community Project Coordinator (CPC) or Project Manager (PM) instead of completing a task without assistance. If you make any mistake while doing a task, you may face several sanctions on our platform, such as:

  • Not getting the reimbursement for the transaction.

  • Not being invited for future Real Payment cycles.

  • Getting banned from the Test IO platform.

  • Legal actions against you if any crime is committed.

Remember, you are dealing with a real purchase, so always ask for help if anything different happens than what you expected or if you have any questions.

Did this answer your question?