Sandbox Internal Error

[Thorvald ter Meer]

Hello,

I was trying to set the payment process using sandbox but I kept
stumbling upon a 500 Internal Error on https://sandbox.google.com/checkout/inapp/purchase_options
Popup with order detail is displayed but then come the "Uh oh. There
was a problem." a few second after without any Error information.
This happen before selecting a payment but after a user logged. If
user is already logged, the error happens straight away.

On production server, the error does not occur up to this step. (have
not tested beyond as I don't want to get charged)

[Sander Smith]

I'll add my 2 cents....

A short time ago I needed to integrate a simple in app payment system
into a webapp I'm building. I began to look into PayPal and to Google
In-App Payments and chose to integrate them both, and let my users
decide what to use.

The entire PayPal integration took about 3 hours. Works beautifully.
They have more functionality in their "phony" testing system than I
would have imagined, and allows for testing all sorts of edge test
cases.

Integrating IAP has been like pulling teeth. Could not get the sandbox
stuff to work at all. Could be me, be then ... I see others having the
same problems. The sandbox code and the live code should be the same
(well, I can't see why it should be different) so it doesn't give me a
good feeling. Doesn't seem like anyone is paying attention. Google is
a huge company, this product *should* have huge strategic value. I'm
highly confused. But then again, talk to me about my experience with
AdSense :(

Anyway, we're going with PayPal. Next week I'm going to talk with a
large group about integrating payment systems into their non-profit
apps. Missed opportunity.

When I get some free time I may look into this again, but probably not
soon.




On Feb 17, 10:41 am, Thorvald ter Meer <thorvald.term...@gmail.com>
wrote:

> Hello,
>
> I was trying to set the payment process using sandbox but I kept

> stumbling upon a 500 Internal Error onhttps://sandbox.google.com/checkout/inapp/purchase_options

[Smart]

I'll add £10
Check out my review on the google wallet docs/team/service:
http://stackoverflow.com/questions/9322519/is-it-too-soon-to-start-implementing-google-wallet

I have no teeth left! I think that if google is going to boast that it
has a shinny new payment system the must also back it up with real
live support! not this sleepy group! I have been asking every day for
the last 2 weeks on this forum getting questions half answered at best
each time, and some time with an attitude like: 'I must be stupid if I
have to ask'! Please comment on my review as the internet needs more
information on IAP, I wan't to progress with this because I believe
that it will be a good service but we must persist to get noticed.

I hope we can help each other if anything guys.

Peace.

Ben

[Ed Chavez]

That could mean an issue with the account you are using to "buy" in sandbox mode. Does the account you are using to buy in sandbox mode have a sandbox account?

[Ed Chavez]

My $0.02 (and I haven't tried the Paypal service yet):

The code is identical...yes it would be odd if different...

The only change are settings:

1. merchant identifier and secret, 
2. a Javascript setting - "sandbox_config" vs "production_config"
   

Am not a Googler so I can only offer tips that hopefully help:

• Create a sandbox account for buyer
• Create a sandbox account for seller
• Use the sandbox buyer account for sandbox testing
• Since this is a US only offering, sandbox account must be US account....

[Ed Chavez]

Read your post, and well, SO closed it. 

First, am not a PHP dev (am .Net) so I can't help you with PHP specific questions....

Read your other posts in this forum and I think your "missing piece" is JWT spec itself. The docs provided by Google are specific to In App payments. It doesn't go into JWT spec details. IMHO, your other question in this forum about "encoding" and "decoding" is related to this "missing piece" of the puzzle.

That's why they (Google) recommend you use a library - to abstract JWT spec and make it easier for you to implement. If you want to get a full(er) understanding and see all the pieces, you'll have to go through the spec (I linked it above).

As above, sorry I can't offer PHP specific help....I did provide the .Net library so if this is an option for you, feel free to give it a whirl. Note that since I worked on it last year (2011) it's based on an older JWT spec (I believe draft 5?) but shouldn't be an issue when used with In App Payments. You can see a sandbox implementation here (which is part of the zip download).

[Thorvald ter Meer]

Tested with a separate sandbox account. Only difference was that it asked me for credit card number (I used one of the test card) but afterward the same error happens. Any other attemp at buying again, resulted in a error without asking for credit card again