Investigating duplicate AI subscription charges: a classification case study
How to separate a single pending authorization from genuinely overlapping subscriptions across web, Apple, and Google, and the decision process for keeping the right plan and cancelling the others.
The scenario: two similar lines appear on a bank statement. The worst response is to keep buying, cancelling, or deleting the account while the status is unclear—each action can create new records that make the original duplicate harder to trace. The first task is classification, not action.
Classify each line as pending, authorized, or settled. A single transaction can briefly show as multiple records before settlement; only the final settled line confirms the actual charge count. Then inspect the provider subscription page, Apple ID subscriptions, and Google Play subscriptions separately—different channels manage their own billing and do not cross-reference each other.
If genuinely overlapping active subscriptions exist, the decision is which to keep and which to cancel. Match each order ID to its date, amount, currency, account, and channel. Keep the plan you want and cancel the others in their original channels: web orders through the provider, Apple orders through Apple, Google Play orders through Google Play. A product app cannot necessarily manage a store order.
For a refund or billing review, provide both order IDs, dates, amounts, channels, and redacted statements. Describe a genuine duplicate purchase accurately; calling a personal repeat purchase 'fraud' can delay or invalidate the request. Save cancellation confirmations and check the next statement. The limitation: some apparent duplicates are a single authorization in a multi-day settlement window, and disputing prematurely can freeze the legitimate order.