I've just begun integration the notification api with my site. Based
on some other questions, it seems like there notification services had
some problems the past couple of days, so I don't know if I'm not
getting them because of those problems or because of something else. I
was wondering if anyone could tell if I'm doing something wrong
(noting that it could be my code).
1) I've set the Sandbox "API callback URL" to my URL using the XML
method (which I've tested with files). This url uses port 80 and is
not SSL-eneblaed (i.e. http).
2) Under order processing, I selected "Automatically authorize and
charge the buyer's credit card".
3) After setting up my site and confirming that it worked as I
expected it to, I placed a few test orders and waited. I didn't
receive any error notifications from my own error handlers on my site
and didn't see any evidence (in my database) that any new-order or
charge notifications made it over.
I was going to look more closely at my code, but given the downtime of
the notification API recently, I have a couple of questions.
1) Are non-SSL URLs, using port 80, acceptable for callback URLs?
2) Is the notification api currently running reliably?
3) Are notifications logged in "Order History" or elsewhere so that I
can confirm that an attempt was made?
4) When "Automatically authorize and charge the buyer's credit card"
is set, is a new-order notification sent first, then a charge-
notification? If so, is that orrder of operation reliable? If not,
what notifications are sent?
If you have problems to receive notifications, please have a look at your integration console. You can reach your integration console in your merchant account Tools > Integration Console
> I've just begun integration the notification api with my site. Based > on some other questions, it seems like there notification services had > some problems the past couple of days, so I don't know if I'm not > getting them because of those problems or because of something else. I > was wondering if anyone could tell if I'm doing something wrong > (noting that it could be my code).
> 1) I've set the Sandbox "API callback URL" to my URL using the XML > method (which I've tested with files). This url uses port 80 and is > not SSL-eneblaed (i.e. http). > 2) Under order processing, I selected "Automatically authorize and > charge the buyer's credit card". > 3) After setting up my site and confirming that it worked as I > expected it to, I placed a few test orders and waited. I didn't > receive any error notifications from my own error handlers on my site > and didn't see any evidence (in my database) that any new-order or > charge notifications made it over.
> I was going to look more closely at my code, but given the downtime of > the notification API recently, I have a couple of questions.
> 1) Are non-SSL URLs, using port 80, acceptable for callback URLs? > 2) Is the notification api currently running reliably? > 3) Are notifications logged in "Order History" or elsewhere so that I > can confirm that an attempt was made? > 4) When "Automatically authorize and charge the buyer's credit card" > is set, is a new-order notification sent first, then a charge- > notification? If so, is that orrder of operation reliable? If not, > what notifications are sent?
I am using Google Checkout API (GCheckout.dll) in ASP.Net. My
application is hosted in non ssl environment currently i'm using sand
box b'coz i'm still testing my shopping cart but issue is i'm not
recieving any notification. i checked my console as well but could not
find any error.
could you please help me for the same?
thanks
dipak
On May 14, 5:13 pm, Ignacio <nacho.diro...@gmail.com> wrote:
> If you have problems to receive notifications, please have a look at your
> integration console. You can reach your integration console in your merchant
> account Tools > Integration Console
> > I've just begun integration the notification api with my site. Based
> > on some other questions, it seems like there notification services had
> > some problems the past couple of days, so I don't know if I'm not
> > getting them because of those problems or because of something else. I
> > was wondering if anyone could tell if I'm doing something wrong
> > (noting that it could be my code).
> > 1) I've set the Sandbox "API callback URL" to my URL using the XML
> > method (which I've tested with files). This url uses port 80 and is
> > not SSL-eneblaed (i.e. http).
> > 2) Under order processing, I selected "Automatically authorize and
> > charge the buyer's credit card".
> > 3) After setting up my site and confirming that it worked as I
> > expected it to, I placed a few test orders and waited. I didn't
> > receive any error notifications from my own error handlers on my site
> > and didn't see any evidence (in my database) that any new-order or
> > charge notifications made it over.
> > I was going to look more closely at my code, but given the downtime of
> > the notification API recently, I have a couple of questions.
> > 1) Are non-SSL URLs, using port 80, acceptable for callback URLs?
> > 2) Is the notification api currently running reliably?
> > 3) Are notifications logged in "Order History" or elsewhere so that I
> > can confirm that an attempt was made?
> > 4) When "Automatically authorize and charge the buyer's credit card"
> > is set, is a new-order notification sent first, then a charge-
> > notification? If so, is that orrder of operation reliable? If not,
> > what notifications are sent?
> > I appreciate any insight. Thanks.- Hide quoted text -
On May 15, 4:44 pm, Dary <taxwaxxaw...@gmail.com> wrote:
> They had a problem earlier this week and it looks to me like they are
> down again.
Yep. I think they're down, I've spent that last few hours trying to
work out why I wasn't getting any notifications through whatsoever in
my sandbox account.
1. Checked Tools > Integration Console and found no errors
2. Used the tool here: http://demo.globant.com/~brovagnati/tools/responsehandler_test.php and got no response (and it took ages)
3. Navigated to the response script locally myself to check the code
in there is working (and it is)
> On May 15, 4:44 pm, Dary <taxwaxxaw...@gmail.com> wrote:
> > They had a problem earlier this week and it looks to me like they are
> > down again.
> Yep. I think they're down, I've spent that last few hours trying to
> work out why I wasn't getting any notifications through whatsoever in
> my sandbox account.
> 1. Checked Tools > Integration Console and found no errors
> 2. Used the tool here:http://demo.globant.com/~brovagnati/tools/responsehandler_test.php > and got no response (and it took ages)
> 3. Navigated to the response script locally myself to check the code
> in there is working (and it is)
> so it must be the sandbox notifications are down.
