Service Codes>When to Send it to the customer

[Guest]

HI there...

Please Help????...thanks....

 

I need to sell (resell) a service and the customer will buy PIN numbers from me.

The bank will process each cc sale and send me a secure code/notification that they have the money

At the same instant, the bank will copy the same secure code/notification to my wholesaler

...who reacts to the secure message from a known secure DNS at the bank and sends me a PIN number to give to my customer.

I must catch the two messages in osC, and

I must make an email to the customer in osC (and an SMS, simultaneously, using the lovely "SMS Me" - Order Updates by SMS contribution) and send them both to the customer...

...who will be waiting to use the PIN he/she just bought in my osC shop

 

My=Problem....please....:

How do I

...1) "capture" and link the incoming secure messages in osC from

...........the bank

...........and my wholesaler

...2) to make my osC shop >>>generate the basic email<<< to the customer with their PIN

 

If I can do that, I think I can make the SMS Me contribution react in a similar way...

 

Many many thanks for all your brainstorming!!!!!!!!!...

Best wishes,

Gratefully...

Charles

:rolleyes:

[♥Vger]

That's serious custom coding. You'll probably have to employ someone to write it for you.

 

Vger

[Guest]

Uh oh...

'Down there' is where we crash this plane, eh?...This will be really messy...Bad News...Bad Morning...

[i think I have the cheap, effective and SAFE answer, though---bear with me please]

 

OK...I cannot be the only one in the global Open Source community who wants to sell PIN numbers for Services!?!?!?!....We are in the 21st Century, right? (just joking...brutally TIRED...since horribly early morning!)

What about another way to fly this heap without ripping off the wings?

'That' processing model is not cast in stone...althought admittedly 'very nice,' and a 'someday wouldn't it be nice'??? The trick is to find things that have been done before and integrate them comfortably (no 'news' there).

 

How about a trick where only one (1) notice is 'eaten' by the shop and THAT provokes the email?

Right now it seems my simple osC shop under construction works on the old cc model where I have to decide if the cc is good, somehow, and 'risk it' by sending product out the door...and pray for 6 months that the card was not stolen. Let's call it "Click&Pray"

 

There is probably a function ~inside osC~ to make the shop wait for an 'internal authorization' before sending that email to the customer thanking them for buying the widget...but where???? Think of it just as ~data*it*needs*from*inside*itself~ to do the 'next step.' Something in the osC shop makes the email get written according to a user defined format and then sends it, picking-up customer info from its database. There must be a function 'inside' that separates "accepting an order" from the later step of telling the stock room man to "ship it." The game here will be to 'delay' the email until the PIN number comes and "drops into the little hole on the form." It cannot send an incomplete email, so it must wait for the computer to give the PIN to the email form maker. What I will describe here is probably OK within today's nice tolerant operational parameters of the osC shop patiently "waiting a little bit" for what it thinks is a "busy computer". Let's make the server's big buffer do some work, here, too! osC doesn't have to do everything! The total transaction time is so fast on modern backbones, that it will not matter.

 

How do people use the osC shop now to sell PIN's? "Click & Pray"? I don't believe it! (I'm only a newbie at this system.) Why? I (and everybody else selling PINs) need to work on the functional basis that the bank has authorized each sale & has gotten the money. I get a notice in seconds from my lovely European bank that it has the money!!! I cannot just give out PIN codes to jokers (think of handing out money!) without somehow double checking that the bank has successfully finished collecting their money. [i already had one hacker that I had to block out!]

 

OK~here it is... New Model>>>Only 'One Notice Makes the World Go Round': a real planetary 'service'!

 

.....Here is my osC shop (makes sale & goes to sleep for a few short seconds...waiting for the PIN code before sending the completed 'thank you email'...)....thinking...'busy computer...'...

........(here is my bank)

...........Bank OKs sale&collects the money [=seconds] and sends instant notice to my supplier [and me] for free [milliseconds]

.............My supplier's transaction server 'reacts' to the bank's OK from a known secure bank DNS, and sends the PIN code only to my SSL secure address (a DNS web 'window'/on a sub domain set-up just for him.)

..............On my provider's fast international backbone, I have my wholesaler's message with the PIN code in milliseconds.

................My osC shop sees the message, eats the PIN code and puts it in ready to send email (&/or SMS)

..................Customer Smiles :D

 

What is really happening inside this?

1. My osC shop knows all the customer transaction details except the cc data (forbidden to the merchant in Europe under 3D-Secure+Verified by VISA+MasterCard SecureCode 'combined' new bank rules)

2. My osC shop waits for the PIN to come, inserts it and sends it...

..... All I have to do is make a table linking my internal transaction ID (in osC) to the Bank's transaction ID (in its secure OK notice), and then the incoming PIN notice from my supplier goes to the right email waiting in the 'THANK YOUs to Send' queue...(ditto to the SMS queue in osC)

3. This is also safe for the merchant because only my/their osC database has the full customer destination data, so nobody can deliver the PIN without the merchant's database linking and sending the PIN.

 

>>>It's a 'tripple blind' control system.<<<

Nobody can make the sale without all the players coordinating and the merchant is the final gatekeeper...which is right! Although admittedly largely a passive system, effective and it saves processing steps without inducing uncertainty.

 

To Sell PIN based Services from a wholeseller.

This is a typical model that more and more osC merchants will _need_ to use in one form or another:

 

What do you think, please>>>you are a real expert at this and zillions of osC people want/will want to SAFELY sell PIN based services now and in the future! You and all of us want to know that the money is safe before we send the precious little PIN...

***********************************************************

PIN-BASED PRODUCT SALES ARE PART OF THE OSCOMMERCE FUTURE:

......MAYBE THE BIGGEST PART, EVENTUALLY!!!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Many Thanks for Brainstorming with us all Vger! :thumbsup:

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Have a Creative Day!!!

Charles

:rolleyes:

 

p.s., I have a young programmer from the faculty helping me, but we need guidance about what osC really does 'inside'...please...