Help your CFO rest easy with secure Payments Testing.

Is the app handling orders and performing all calculations as intended?

Is the payment processor meeting expectations when tested with multiple users and simultaneous transactions?

Are your customers met with confusing or unnecessary steps that lead to purchase abandonment and lost transactions?

Do your payment features honor and align the locale and geo-locations that matter to your customers?

Does the app seamlessly integrate with your chosen payment gateway and transaction flows?

Are sensitive credit card and CVV numbers securely transmitted?

Do your payment features and secure communications work across 100s of platform combinations or configurations?

Can your international customers make payments in their local currency?

One of our clients in the Netherlands, a cloud-based computer file transfer service, required payments testing for their regular credit card payments. They also needed testing on their proprietary payment system called iDEAL, which is the dominant payment gateway in the Netherlands.

As these were real payments and some were higher ticket items, Testlio first obtained a discount voucher from the client to pass along to the testers. We then secured a group of experienced testers from within the Testlio network. The testers were not only located in the Netherlands, but they also used their credit cards and iDEAL to conduct a variety of payment testing types including functional testing, security testing, compatibility testing, and location testing.

Before pushing an app update to the Google Play store, Testlio client, a real-time communications company, needed first to test their updated code to confirm it was compliant with the new requirements for the Google Play Billing Library. Testlio was brought in to test real purchases to validate that the app complied with the new Google Play Store requirements and to ensure that automated refunds of payments did not occur after three days.

To be safe, Testlio tested the entire real payment process on both Android and iOS. We utilized Sandbox testing, which enabled testers to login to an App Store account they own using all available test card types. This approach ensured no actual charges go through. The client pushed their fully compliant app with full acceptance.

When a Testlio client, a popular writing assistant app, wanted to monetize their product, they needed to test all user purchase variations to ensure they worked in the test environment.

Testlio performed sandbox testing on iOS to verify user access as well as the ability to purchase premium features, a high priority for the company. The payments testing initiative also included A/B testing experiments by presenting different pricing to a subset of app users. Through Testlio, the client was able to determine which pricing variation performed better and that the entire purchasing functionality worked as intended.

Many QSRs lead the way when it comes to app-driven customer experience, and payments testing becomes a vital part of the overall experience. QSRs use a variety of POS systems for their drive-thrus, partner systems, and mobile apps. Payments Testing helps them assure their systems link to credit cards, Apple Pay, and other digital payment services.

Extensive payments testing also helps QSRs better understand user experience for things like ordering ahead and app-based tipping. For example, A/B experiments help identify which type of tipping (e.g., percentage-based vs. incremental amounts) is more popular.

Also, it’s not uncommon for QSRs to have custom payment processes using backend technology from services like Infor, Oracle, or First Data. When payments fail, QSRs typically first go to these services to understand what happened. Unfortunately, the failures fall on the app side. Conducting extensive payments testing allows QSRs to tap into their logs and better pinpoint where the faults are happening.