question

foodstorm avatar image
foodstorm asked foodstorm commented

Are vaulted cards from Remote Pay compatible with e-commerce API?

Hi there,

We are vaulting cards from Clover devices using the Remote Pay Javascript SDK.

When attempting to process a payment via the e-commerce API, using the token from Remote Pay, we always get a 401 Unauthorized error - see request & response below.

The documentation says that the Developer Pay API has been superseded by the E-Commerce API, but am I right in thinking that we need to stick with the Developer Pay API for tokens returned from Remote Pay?

Thanks,
Anthony.


Request:

https://scl-sandbox.dev.clover.com/v1/charges


Authorization: Bearer c3e0f****db86

Accept: application/json

Content-Type: application/json

{

"amount":10725,

"currency":"usd",

"external_reference_id":"6679",

"source":"7297162975886668"

}


Response:

StatusCode = 401

X-Clover-Request-Id: 55f10de7-52e5-4ce3-5563-bb0ccf543aa1

...

{

"message":"401 Unauthorized",

"error":{

"code":"processing_error",

"message":"401 Unauthorized"

}

}

e-commerce apiDeveloper Pay APIRemote Pay Cloud
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

·
David Marginian avatar image
David Marginian Deactivated answered foodstorm commented

No, tokens returned from the device are not compatible with the new ecomm API.

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.

foodstorm avatar image foodstorm commented ·

Thank you. We got it working with the Developer Pay Api, Cheers.

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