question

daniel-1 avatar image
daniel-1 asked bryanvargas commented

Getting Unauthorized response when trying to connect to device using the Pay Display App

We have developed an integration using the REST Pay Display API to capture payment tokens on a clover device. In sandbox we are able to get a list of devices for our application and connect to it using REST just fine. Now that we are attempting to use with prod account, I'm getting an unauthorized response when I try to communicate with the device.

Using the merchant access token, I can get the list of devices fine. But when attempting a call like

connect/v1/device/read-confirmation

Then I get the following

{ "message" : "Unauthorized" , "requestId" : "b7ffbcbb-9025292" , "type" : "UNAUTHORIZED" }


Is there another step in production accounts that is needed before we can communicate with devices on the merchant account?

Cloud Pay Display
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.

2 Answers

·
bryanvargas avatar image
bryanvargas answered daniel-1 commented

Did you change the URL to a prod URL, did you get a new OAuth token, here are some troubleshooting steps:

https://docs.clover.com/docs/401-unauthorized

1 comment
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.

daniel-1 avatar image daniel-1 commented ·

Yes, I'm using the prod URLs with a fresh OAuth token. Like I mentioned, I was able to get the device list fine using the current token by calling this url with the api token

https://api.clover.com/v3/merchants/{MerchantID}/devices

But when I try sending a confirmation to a specific device, I'm getting the above unauthorized response from the url

https://api.clover.com/connect/v1/device/read-confirmation

What I don't know is if there is some setting that needs to be enabled to allow the cloud pay display app.

0 Likes 0 ·
daniel-1 avatar image
daniel-1 answered bryanvargas commented

We were able to get around the 401 response by updating our app to require all permissions. It appears this is required to use Cloud Display App. We can successful run card not present transactions such as manual entry, however card present transactions are all failing.

I see that this document says the supportsMultiPayToken: true is also required for card present transactions. This is set to false currently on our merchant.

https://docs.clover.com/docs/creating-a-card-token

How can we change this to true?

1 comment
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.

bryanvargas avatar image bryanvargas ♦♦ commented ·

if this is a test merchant, you can email developer-relations@devrel.clover.com and see if they can update some of your merchant settings.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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

Welcome to the
Clover Developer Community