Conference 7.286::dcu

    re: .0
    
    This is a network fault, not a DCU fault.  It has happened to me as
    well, using an EXPRESS-24 card at a machine on the CIRRUS network. 
    Apprently, the machine discovers it cannot dispense cash for some
    reason AFTER it has entered a debit message on the network (overly
    simplified explanation).  The DCU is merely responding to the debit
    message, so it's not their fault.  When the $ is restored to your
    account, you should assure that you are creditied any back interest
    due.
    As for checking your recipts, I would vigorously agree, whenever this
    sort of thing happens to you, you should verify that your account has
    not been incorrectly debitted by the network.
    
    The risks of living in the age of electronic banking...

I suppose it would be too hard for the machine to send a credit message
to recover from being unable to deliver the money specified in the
previous debit message?  Or did the people who specified the system
care more about accidental credits than they did about accidental debits?

If this were the responsibility of the bank, one could change banks to
protest.  Since it is the network, users who are affected cannot find
those responsible.  So we have to make the banks care about it -- and
the only way to do that is to make it clear that this kind of behavior
on the part of the network is NOT ACCEPTABLE, and simply restoring the 
money (plus interest) when it happens doesn't go far enough.  The DCU
should start yelling at those who own the network to fix the stupid thing.
We and the DCU ought to be allies on this -- they shouldn't find this
behavior on the part of the network any more reasonable than we do.

	Enjoy,
	Larry

    Whoa, flame off!
    
    I doubt that the DCU finds this sort of network glitch any more
    palatable than you or I, since they have to invest the time and effort
    to track down the problem, credit your account, recalculate the
    interest, etc.  BayBank was not real thrilled about the problem,
    either, when it happened to me.  Apparently, the various networks are
    rather independent and autonomous, and have a rather cavalier attitude
    about such problems, and I doubt that DCU is big enough to strike fear
    into their hearts, especially if BayBank was not!
    
    I sense that you're mad as hell and want to blame someone, but a little
    sanity here, please.  Have you called Mary Madden and asked if there's
    anything DCU can do to prevent this sort of thing?

Sorry, I didn't mean .2 as a flame against the DCU, but rather against
the network operators.  To respond to the tag line of .1 -- yes, this is
one of the risks of electronic banking.  But problems like these are *not*
inherent in the technology.  They happen because somebody doesn't care
about making a system that works.  Can they be made to care?  If not
by banks (the DCU among many others), then by whom?

And consider this.  Banks are very careful to insure that the money adds
up properly, and I've got to believe that they log all of the transactions
on the money machines.  So somebody probably found out there was extra 
money but apparently just kept it.  That's why I'm reacting so strongly.  

	Larry

    
    Ok, well I must get in on this one.  I believe it was the same weekend
    as .0, and I was at Shaw's in Milford getting some stuff for dinner.  
    I went up to the ATM with a full load of groceries, and SLAM! the machine 
    wouldn't give me any money.  I tried 3 times before giving up!
    
    I then figured, ok, well, I will just run down to the Co-op in Amherst
    and grab some money.  No luck.
    
    The only thing I could figure out was that these wonderful machines
    tried to reach my balance at DCU and couldn't so they said 'forget it,
    no money for you!'
    
    Things were so much easier when the ATM's couldn't see my account!
    
    Oh well, life goes on...
    
    Steven