Anyone ingrated google checkout with standard ASP before?

[Superficial]

hi there,

I'm not a programmer but the issue is fairly simple.

Our site currently cannot register a sale (and therefore create a pending order) unless the user is returned to the site (because we are using Google's 3rd party servers).

currently (we're in beta) the user must remember to hit a link that redirects them to the "order complete page" before our site can register a complete transaction.

As you may relaise this is not ideal - if the user were to forget to click the link they will have paid and we will have no record of it.

Can anyone offer any help?

thanks.

 

[elkdanger]

hi there,

I'm not a programmer but the issue is fairly simple.

Our site currently cannot register a sale (and therefore create a pending order) unless the user is returned to the site (because we are using Google's 3rd party servers).

currently (we're in beta) the user must remember to hit a link that redirects them to the "order complete page" before our site can register a complete transaction.

As you may relaise this is not ideal - if the user were to forget to click the link they will have paid and we will have no record of it.

Can anyone offer any help?

thanks.

If Google Checkout is anything like the major payment providers (like HSBC, Barclays and even Paypal), they should be able to POST to a location of your choice with details of the order at the time of order confirmation. This post-back is automatically instigated by the payment provider, and *should* be guaranteed to happen if a payment was successful. This is the time you would record confirmation of the order, since it doesn't rely on the user pressing the 'Return to merchant' button.

Without knowing more about the API I can't elaborate, but I would imagine this scenario is the case.

What we normally do with orders is, create an initial database entry at the time right before the user gets directed to the payment provider, recording the users details, inventory, etc and set some sort of order status flag to 0. Then, when the payment provider gets in touch with the site via the auto-postback, we alter the status value accordingly depending on the result of the transaction. At this point, if successful, we send out any confirmation emails, etc.

 

[Superficial]

If Google Checkout is anything like the major payment providers (like HSBC, Barclays and even Paypal), they should be able to POST to a location of your choice with details of the order at the time of order confirmation. This post-back is automatically instigated by the payment provider, and *should* be guaranteed to happen if a payment was successful. This is the time you would record confirmation of the order, since it doesn't rely on the user pressing the 'Return to merchant' button.

Without knowing more about the API I can't elaborate, but I would imagine this scenario is the case.

What we normally do with orders is, create an initial database entry at the time right before the user gets directed to the payment provider, recording the users details, inventory, etc and set some sort of order status flag to 0. Then, when the payment provider gets in touch with the site via the auto-postback, we alter the status value accordingly depending on the result of the transaction. At this point, if successful, we send out any confirmation emails, etc.

Thanks for the reply

Yeah google have this facility here is there response:

-----
Google
Checkout checkout can send your server notifications to synchronize your
servers order status. These notifications can contain user information,
items ordered, order status, financial status and more. To receive them
you will need to implement an API callback handler to parse XML
notifications and update your database. For more information and sample
code, please take a look at our Developer's Guide located at:

http://code.google.com/apis/checkout/developer/Google_Checkout_XML_API_Notification_API.html
------

so you're quite right. Problem is that I'm not a programmer and our programmer is unable to work out how to use the API callack handler - which leaves me up **** creak lol.

thats a good idea though - essentially recording all the necessary details in a temporary table and moving them into orders once receiving the info.

all i need now is a programmer that can do it.

thanks for your tiem mate - much appreciated

regards,