I hadn't used my AWS account in nearly eight years—the last time was during my master's program. I suddenly noticed a $1 charge from AWS and worried that someone might be testing my card before making a larger unauthorized purchase. I disputed the charge, so my card issuer canceled the card and sent me a replacement. Later, AWS emailed me saying its billing-information verification had failed. Why does AWS make a temporary charge without warning customers first? Now I have to wait for the replacement card and update my payment details everywhere.
3 Answers
The problem is that a small test charge followed by another transaction can look exactly like a fraud pattern, especially when the account hasn’t been used in years. Your card issuer may have blocked it because of that sequence, so the concern was understandable even if the charge was legitimate.
That $1 transaction is usually a temporary authorization used to verify that the card is valid. It’s a common practice among merchants, and it should normally disappear or be reversed rather than become a permanent charge.
This happened to me with an old, unused cloud account too. In my case, the unexpected verification charge reminded me that the account was still active. I ended up closing the account because keeping forgotten payment details stored there felt like an unnecessary security risk.
That’s essentially what I had to do as well. I reported the card, waited for the replacement, and then closed the old account.