This is a tough one, I researched this one all last night.
First I would recommend google checkout as the checkout and payment system.
Next use google App Engine and construct a relay server, one that will tie the orders from google checkout with an unchangeable destination server.
Ensure that if the destination server is changed, then no further orders will be processed.
Finally for the destination server side. For this you would just generate the keys and forward them to the correct gmail account.
Google has most of this infastructure in place for companies, which you can leverage yourself.
Show differencesHistory of post edits
#1kd7tck
Posted 23 September 2012 - 03:39 PM
This is a tough one, I researched this one all last night.
First I would recomend google checkout as the checkout and payment system.
Next use google App Engine and construct a relay server, one that will tie the orders from google checkout with an unchangeable destination server.
Ensure that if the destination server is changed, then no further orders will be processed.
Finally for the destination server side. For this you would just generate the keys and forward them to the correct gmail account.
Google has most of this infastructure in place for companies, which you can leverage yourself.
First I would recomend google checkout as the checkout and payment system.
Next use google App Engine and construct a relay server, one that will tie the orders from google checkout with an unchangeable destination server.
Ensure that if the destination server is changed, then no further orders will be processed.
Finally for the destination server side. For this you would just generate the keys and forward them to the correct gmail account.
Google has most of this infastructure in place for companies, which you can leverage yourself.