What is Payments Testing?

Payments testing is a type of functional testing in which the Tester uses a payment instrument (PI) in order to verify the payment flow is working properly. Payment instruments include: Credit Cards, Debit Cards, Online Accounts (GPay, Apple Pay..etc). This includes:

  • verifying the total amount is calculated correctly,

  • the tax is calculated according to the country regulations,

  • the currency is displayed correctly,

  • the payment flow can be completed without an interruption

  • the payment flow can be interrupted/paused/dismissed at any moment without any issues

Typically, the Testers are required to perform the full flow, starting from adding an item to the basket through paying with the specific payment method. Often, you will be asked to cancel the order afterward.

Payments Testing task examples:

  • Sandbox payments testing for Client apps

  • Performing a purchase of an item from the online store with a defined payment method, canceling the purchase within 15 minutes to get a full refund

  • Purchasing a service with 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 task, where the testers are expected to make a payment (with a specific payment method) using a certain application or web link. Typically, the payment amount is small.

  • “Payout” testing task, where testers are expected to provide their account information (for a specific bank, wallet, or app). Afterward, it’s also necessary to confirm that you received the funds. The Client on their end is verifying the API call from the payment method.

  • On-site testing. Visiting a mini-market and performing cash payments for an item defined by the Client. Afterward, it’s also necessary to report back on the experience: experience, including ease of use and process speed, and to also report any issues during the process. You may also be asked for a store ID and Clerk’s name.

  • On-site testing that includes payment processing at a gas station, either at the pump, in-store, or both, using a predetermined amount specified in the Test Case.

    • Keep in mind US Gas Station merchants may hold up to $100.00 when using credit or debit cards using the payment terminal at the pump. The $100.00 needs to be available in the account in addition to the specified amount in the Test Case.

    • This amount is determined by the gas station and Not the Credit card company or Bank

    • The $100 hold can be avoided by using a PIN (at the pump terminal) or paying inside the Gas Station

  • Video recording full payment flow of the specified application. Please use our recommended blurring tools to blur sensitive data, and submit the recording with your task. The video recording will be used by the product team to analyze the payment flow usability, integration with payment apps, timeouts, etc.

How to prepare for Payments Testing?

  • Make sure your payment and location information is up to date on the Testlio profile. Testlio Services Team is using this information to compile the team for the needed workspace.

  • Order a separate bank card for testing purposes only - this way you can keep track of your personal funds and payments testing funds separately

  • Sign in to your eWallets, crypto wallets, online banks, payment apps to make sure your accounts are functional

  • If applicable, ensure the payment method is correctly connected to your store profiles (e.g., Apple ID, Google Pay ID, etc.)

  • 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 of the payments testing tasks involve verifying purchase confirmation emails. Best practices for the mailbox:

  • It is important to keep in mind 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 corresponding workspace environments.

  • Pay close attention to Test Run Instructions. Sometimes there may be a warning that purchases should NOT be fully completed because refunds cannot be processed (e.g. testing on production environments).

Check out our FAQ article for Payments Testing here.

We also have a whole webinar dedicated to Payments Testing, which you can watch and listen on Testlio Youtube channel.

Did this answer your question?