call back file changed in settings but google still sending to old one

I realized that and threw in a page to suck up the queued
API callbacks.
I agree with your view on when the change should occur. 
Just caught me
by surprise and it seems to be a FIFO queue so cart info
queued up
behind it never gets out till it clears.

tony 

-----Original Message-----
From: google-checkout-api-integrationgooglegroups.com
[mailto:google-checkout-api-integrationgooglegroups.com] On Behalf Of
GoogleCheckoutDevPro
Sent: Monday, December 11, 2006 3:52 PM
To: Google Checkout Developers Forum - API Integration
Basics
Subject: [google-checkout-api-integration] Re: call back
file changed in
settings but google still sending to old one


Hi,

The API callback URL is set to each order at the time the
order is
placed, so changing it after the order is placed will not
prevent Google
from hitting your old API callback URL.

I think it would seem like the correct callback API file is
being
invoked because new orders placed after the change will be
correctly
associated with the new API callback URL.

Please reply back if this doesn't help.


Thanks,
Jacob






--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---