Unable to create test sandbox seller account:

189 views
Skip to first unread message

mikeando

unread,
Jan 10, 2012, 10:19:25 PM1/10/12
to In-App Payments
Hi,
In an attempt to track down why my JWTs are not working (the "Uh Oh.
There was a problem" thread), I'm trying to create a new seller so I
can try with an alternate seller id/secret pair.

However I'm now getting a Server Error page when I try to get to the
inapp settings page:

Luckily I was logging everything I was doing as I went through it, so
you should be able to reproduce it pretty easily.

Any pointers to what I'm doing wrong in this process would be greatly
appreciated.

0. Grab a mailinator address

I'm using
<XX...@sogetthis.com>

Then note down the alternative name... so other users cant get that
email.

For me thats <M8R...@sogetthis.com>.

Note that I'm not using `mailinator.com` in case google filters that
out.

Can check the email at <http://XXXXX.mailinator.com/>

1. go to https://sandbox.google.com/checkout

This redirects to accounts.google.com/ServiceLogin?
service=sierrasandbox&continue=....

2. hit the "Sign up now" button on the right

3. Fill in the google wallet details:
email address with the alternative from 0.
pick your own password (I'm using xxxxx)

Location: Australia
Card number: Visa 4111 1111 1111 1111 any three digits any future
date (as per <http://code.google.com/apis/inapppayments/docs/
testing.html> )

Cardholder Name : GIAP Test User
Billing Address : Nowhere
City/Town : Nowhere
State : Western Australia
Postal Code : 6000
Phone number 12345678

Shipping address is my billing address selected.

Create my Account

Got redirected to www.google.com/wallet/where-it-works.html

4. go back to https://sandbox.google.com/checkout

Takes me straight in to Sandbox branded page.

5. Go back to https://sandbox.google.com/checkout/customer/gadget/inapp/developersignup.html

It now asks for a whole bunch of details.

Defaults to our alternative email - all good.
Country : USA

State Alabama
ZipCode 36310
phone 1234567890

Other details as 3.

Primary product : Computer SOftware
Monthly sales <1000

Use fake tax id 12-2345679 as suggested here:
http://code.google.com/apis/inapppayments/docs/tutorial.html

Submit generates a Server Error : 500

6. Trying to go to https://sandbox.google.com/checkout/customer/gadget/inapp/settings.html
generates a server error too!

7. https://sandbox.google.com/checkout/ is OK though!

8. Try the sandbox inapp settings.html again in a different browser:

Woo hoo that generates a server error 500 too:


9. Go to mailinator and check the email : theres an account-
verificati...@google.com email.
10. Click on link in the email
11. Account verified!

12. Retry inapp settings again in original browser. Still get 500!

13. Open new browser (opera) clear cookies etc, and go to inapp
settings again!

Login => 500 Server error!





mikeando

unread,
Jan 13, 2012, 2:36:56 AM1/13/12
to In-App Payments
I tried this with USA details rather than Australian ones.
Made no difference. (Except I had to use a real phone number for
it ..
maybe the phone number checking is more robust on the USA accounts
than the Australian ones.)

A second developer of ours has been through the process too, and he
also received a server 500 error.

Mike A.

On Jan 11, 11:19 am, mikeando <drmikea...@gmail.com> wrote:
> Hi,
> In an attempt to track down why my JWTs are not working (the "Uh Oh.
> There was a problem" thread), I'm trying to create a new seller so I
> can try with an alternate seller id/secret pair.
>
> However I'm now getting a Server Error page when I try to get to the
> inapp settings page:
>
> Luckily I was logging everything I was doing as I went through it, so
> you should be able to reproduce it pretty easily.
>
> Any pointers to what I'm doing wrong in this process would be greatly
> appreciated.
>
> 0. Grab a mailinator address
>
>   I'm using
>   <XX...@sogetthis.com>
>
>   Then note down the alternative name... so other users cant get that
> email.
>
>   For me thats <M8R-...@sogetthis.com>.
>
>   Note that I'm not using `mailinator.com` in case google filters that
> out.
>
>   Can check the email at <http://XXXXX.mailinator.com/>
>
> 1. go tohttps://sandbox.google.com/checkout
>
>     This redirects to accounts.google.com/ServiceLogin?
> service=sierrasandbox&continue=....
>
> 2. hit the "Sign up now" button on the right
>
> 3. Fill in the google wallet details:
>    email address with the alternative from 0.
>    pick your own password (I'm using xxxxx)
>
>    Location: Australia
>    Card number: Visa    4111 1111 1111 1111     any three digits        any future
> date (as per <http://code.google.com/apis/inapppayments/docs/
> testing.html> )
>
>    Cardholder Name : GIAP Test User
>    Billing Address : Nowhere
>    City/Town : Nowhere
>    State : Western Australia
>    Postal Code : 6000
>    Phone number 12345678
>
>    Shipping address is my billing address selected.
>
>    Create my Account
>
> Got redirected towww.google.com/wallet/where-it-works.html
>
> 4. go back to  https://sandbox.google.com/checkout
>
>    Takes me straight in to Sandbox branded page.
>
> 5. Go back tohttps://sandbox.google.com/checkout/customer/gadget/inapp/developersi...
>
>    It now asks for a whole bunch of details.
>
>    Defaults to our alternative email - all good.
>    Country : USA
>
>    State Alabama
>    ZipCode 36310
>    phone 1234567890
>
>    Other details as 3.
>
>    Primary product : Computer SOftware
>    Monthly sales <1000
>
>    Use fake tax id 12-2345679 as suggested here:http://code.google.com/apis/inapppayments/docs/tutorial.html
>
>    Submit generates a Server Error : 500
>
> 6. Trying to go tohttps://sandbox.google.com/checkout/customer/gadget/inapp/settings.html
> generates a server error too!
>
> 7.https://sandbox.google.com/checkout/is OK though!
>
> 8. Try the sandbox inapp settings.html again in a different browser:
>
>    Woo hoo that generates a server error 500 too:
>
> 9. Go to mailinator and check the email : theres an account-
> verification-nore...@google.com email.

pying

unread,
Jan 13, 2012, 12:59:15 PM1/13/12
to In-App Payments
Yup we're aware of the issue and are currently working to resolve it.
> > 7.https://sandbox.google.com/checkout/isOK though!

Nick Lewis

unread,
Mar 4, 2012, 4:26:22 PM3/4/12
to In-App Payments
Has this been fixed? Right now its currently impossible to create a
sandbox account. 500 error received on each visit to
https://sandbox.google.com/checkout/customer/gadget/inapp/developersignup.html
> > >    Takes me straight in toSandboxbranded page.
>
> > > 5. Go back tohttps://sandbox.google.com/checkout/customer/gadget/inapp/developersi...
>
> > >    It now asks for a whole bunch of details.
>
> > >    Defaults to our alternative email - all good.
> > >    Country : USA
>
> > >    State Alabama
> > >    ZipCode 36310
> > >    phone 1234567890
>
> > >    Other details as 3.
>
> > >    Primary product : Computer SOftware
> > >    Monthly sales <1000
>
> > >    Use fake tax id 12-2345679 as suggested here:http://code.google.com/apis/inapppayments/docs/tutorial.html
>
> > >    Submit generates a Server Error : 500
>
> > > 6. Trying to go tohttps://sandbox.google.com/checkout/customer/gadget/inapp/settings.html
> > > generates a server error too!
>
> > > 7.https://sandbox.google.com/checkout/isOKthough!
>
> > > 8. Try thesandboxinapp settings.html again in a different browser:

mikeando

unread,
Mar 4, 2012, 7:21:47 PM3/4/12
to In-App Payments
Hi Nick,
I was never able to get this to work, and gave up. It may have been
fixed by now, but I am not sure.
In the end I had to use a real non-sandbox account set up by a
colleague using US info.
That account worked fine. (But obviously I was charged for every test
I ran)

Mike A.

On Mar 5, 5:26 am, Nick Lewis <to.nickle...@gmail.com> wrote:
> Has this been fixed? Right now its currently impossible to create a
> sandbox account. 500 error received on each visit tohttps://sandbox.google.com/checkout/customer/gadget/inapp/developersi...
>

Nick Lewis

unread,
Mar 5, 2012, 11:01:39 AM3/5/12
to In-App Payments
Thanks for the message Mike.

However, very disappointing though. As a new potential in-app/google
checkout user, its pretty discomforting to know the most useful part
of developing and integrating in-app payments -- the sandbox -- isn't
working, let alone the last message on the thread was over 60 days
ago! Sighhhh

Perhaps they'll be updates soon.

Ed Chavez

unread,
Mar 6, 2012, 10:26:55 AM3/6/12
to in-app-...@googlegroups.com
Seems fixed now (the sandbox url)
Reply all
Reply to author
Forward
0 new messages