What is Payments Testing?
Payments testing is a type of functional testing in which a tester uses a payment method to verify a payment flow is working properly. Payment methods include: credit cards, debit cards, digital wallets (such as Apple Pay, Google Pay). Such testing may include:
Verifying the total amount is calculated correctly
The tax is calculated according to the country's regulations
The currency is displayed correctly
The payment flow can be completed without interruption
The payment flow can be interrupted/paused/dismissed at any moment without any issues
Typically, testers are required to perform the full flow, starting from adding an item to their basket through paying with the specific payment method. They often cancel the order afterward.
Payments Testing Example Tasks
Sandbox payments testing for client apps.
Purchasing an item from an online store with a defined payment method and canceling the purchase within 15 minutes to get a full refund.
Purchasing a service from a client, including a 99% discount code.
Verifying location-specific pricing. The main goal of the task is to verify that the expected and actual price of the product or service matches the specific country.
“Pay-In” testing: Testers are expected to make a payment (with a specific payment method) using a certain app or web link. Typically, the payment amount is small.
“Payout” testing: Testers are expected to provide their account information (for a specific bank, wallet, or app). They then confirm they received the funds. The client verifies the communication between the payment system nodes.
On-site testing: Visiting a store such as a mini-market and conducting a cash transaction for an item defined by the client. Testers then report back on the experience, including ease of use and process speed and also any issues during the process.
On-site testing: Payment processing at a gas station, either at the pump, in-store, or both, using a predetermined amount. This may include a hold on an additional amount on the payment method.
Video recording the full payment flow for a specified app. This needs to include blurring sensitive data. The recording is used product team to analyze the payment flow usability, integration with payment apps, timeouts, and more.
Prepare for Payments Testing
See some actions to take to get yourself ready to conduct payments testing:
Complete Payments Testing Basics training in the Testlio Academy.
Make sure your payment and location information is up to date in your Testlio profile. This information is used to compile teams for workspaces.
Order a separate bank card for testing purposes only – so you can keep track of your personal funds and payments testing funds separately.
Sign in to your digital wallets, crypto wallets, online banks, and payment apps to make sure your accounts are functional.
If applicable, ensure each payment method is correctly connected to your digital wallets (such as your Apple ID, Google Pay ID).
Keep your cards available to use, including sign-in credentials & pin codes.
Dedicate a separate budget for payments testing – this is your investment in getting more testing opportunities.
Make sure you have a functional mailbox that can be used for testing purposes as most payment testing tasks involve verifying purchase confirmation emails. Best practices for the mailbox:
Email functions, such as filters, should be avoided.
Create a sub-address per workspace. For example,
margaret.marks+WorkspaceName@gmail.com.
Remember that while you are testing any product on the Testlio platform that is not yet available to the public, you have to protect the information and not discuss the product details outside of the workspace.
Pay close attention to the test run instructions. Sometimes they may include a warning that purchases should NOT be fully completed because refunds cannot be processed (such as when testing on production environments).
FAQ
Do I need to be an expert in finances in order to do payments testing?
No, you don’t. Handling your daily financial life (having a bank account, making online payments) already indicates you understand common payment flows. If we need a specific financial background, it is specified and communicated before testing.
Similarly, if your credit score is important to meet testing requirements, it is checked separately.
Do I need to share my private information?
No one should require access to your financial accounts. If anyone ever asks you for such access, please always flag it to the Testlio team (the Engagement Manager or Testing Manager) or raise a concern.
It’s rather rare that you need to share your private information. In some cases, you may need to share your bank account details. Please note that private information is not be shared with third parties and is only used for product analysis purposes.
How to get reimbursed for processed payments?
All funds that you use during testing are reimbursed. This includes transaction fees, conversion fees, and compensation for the time to reach a location for on-site payments. Please note that you will not lose any money for conducting payments testing on the Testlio platform.
Refund and reimbursement processes are documented in the workspace. To learn about the process before accepting a workspace invitation, ask the Testlio team. All possible refund options are defined with the client. The most common methods are:
Refund by the client. You need to share the transaction ID, account ID, and receipt.
Refund by Testlio with a direct funds transfer. You need to provide a receipt or account statement.
How much money will I need to have available while participating in payments testing?
Generally, it's recommended to have a separate budget that is available for testing. Funds can be transferred to linked accounts for testing purposes.
In some cases, it will be clear in advance how much money is needed to have available. You will learn this before you start testing.
Keep in mind that some test runs take place with the production app and the payout is determined in the run acceptance. In such cases, make purchases at the lowest possible price. Keeping the amount low benefit the client, Testlio, and you as the tester. Maximizing your purchasing power while staying within the client’s budget benefits everyone.
We also have an entire webinar dedicated to payments testing.
#TestlioBot