@RobD3 wrote:
Payments (including the one referenced in this discussion) were scheduled against an account funded by a "large'ish" deposit. The deposit was a regularly deposited check (not a payroll check) that had been recieved at least half a dozen times before and not held as security for any reason. Inexplicably, the one that caused this mess was held for 2 business days. I had no knowledge of this. This caused a payment to an AMEX Hilton card to be returned unpaid. I have not needed OD protection for many years so there was nothing in place to guarantee the payment. I was notified by automatically of the issue, so I immediately moved $$'s, to no avail. A day later, the hold was released and the damage had been done. There was nothing I could do except wait for things to play out. Hence, this discussion. Needless to say, I will never be without some form of payment protection in the future. The payment was reprocessed without issue.
I'm not trying to be petty here, but in your original post, you mentioned this returned payment wasn't your fault. After the explanation above, just for the sake of posterity, it should be noted that this may indeed fall on your side of the fault. This wasn't an AMEX issue by any means. One should only schedule payments out when funds are verified available. This is, indeed, the truest of the true returned payments - a payment was made against an account that had insufficient funds.
