Sorry, we could not add that reade

Hi Phil,

That’s the error response message from Stripe’s API, so the best thing for you to do is check your Stripe API logs. You can find these in the “developers” portion of your Stripe dashboard on the top-right corner of your screen.

In reviewing your account it looks like you got your reader connected successfully in test mode on the location “Performance Culture”. It looks like you’ve mistakenly reentered the authorization string as the device’s label “item-kangaroo-together”. There are 2 separate prompts you’ll see (the 1st is the code, the second one asks you for a label).

Keep in mind that Stripe Connect authorization is separate for live and test mode, so you’ll want to be sure to complete both of those processes if you haven’t already. Your account number is the same regardless, so that acct_1LU… value should be in the account ID field whether you’re in live or test mode.

I don’t receive a second prompt when I enter the three-word code, though, it just gives me the error message immediately after entering it. Do I inadvertently have it in test mode?

Does it matter that we have the wisepos machine?

Hi there,

Okay, I got it working from the website! Now how do I get it connected to Point of Sale for Woocommerce?

Hi Phil,

The WisePOSE is the preferred device, so that’s the best one to use. Both of those prompts occur prior to the submission, so you would see both before the error message. I can’t atest to whether you have it in test mode, that’s something you’ll have to check within your settings.

Regarding Point of Sale for WooCommerce, we are not the developers of that plugin. The checkout procedure for our plugin can be performed with WooCommerce’s existing frontend checkout procedure or the backend checkout procedure available on all WooCommerce sites in the “Orders” panel labeled “customer payment page”. Our plugin will add the gateway to the Woocommerce payments section like any other gateway and proceed through checkout with the StripeJS SDK. If you have trouble getting the plugin available in a third party POS plugin you’ll need to discuss with that plugin developer. You can also fork off of this adaptation of the Kilbot WCPOS plugin which provides a compatibility patch but please note we do not support/maintain this codebase, so upgrades will be required: https://github.com/arcanestrategies/stripe-terminal-for-woocommerce-pos

Hi Phil,
Just as a quick follow-up for others with a similar situation as yours, please post the link to the POS you’re referring to. There are MANY WooCommerce POS plugins which use that name. The most commonly used one “WooCommerce POS” is by Kilbot while other paid extensions are not controlled by the WordPress repository, so they’re not held to any same-name conventions. For example there’s “Point of Sale System for WooCommerce” by Webkul and “Point of Sale for WooCommerce” by Actuality. These plugins all have different gateway and device compatibility. For example, the one by Kilbot requires a paid PRO version for support with 3rd party gateways (like ours) and the one by Actuality only technically supports the Verifone P400 (according to their documentation) which was replaced by the BBPOS Wise POS E roughly 1 year ago.

I had this problem and it turned out to be the Stripe API was set to a 2020 version and not the current one. When I updated it within the Stripe developer’s dashboard it started working.

Thanks again for sharing your findings, Simon. For those reading this, the version in your Stripe developer’s dashboard does not factor into this plugin nor our dependencies as of date of this writing. The API version is specified by us, so you won’t find that fetching the latest upgrade would factor into the plugin’s behavior (unless of course you didn’t have the 2019 or 2020 versions).