Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 15,000 merchants.
App Store chargebacks happen when cardholders dispute a bill for an app download or transaction made in a mobile app on Google Play/Apple's App Store.
TL;DR: App Store chargebacks happen when cardholders dispute a bill for an app download or transaction made within a mobile app on Google Play/Apple's App Store. The most frequent App Store chargeback is In-App Purchase chargeback (also known as IAP chargeback). To prevent IAP chargeback, you must ensure that all IAP transactions are clearly labeled, use anti-fraud tools to stop scammers in their tracks -- and automate your disputes for better ROI.
In-app purchases (IAP for short) are a crucial monetization strategy for mobile app developers.
With IAP, developers can make money by allowing users to purchase virtual goods or additional features within the app. These micro-transactions often build up into a sustainable business model for developers of freemium apps or products.
Yet, as with any financial transaction, there is always the risk of chargebacks.
More so, digital goods are traditionally prone to high rates of chargebacks, which negatively affects a merchant’s chargeback ratio – leading to severe consequences like hefty penalties and loss of processing rights.
Additionally, since Google has expanded the user choice billing program for Play Store, letting users choose alternative payment systems for in-app purchases, understanding how to mitigate IAP disputes on Google Play and Apple Store is vital.
Keep reading for details on how to fight and recover app store chargebacks. We shall take a deep dive into all the essential topics such as:
Let’s jump right in.
An App Store chargeback is when a cardholder disputes a charge on their credit or debit card for an app download or transaction made within a mobile app on Google Play or Apple's App Store.
As with other chargeback types, the card issuer will investigate the claim when a consumer initiates an App Store chargeback. If the claim is valid, the card issuer will reverse the transaction, giving a full refund to the cardholder. The app developer will lose the revenue from the sale. They may incur additional administrative costs, including chargeback fees if they wish to accept the chargeback.
Having said all that, it’s crucial to note that the most recurring App Store chargeback is in-app chargebacks. That is the main focus of this piece.
IAP chargebacks occur when the consumer claims that the purchase was unauthorized, fraudulent, or made in error. In such cases, the sources of grievance include virtual currency, like coins or gems, paid app features like ads removal, bonuses, or exclusive objects like optimized player health, player appearance enhancements, or options to circumvent time-limited functionality.
Both Google and Apple have established chargeback policies to protect consumers from unauthorized transactions and ensure fair play in the ecosystem. However, these policies cause frustration for app developers, as they often lead to IAP chargebacks.
For example, Google’s new policy, hinted at earlier, incentivizes developers who use third-party processing rather than the transactions being handled directly by Google.
The user choice billing program allows users to choose alternative payment systems for in-app purchases — to India, Australia, Indonesia, Japan, and the European Economic Area. With the new guidelines, Google gave a 4% discount on fees for developers using third-party billing.
While the program is advantageous for app developers, as third-party processors often have more flexible and lenient chargeback policies, the use of third-party processors also opens up the potential for fraud and scams.
App developers may work with processors with weak fraud prevention measures, which can lead to chargeback spikes. Additionally, third-party processors may not be subject to the same regulations and oversight as Google and Apple, which can also contribute to a higher rate of chargebacks.
However, what’s straightforward, what you should bear in mind is that in-app transaction chargebacks, like all CNP transactions, are the result of either criminal or friendly fraud.
Criminal fraud occurs when a scammer uses a cardholder’s credentials or card details to make unauthorized transactions. They usually pile up assets such as gems, coins, or extra game lives and then sell app access to the highest bidder on the black market.
The actual card owner realizes what’s happened and hits you with chargebacks.
Even though criminal fraud is a significant threat to app developers, the real kicker here is friendly fraud, which happens when a cardholder tries to game the system to get freebies. Sometimes, cardholders commit friendly fraud unknowingly.
In a nutshell, what we know about why IAP-friendly frauds happen are as follows:
While friendly fraud seems fun for cardholders, ​​it causes enormous damage to merchants. Industry data suggests merchants could lose $193 for a $1 chargeback this year, an increment from $34 in 2021.
As we noted earlier, in-app purchase chargebacks are natively card-not-prevent chargebacks.
Consequently, one essential step for mitigating in-app purchase chargebacks is to ensure that all IAP transactions are clearly labeled. Furthermore, inform users of impending charges before billing them. Provide clear descriptions of the virtual goods or features purchased and the purchase cost. And alert a parent when a minor makes an IAP.
If your business model is such that customers or users can circumvent in-app challenges in exchange for cash, you might want to rethink that, as it could lead to buyer’s remorse. Likewise, have clear and easy-to-use refund and cancellation policies in place.
Another vital step is to implement robust fraud detection and prevention measures.
Use secure payment methods, such as tokenization, encryption, and account verification. And monitor transactions for red flags that might trigger fraudulent chargebacks – such as multiple purchases from the same device/IP address or new users. Scammers frequently use stolen cards or billing details to stock up a new app account with in-app purchases and see the access. Be proactive in identifying and blocking such suspicious or fraudulent transactions.
Also, don’t forget to keep track of your chargeback ratio, which is the percentage of transactions that result in chargebacks. A high chargeback ratio can indicate a problem with the app's billing or refund policies due to lax business practices from your processor or a lack of fraud prevention measures.
App developers with high chargeback ratios risk suspension or ban from Google Play or Apple Store.
Like all digital goods, a lack of commensurate documentation that establishes the order's legitimacy means a 100% chargeback loss.
Here are some vital tips to improve your chances of winning App Store chargebacks.
Chargeback automation saves time and resources for developers. Instead of writing off chargebacks due to the dollar values involved, you can automate the process of responding to and managing chargebacks. You get:
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 15,000 merchants.