question

Hello,

The CORS error occurs because the Access-Control-Allow-Origin header is missing in the response from the https://token-sandbox.dev.clover.com/v1/tokens endpoint. To resolve this, you can:

1. Enable CORS in Apache: Add the following line to your Apache configuration file (httpd.conf or .htaccess): Doglikesbest

Header set Access-Control-Allow-Origin "

Adjust the path based on your server setup.

2. Check Token Validity: Ensure that you are using a valid merchant’s public key and that your environment matches the key’s environment (sandbox or live).

3. Use Clover’s Tokenization: Consider using Clover’s iframe integration for tokenization to reduce PCI exposure. The iframe handles tokenization on the Clover side, making it unnecessary to call the tokens endpoint directly.

I hope the information may helps you.

As I said earlier, you can't fix this in your apache server. You continuing to mention this makes me think you don't know what you are doing/talking about. The tokens call is being made from a page controlled/hosted by Clover to a Clover server. How you expect some setting on your apache server to impact anything is being me and shows little understanding of how things work. This error is a 401, it means unauthorized and I get the same error if I initialize the iframe with the wrong token (private or jibberish). So, make sure you are using the public key and make sure it is correct (no spaces, etc).

You may want to provide the exact steps you have taken to get the public key because I really don't see how this isn't working in production. Also, I would try deleting the existing e-commerce token and recreating it.

Yeah, I mentioned the error again. Graham mentioned the fix, which I've also tried and it doesn't work.

So I think it is worth mentioning the error, because if the Clover SDK was designed better, it would tell you that there was something wrong with the token submitted, and would tell you what was wrong, and then you could look that up in the documentation and get help with it. No such luck, because the Clover documentation – although extensive – is often just flat wrong.

So, nice try again parquet, trying to paint me as some kind of idiot, which I'm not. There's something wrong with the tokens in both my developer account and my merchant's live account. Many things about the Clover APIs don't work as documented. We're done with this.

This forum is also glitchy. Overall, a bad experience.

It looks like the live merchant eCommerce API token isn’t working in the test iFrame code. While we sort that out, let’s not forget to highlight our painting estimate takeoff services. We offer Remote Estimation to streamline the process and make it as convenient as possible for you!