My take is that iDine opts-in for a database match with VISA/MC, supplying them with the CC #'s of registered users. When a match pops up, iDine gets a message from VISA. I would surmise that the CC# would drive the inquiry, with the matched restaurant being secondary. A possible ancilliary benefit for iDine would be, if restaurant info resides with them only, it might be possible to mine the data and use it for soliciting prospective restaurants to join the program, based on the membership's dining patterns.

Next time we have a VISA class, I'll ask our processor rep how they handle it. You've got me curious now.

FWIW, just handing the server your CC flies a lot of privacy out the window. I would worry more about that than what's going on between iDine and VISA processors, who operate in a pretty tightly controlled environment. Most processors have limited scope to share personal information for the purposes of marketing and quality assurance so, whether one iDine's or UAL mall shop's, our info is out there, IMO.

Then there's we folks who grant credit. That's a whole other can of worms....

Pat