Consumer Rights Wiki

Forced retention of payment methods: Difference between revisions

← Older editNewer edit →
VisualWikitext
This article reads very well, however there are two issues with sourcing: 1. the number of claims made without citation, and 2. the images appear to be original research or . Such images are fine to include to support a cited source (e.g. 'the privacy policy says xyz, here's an image' followed by a link to an archive of the pricacy policy, or 'here's what x signup screen looks like') but should not be used as primary, uncited, evidence to support a specific allegation e.g. captivate.fm here
Beanie Bo (talk | contribs)
confirmed, Administrators
907 edits
added amazon/audible lawsuit. fixed some wording
Line 1: Line 1:
{{Incomplete}}
{{Incomplete}}


'''Forced retention of payment methods''' is a common design pattern in which online platforms and payment processors store user payment credentials without offering a clear or accessible way to revoke them. In many cases, cards or payment authorizations remain attached to an account unless a new method is added, or until the entire account is deleted. This design restricts users’ control over their own financial data and can result in unwanted recurring charges.
'''Forced retention of payment methods''' is when online platforms and payment processors store user payment credentials, often without a clear or easily accessible way to revoke them. In many cases, cards or payment authorizations remain attached to an account unless a new method is added or until the account itself is deleted. This design restricts users’ control over their financial data and could potentially result in unwanted recurring charges.


The issue disproportionately affects individuals with limited financial resources, as well as non-profit or low-budget users, who may lack the legal or technical knowledge required to challenge such systems. This article documents how the practice works, outlines its implications for consumer rights, and presents case studies across multiple services.
The issue disproportionately affects individuals with limited financial resources, as well as non-profit or low-budget users, who may lack the legal or technical knowledge required to challenge such systems.


==How it works==
==How it works==
In most cases, forced retention of payment methods is implemented through user interfaces that do not allow stored payment data to be removed unless a replacement method is added. Some platforms go further, requiring the deletion of the entire account in order to erase billing credentials.
In most cases, forced retention of payment methods is implemented through user interfaces that do not allow stored payment data to be removed unless a replacement method is added. Some platforms go further, requiring the deletion of the entire account in order to erase billing credentials.


Another variant involves payment intermediaries (like PayPal), where billing agreements are created automatically during a one-time purchase, without an explicit consent process. These agreements remain active unless manually revoked, which is often hidden behind asynchronous interfaces or inaccessible menus.
Another variant involves payment intermediaries (like [[PayPal]]), where billing agreements are created automatically during a one-time purchase without an explicit consent process{{Citation needed}}. These agreements remain active unless manually revoked, which is often hidden behind asynchronous interfaces or inaccessible menus.


Overall, these systems are designed in a way that favors continued billing and makes revocation difficult, non-obvious, or impossible without contacting support.
Overall, these systems are designed in a way that favors continued billing and makes revocation difficult, non-obvious, or impossible without contacting support.
Line 15: Line 15:
Forced retention of payment methods causes long-term risks for consumers by removing their ability to control how and when they are billed. When a person cannot revoke stored card data or stop an ongoing billing authorization, unwanted charges become more likely. This risk increases when services use automatic renewals or hide cancellation options.
Forced retention of payment methods causes long-term risks for consumers by removing their ability to control how and when they are billed. When a person cannot revoke stored card data or stop an ongoing billing authorization, unwanted charges become more likely. This risk increases when services use automatic renewals or hide cancellation options.


Many users are not offered a simple way to delete a card or cancel a billing agreement. This situation puts the burden entirely on the user and punishes those with limited time, resources, or legal knowledge. Some are even forced to delete their entire account or give up access to services just to stop the billing.
Many users are not offered a simple way to delete a card or cancel a billing agreement. This situation puts the burden on the user while disadvantaging those with limited time, resources, or legal knowledge. Some may even feel compelled to delete their account or give up access to services just to stop the billing.


These obstacles are often made worse by unclear interfaces, delayed menus, or wording that makes it difficult to understand how to stop payments.
These obstacles are often made worse by unclear interfaces, delayed menus, or wording that makes it difficult to understand how to stop payments.
Line 26: Line 26:
This action resulted in the irreversible loss of all stored content, as well as any communication history with support. The user described this as a last resort to stop further charges, since no clear cancellation path existed within the account settings.
This action resulted in the irreversible loss of all stored content, as well as any communication history with support. The user described this as a last resort to stop further charges, since no clear cancellation path existed within the account settings.
[[File:Capture d'écran 2025-06-06 151815.png|thumb|948x948px|Captivate billing history]]
[[File:Capture d'écran 2025-06-06 151815.png|thumb|948x948px|Captivate billing history]]




Line 100: Line 98:




 
=== Amazon ===
 
A class-action lawsuit is currently pending against Amazon for enrolling customers into Audible and charging them the $14.95 monthly subscription fee without notice or consent. Grace Sherk, the plaintiff, claims this act by Amazon was only possible due to the company holding customers' payment and billing information by default<ref>{{Cite web |date=2025-04-23 |title=Amazon Audible faces class action over unauthorized subscriptions |url=https://topclassactions.com/lawsuit-settlements/lawsuit-news/amazon-audible-faces-class-action-over-unauthorized-subscriptions/ |website=Top Class Actions}}</ref>. When combined with Audible's failure to enact [[click-to-cancel]], customers' were locked into monthly payments until they could resolve the issue with customer service.
 


==Pattern of friction and discouragement==
==Pattern of friction and discouragement==
Line 119: Line 116:


===Article 6 and 17 of the General Data Protection Regulation (GDPR)===
===Article 6 and 17 of the General Data Protection Regulation (GDPR)===
These articles define the lawfulness of processing and the right to erasure. If a user requests the removal of stored financial data and the platform refuses unless a new payment method is provided, this may violate both articles.
In the UK and EU, these articles define the lawfulness of processing and the right to erasure. If a user requests the removal of stored financial data and the platform refuses unless a new payment method is provided, this may violate both articles.


===Article 12 of the GDPR===
===Article 12 of the GDPR===
Retrieved from "https://consumerrights.wiki/w/Forced_retention_of_payment_methods"