As a coinbase customer and someone who manages a team and large complex distributed systems, this is an oversight I would not expect from an industry leader and makes me nervous to continue doing transactions with coinbase.
How can we be made comfortable that this won't happen again? $50 isn't the root cause fix and could have cost the OP $15,000 due to the delay. What if those BTC was going to be used to make a purchase? He is left holding the bag, leaving a sour taste.
I've had to deal with micropayment reconciliation for a minor handset mfgr (multiple currencies, payment processors, timezones, products, on and on). Sometimes the credit card processor up and changes the API without notice, and a whole slew of payments have to rerun. This is where fields in the local reconcilation db start to creep in and all sort of weird flags get made. What the heck is flag F? (IOTW, document the heck out of the db schema AND have lots^10 unit tests.)
Complaining about the complexities does not instill faith that you have a solid grasp on your product. Tell me you dont work at coinbase, please.
1. Let's suppose I employ an old gambit: process a large transaction through CoinBase, receive the coins and say "I never received them." I'm sure they have at least enough controls in place to avoid double-credit fraud.