question

bjphilli avatar image
bjphilli asked georgeono commented

Confusion with Merchants in Sandbox Environment

I'm trying to run the remote cloud pay sample app. When I try to run the "Main Example", I give it my App ID and click Authenticate to Clover. It redirects me to a page in the sandbox environment to select a merchant, but there are no merchant options. However, on the Your Apps tab, I can see that my app has 1 merchant with the app installed (which makes sense, we do have a Clover Mini set up and linked to a Merchant in the Dev Kit tab.) How come I can't see this Merchant when trying to use the sample app?

If I try to create a merchant in the sandbox environment, when I click submit it always asks me to log in (even though I am already logged in) and I'm getting a 401 response. Is there some limit on creating merchant accounts in the sandbox environment? My account is an admin role with all available permissions allowed.

SandboxMerchant
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

anthonypinto avatar image
anthonypinto answered georgeono commented

In order for the example to work as expected you will need the following:

  • The sample server running

  • A web app in the sandbox appmarket (pointed to the example server's base url)

  • A sandbox test merchant with the web app installed.

  • A Clover Mini Devkit, with the Cloud Pay Display app installed from the app market

In order to create a test merchant on sandbox, you must create a sandbox developer account here: https://sandbox.dev.clover.com/develo...

This account is separate from any production developer accounts.

Edited 3/24/16

Additionally you should confirm the following:

  1. you are authenticating with the correct ClientId (AppId) and via the correct server. The latest version of the library has selects for preset configs for these values. You can customize these values for your own app here: https://github.com/clover/remote-pay-...

  2. You have configured your browser to accept the included self signed certificate in order to test using the SSL as described here: https://github.com/clover/remote-pay-...

7 comments
10 |2000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

bjphilli avatar image bjphilli commented ·

Anthony,

I have all of these things set up. I have 2 problems still with running the sample (I'm just trying to do the "Main Example")

1: After I authenticate with Clover, the app makes a call to /v3/merchants/{mId}/devices, but I get a "No Access-Control-Allow-Origin header present" error. My local server is set up at the default https://localhost:8443 and I have set up the CORS domain on the sandbox app to match that.

2: If I ignore this warning in Chrome, I can see my Clover mini, but when I try to pair with the device, it returns unauthorized with the response "logged out."

0 Likes 0 ·
anthonypinto avatar image anthonypinto commented ·

Ok, thanks @bjphilli, we are working to try and track this bug down. I appreciate your patience, and we'll update as soon as we have any more information.

0 Likes 0 ·
bjphilli avatar image bjphilli commented ·

@AnthonyPinto do you have any update on this?

0 Likes 0 ·
anthonypinto avatar image anthonypinto commented ·

Can I ask what browser(s) you have tested this on?

0 Likes 0 ·
bjphilli avatar image bjphilli commented ·

I've tried Chrome, Firefox, and Edge. Same issue on each.

0 Likes 0 ·
Show more comments

Welcome to the
Clover Developer Community