Starbucks double-charges a million customers

Error in credit, debit card processing happened Memorial Day weekendnc_starbucks06_09_500kmsnbc_090609.300w

Starbucks Corp. accidentally charged as many as one million customers twice for their purchases over a recent two-day period, but the company said it recognized the error and has worked to reimburse all impacted customers.

Starbucks spokeswoman Trina Smith said all U.S. and Canadian customers who used a debit or credit card on Friday, May 22, and part of Saturday, May 23, were accidentally charged twice for their purchases. The settlement processing error affected about 1 million transactions, Smith said.

The Seattle-based coffee company said it began working to resolve the problem as soon as the banks opened on Tuesday, May 26, after the Memorial Day weekend. She said customers should have seen a credit applied to their accounts by May 29.


This just hit the media outlets on Tuesday but we actually got an in-store memo about it two weeks prior– just after it happened.


1 Response to “Starbucks double-charges a million customers”

  1. 1 grasshopper June 13, 2009 at 1:38 am

    this is a great reminder to use cash… you can’t know for sure what’s leaving your bank account when you use credit

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

June 2009
« May   Jul »

Twitter Updates

Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Patsy Burnette's Facebook profile
Help end world hunger

Psalm 19:1-3

"The heavens declare the glory of God; and the firmament sheweth his handywork...There is no speech nor language, where their voice is not heard."

Blog Stats

  • 99,432 hits

%d bloggers like this: