Article View: misc.consumers
Article #9074Re: How Does This Happen?
From: spamtrap1888
Date: Thu, 07 Aug 2008 20:51
Date: Thu, 07 Aug 2008 20:51
37 lines
3343 bytes
3343 bytes
On Aug 7, 12:43 pm, "SpammersDie" <x...@xx.xx> wrote: > <spamtrap1...@gmail.com> wrote in message > > news:c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com... > > > On Aug 5, 8:00 am, Scott in SoCal <scottenazt...@yahoo.com> wrote: > > >> I find that hard to believe the way you keep playing the victim card > >> on behalf of these incompetent money managers. > > > There is a fine banking tradition of refusing to honor withdrawals > > after a sufficient lapse of time -- "stale-dated" checks. All my > > dividend checks have a date on them beyond which they will no longer > > be honored. After that, the payee must go groveling back to the maker > > to get a replacement check. If a giant corporation is not required to > > keep sufficient funds in its checking account for eternity, neither > > should Joe Consumer be. > > > Banks should have treated these withdrawals as if they were stale- > > dated checks. > > Where did it say in the article that the banks honored aged EFTs? > > It sounds more like the vendor spit out the merchandise and waited months to > initiate the EFT. The vendor does not initiate the EFT, the customer does when he sticks his debit card in the vendor's machine. Inserting the debit card is the same as writing the check and mailing it. If vendors could initiate EFTs they could suck your balance dry at any time. The vendor's lackadaisicalness is not the customer's responsibility. Per Scott, "[the CTA's] system queued up a few months' worth of customers' charges, and then sent them through all at once." That would be like me accumulating two years' worth of dividend checks, then cashing them all at once. The bank would kick the stale date checks back to me, not process them for payment.
Technical Details
Message-ID:
<dc64fddb-49b4-4796-914a-045b75378e1a@z6g2000pre.googlegroups.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!postnews.google.com!z6g2000pre.googlegroups.com!not-for-mailReferences:
<ko35949b1nba66qgk3hjg024brcr26vdgu@4ax.com> <g74vjr$3hl$2@jik3.kamens.brookline.ma.us> <gcqc94lo4l0n39p5alvlukv3rem2cbs223@4ax.com> <g77c1l$qll$1@jik3.kamens.brookline.ma.us> <3kpg94tbalh9lmoe6avfa1i9jcc0mau8j4@4ax.com> <c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com> <tfImk.150188$102.3147@bgtnsc05-news.ops.worldnet.att.net>Show Full Headers
Complete Article Headers
X-Google-Thread: 107518,d777ae74711f9ca1 X-Google-Thread: 10e835,d777ae74711f9ca1 X-Google-Attributes: gid107518,gid10e835,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!postnews.google.com!z6g2000pre.googlegroups.com!not-for-mail From: spamtrap1888@gmail.com Newsgroups: misc.consumers,chi.general Subject: Re: How Does This Happen? Date: Thu, 7 Aug 2008 13:51:08 -0700 (PDT) Organization: http://groups.google.com Lines: 37 Message-ID: <dc64fddb-49b4-4796-914a-045b75378e1a@z6g2000pre.googlegroups.com> References: <ko35949b1nba66qgk3hjg024brcr26vdgu@4ax.com> <g74vjr$3hl$2@jik3.kamens.brookline.ma.us> <gcqc94lo4l0n39p5alvlukv3rem2cbs223@4ax.com> <g77c1l$qll$1@jik3.kamens.brookline.ma.us> <3kpg94tbalh9lmoe6avfa1i9jcc0mau8j4@4ax.com> <c1f774e3-94de-4c23-9924-32b208533d23@j1g2000prb.googlegroups.com> <tfImk.150188$102.3147@bgtnsc05-news.ops.worldnet.att.net> NNTP-Posting-Host: 76.191.199.85 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1218142270 29410 127.0.0.1 (7 Aug 2008 20:51:10 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 7 Aug 2008 20:51:10 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: z6g2000pre.googlegroups.com; posting-host=76.191.199.85; posting-account=IKrCMwoAAAAvbBFDI2BDgowVKvaBbkTn User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16,gzip(gfe),gzip(gfe)