“Account is not enabled for card processing” error code

Hello,

We have keep getting an error code with this info:

{"errors":[{"category":"INVALID_REQUEST_ERROR","code":"CARD_PROCESSING_NOT_ENABLED","detail":"Account is not enabled for card processing, visit www.squareup.com/activate"}]}

This has been happening for a little over a month. We have tried calling Square several times, hours at a time and they said because the issue is only sporadic and we have some online orders work and all in person orders work that Square has no issues and they can’t help.

We have deactivated and reactivated the Square integration on the website.

What will it take to finally fix this?

:wave: I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Additional Documentation

Handling Errors
Get Started
Troubleshoot In-App Payments SDK Problems

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

The error message you’re seeing, “CARD_PROCESSING_NOT_ENABLED”, indicates that the Square account you’re trying to process payments with is not enabled for card processing. This could be due to a variety of reasons, such as the account not being fully set up or activated for card processing.

To resolve this issue, you should visit Sign up for Square and complete the necessary steps to activate your account for card processing. Make sure all the required information is correctly filled out and that your account is in good standing.

If you’ve already done this and are still experiencing the issue, it might be a good idea to double-check the account credentials you’re using in your integration. Ensure you’re using the correct access token for the Square account that has been activated for card processing.

This answer was reviewed by @Bryan-Square.

What’s the location_id that your trying to process the payment with? :slightly_smiling_face:

I know the message indicates that the account is not enabled. However, it is fully enabled and set up. We have no issues with some orders but errors with others. And no issues with in person orders.

What’s the location_id that your trying to process the payment with and what are the payloads that your getting this error with? Are you consistently getting this error with certain payloads for the request? :slightly_smiling_face:

Please tell me how to locate the location id? And what does a payload mean? Perhaps is there someone that can walk me through this on the phone?

I took a look at your account and it looks like your using our WooCommerce integration. You’ll want to reach out to them for assistance since all API functions are managed by them. :slightly_smiling_face:

With all due respect, we have already reached out to WooCommerce and they said this is a Square issue. And it’s a Square error code. Please help us?

Do you have more then one Square account and is the one that’s connected to the integration the one connected to the WooCommerce integration. :slightly_smiling_face:

We only have one Square account.

Is the email address associated to the account the same as the email associated to your Forum profile? :slightly_smiling_face:

Yes it is the same email address.

That account is active however one of your locations is deactivated which may be causing the error. You can reactivate at any time. To do so:

  1. Visit Locations > Select Status (Inactive).
  2. Click the location you wish to reactivate.
  3. Click Reactivate Location.

After you reactivate the location does the integration work? :slightly_smiling_face:

I checked and all locations that we use are active. Keep in mind this is in intermittent issue (but has lost us thousands) so I’m not sure what to do?

If that’s the case then WooCommerce will need to identify what location_id they’re passing into the CreatePayment request when this error happens to see if it different then the location_id for your account. That’s would be the next step. :slightly_smiling_face:

Here are the console logs from when I try to make a subscription payment

JQMIGRATE: Migrate is installed, version 3.4.1 jquery-migrate.min.js:2:981
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. above-the-fold.min.js:1:4877
Feature Policy: Skipping unsupported feature name “encrypted-media”. 2 checkout
Some cookies are misusing the recommended “SameSite“ attribute 9
Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. like.php
Request to access cookie or storage on “https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Ffacebook.com%2Fthegoldenpetlife&width=0&layout=button_count&action=like&size=large&share=true&height=46&appId=430846707655101” was blocked because it came from a tracker and content blocking is enabled.
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:9535
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:10094
Square: Building payment form wc-square.min.js:1:12363
Partitioned cookie or storage access was provided to “https://web.squarecdn.com/1.54.6/main-iframe.html?applicationId=sq0idp-wGVapF8sNt9PLrdj5znuKA&hostname=goldenpetlife.com” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Square: Payment form loaded square.js:1:84956
Partitioned cookie or storage access was provided to “https://web.squarecdn.com/1.54.6/single-card-element-iframe.html” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Partitioned cookie or storage access was provided to “https://connect.squareup.com/payments/data/frame.html?referer=https%3A%2F%2Fgoldenpetlife.com%2Fcheckout” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Square: Requesting payment nonce square.js:1:84956
Square: Card data received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verifying buyer square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verification result received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Payment nonce present, placing order square.js:1:84956
Square: Requesting payment nonce square.js:1:84956
Square: Card data received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verifying buyer square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verification result received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Payment nonce present, placing order square.js:1:84956

When we make a one-time, no subscription purchase, these are the console logs for a successful one-time purchase:

Some cookies are misusing the recommended “SameSite“ attribute 9
JQMIGRATE: Migrate is installed, version 3.4.1 jquery-migrate.min.js:2:981
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. above-the-fold.min.js:1:4877
Feature Policy: Skipping unsupported feature name “encrypted-media”. 2 checkout
Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. like.php
Request to access cookie or storage on “https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Ffacebook.com%2Fthegoldenpetlife&width=0&layout=button_count&action=like&size=large&share=true&height=46&appId=430846707655101” was blocked because it came from a tracker and content blocking is enabled.
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:9535
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:10094
Square: Building payment form wc-square.min.js:1:12363
Partitioned cookie or storage access was provided to “https://web.squarecdn.com/1.54.6/main-iframe.html?applicationId=sq0idp-wGVapF8sNt9PLrdj5znuKA&hostname=goldenpetlife.com” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Square: Payment form loaded square.js:1:84956
Partitioned cookie or storage access was provided to “https://web.squarecdn.com/1.54.6/single-card-element-iframe.html” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Partitioned cookie or storage access was provided to “https://connect.squareup.com/payments/data/frame.html?referer=https%3A%2F%2Fgoldenpetlife.com%2Fcheckout” because it is loaded in the third-party context and dynamic state partitioning is enabled.
Square: Requesting payment nonce square.js:1:84956
Square: Card data received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verifying buyer square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Verification result received square.js:1:84956
Square: [object Object] square.js:1:84956
Square: Payment nonce present, placing order square.js:1:84956
Navigated to https://goldenpetlife.com/checkout/order-received/3312?key=wc_order_kTn8dlraS3mW7
Some cookies are misusing the recommended “SameSite“ attribute 10
JQMIGRATE: Migrate is installed, version 3.4.1 jquery-migrate.min.js:2:981
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. above-the-fold.min.js:1:4877
Feature Policy: Skipping unsupported feature name “encrypted-media”. 3312
Feature Policy: Skipping unsupported feature name “encrypted-media”. 3312
Content-Security-Policy: Ignoring ‘block-all-mixed-content’ because mixed content display upgrading makes block-all-mixed-content obsolete. like.php
Request to access cookie or storage on “https://www.facebook.com/plugins/like.php?href=https%3A%2F%2Ffacebook.com%2Fthegoldenpetlife&width=0&layout=button_count&action=like&size=large&share=true&height=46&appId=430846707655101” was blocked because it came from a tracker and content blocking is enabled.
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:9535
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.xx.fbcdn.net/rsrc.php/v3iEpO4/yD/l/en_US/iGhRcCEw5OK.js?_nc_x=Ij3Wp8lg5Kz like.php:3:10094
Square: No payment form found! wc-square.min.js:1:12363

The error for subscription purchases seems to be occurring at line Square: Payment nonce present, placing order square.js:1:84956 in which the page refreshes and a generic “payment failed” message is presented to the user. At this point on our side, we see the error message outlined in my initial message.

I am unsure how to locate my location_id where would I find this information? And what are you trying to determine from the location_id ? Is this supposed to be “Business Location” under the WooCommerce plugin’s Square tab? (attached as fig. 1)

Once I get my location_id what am I supposed to use this for to debug? How can I find my location_id and then verify it once WooCommerce gets back to me with what the location_id is that they’re passing into the CreatePayment request?

Inside WooCommerce, I also have 2 active subscriptions for my Square account. Could this be affecting only the subscription payment method, but not the one-time payment methods? I’m trying to understand why I can successfully process one-time payment methods but not first time subscription orders.

I’m unsure how to capture the exact payload requests, but this error is consistently and only happening for subscription orders.

Any insights or suggestions on how to further debug much appreciated

Fig. 1

Honestly, this is all something that WooCommerce needs to debug. Since your interacting with the WooCommerce interface I really don’t have any debugging tools. I wanted to know what the location_id is so I could try and see if there is anything wrong with the location. :slightly_smiling_face:

location_id for both subscription orders and one-time payment orders is SHDGZ3A59HBK1

GET request URL is

https://pci-connect.squareup.com/payments/hydrate?applicationId=sq0idp-wGVapF8sNt9PLrdj5znuKA&hostname=goldenpetlife.com&locationId=SHDGZ3A59HBK1&version=1.54.6

Still feel very in the dark as to why subscriptions are not processing but one-time payments are processing. Both subscription transactions and one-time payment transactions are using the same location_id so that shouldn’t be the issue.

How else can we debug this? Any assistance on your end checking if there is anything wrong with the location for the associated location_id would be greatly appreciated.

If I create a new product as a “Simple Product” through the WooCommerce + Square plugin on my Wordpress site and try to buy it as a test, the payment is processed and the order goes through.

However, if I add a new product as a “Simple Subscription” or “Variable Subscription” and try to buy it as a test, the payment fails and the order fails. The error message is the same message I always get:

{"errors":[{"category":"INVALID_REQUEST_ERROR","code":"CARD_PROCESSING_NOT_ENABLED","detail":"Account is not enabled for card processing, visit www.squareup.com/activate"}]}

I’m really confused why this is the error message I get, as it seems like some generic error message that is not necessarily pointing toward the root of the payment processing issue. I only have one Square account, and the account processes orders for a one-time “Simple Product” but not for a “Simple Subscription” or “Variable Subscription.”

What else could be the issue that causes this error message to arise?

You ask for the location_id, but I don’t know where to verify that the location_id that the browser network request is receiving is the accurate location_id to use for my products and purchases. I want to confirm, WooCommerce would be the ones who own my location_id, correct? It’s my understanding that I could find my location_id’s inside of the Developer portal under the Applications tab, however I do not have anything in there. This is the page I see when I go to the Developer account with the only Square account I have:

Is there anywhere else at all that I could be finding my account’s location_id’s? When I go through the network requests in the browser, all products are receiving the location_id: SHDGZ3A59HBK1 is this what you’re able to see on your end?

I’m trying to understand what information I should expect to receive from Square, and what information I should expect to receive from WooCommerce. Square says WooCommerce has all the info, and WooCommerce says to find the location_id from Square.

Put simply, I want to verify that WooCommerce is handling all transaction, locationID, ApplicationID, failed payment processing issues, etc. I keep reading that I need to check what location_id is being passed into the CreatePayment request, but is that not handled through the WooCommerce plugin? There is nowhere in the WooCommerce Square plugin tab that shows identifiable location_id’s, just “Business Location” names.

I feel stuck on the following questions to move forward:

  • How can we verify that these are the correct IDs being passed into the CreatePayment request?
  • Where can I double check that these location IDs are properly set inside of the Square x WooCommerce plugin?
  • Is there a way to verify that these location IDs are associated with the products in my store, or if the products are expecting a different location ID?
  • How can I find what location_id is associated to each “Business Location” I have?
  • Are products set with different location_id’s, and is that through the CreatePayment request? If so, where do I verify what the CreatePayment request is expecting to receive for the location_id?
  • Let’s say this isn’t a location_id issue, where do I go from here to debug?

I’m just trying to move forward with this, so any thoughts on how to further debug greatly appreciated.