Google Checkout Call Back Issues

[Darren B]

I know it does seem strange, you have had some bad luck with Google Checkout.

LOL the biggest problem was actually the simpliest to fix, it was consolidating cart discounts caused a problem with the xml sent. Untick and it works

Cheers
Darren

[Benjamin Dyer]

I know it does seem strange, you have had some bad luck with Google Checkout.

[Darren B]

No probs Ben, when i get a chance ill contact support. Its not effecting orders and the initial call back so no biggy here. Just wondered why i seem to be the only one seeing it.

thanks
Darren

[Benjamin Dyer]

Morning Darren,

This is fairly curious. I did some checking for you and it hasn't been reported before. It would need some investigation by the support team I am afraid.

[Darren B]

Im getting more an more emails from google as the orders increase by this method, does nayone else use GC or have these issues

this is what google is trying to tell Actinic (i have removed some details and replaced this with * to protect my customers info

<?xml version="1.0" encoding="UTF-8"?>
<risk-information-notification xmlns="http://checkout.google.com/schema/2" serial-number="703054721300045-00005-5">
  <timestamp>2010-07-13T17:34:29.753Z</timestamp>
  <risk-information>
    <ip-address>85.165.245.219</ip-address>
    <billing-address>
      <email>Marius-bbgnf0nklm6@checkout.google.com</email>
      <company-name></company-name>
      <contact-name>M****s V****n</contact-name>
      <phone>9********0/phone>
      <fax></fax>
      <address1>J******n 5</address1>
      <address2></address2>
      <country-code>NO</country-code>
      <city>Larkollen</city>
      <region></region>
      <postal-code>1560</postal-code>
    </billing-address>
    <avs-response>U</avs-response>
    <cvn-response>M</cvn-response>
    <eligible-for-protection>true</eligible-for-protection>
    <partial-cc-number>6332</partial-cc-number>
    <buyer-account-age>0</buyer-account-age>
  </risk-information>
  <google-order-number>703054721300045</google-order-number>
</risk-information-notification>

this is another failure which implies and update to the order status

<?xml version="1.0" encoding="UTF-8"?>
<order-state-change-notification xmlns="http://checkout.google.com/schema/2" serial-number="129105003417505-00006-1">
  <new-fulfillment-order-state>PROCESSING</new-fulfillment-order-state>
  <new-financial-order-state>CHARGEABLE</new-financial-order-state>
  <previous-fulfillment-order-state>NEW</previous-fulfillment-order-state>
  <previous-financial-order-state>CHARGEABLE</previous-financial-order-state>
  <timestamp>2010-06-23T20:49:59.694Z</timestamp>
  <google-order-number>129105003417505</google-order-number>
</order-state-change-notification>

i cant believe im the only one having issues, or do i have something setup wrongly?

If no one here has seen this before then i guess its a job for support although i really dont have time just at the moment

[Darren B]

thats what i have been thinking, what google does is sends the call back saying the order has been paid for but later it might come back as a possible fruad once it has been run through their systems (recently i had one cancelled by google for this and then the person placed a few days later using AP and this was flagged red aswell)

so the other call backs are for order status updates, it will also issue call backs when you have marked it as shipped - which would be good to be intergrated into actinic

Darren

[Mike Hughes]

This sounds complicated.

I always thought the callback was to indicate a successful payment. I've never heard of a PSP wanting to make extra callbacks to say "Sorry, we've changed our mind, ignore the earlier callback."

It sounds like something you'll need to get support to look into.

Mike

[Darren B]

Im getting a number of GC orders these days but im also getting alot of errors from GC with the call back.

The initial call back works and the order downloads properly, but google sometimes makes another call back when the order is declined or wishes to update the original e.t.c but this gives errors as for some reason only the first call back works after that it would appear google is getting a 404 error.

Im not sure were the issue is, is it Actinic or Google. I dont understand the full sequence of the call back after the inital payment one, but google cant seem to make anymore call backs

Any help would be apreciated
Darren