Forced retention of payment methods: Difference between revisions
Finished writing |
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 |
||
| Line 1: | Line 1: | ||
{{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 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. | ||