Title: Enabling tokenization for subscriptions Last modified: May 29, 2020 --- # Enabling tokenization for subscriptions * Resolved [tgar8033](https://wordpress.org/support/users/tgar8033/) * (@tgar8033) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/) * Hello and thanks in advance for the help. I am trying to set up Square through my woocommerce website. When I connected my square account to my woocommerce account and tried to start accepting square as a payment option i got “Square is inactive for subscription transactions. Please enable tokenization to activate Square for Subscriptions.” I saw a previous thread that stated checking the box that says “Allow customers to securely save their payment details for future checkout.” When i do that, the error regarding tokenization goes away, but when users try to check out they get “an error occured, please try again or try an alternate form of payment”. I am stuck and am looking for any help. thanks again! Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Support [slash1andy](https://wordpress.org/support/users/slash1andy/) * (@slash1andy) * Automattic Happiness Engineer * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12928085) * Hey there! * You are correct, you do need to enable that setting in WooCommerce to allow your customers to save their cards. If you are not getting that error with regular sales, and getting the error after checking that, then there’s likely an issue with your Square account, perhaps it’s not set up to allow customers to save cards. I would recommend getting in contact with them to confirm that is the case (that your account is allowed to save cards). * Thread Starter [tgar8033](https://wordpress.org/support/users/tgar8033/) * (@tgar8033) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12935268) * I’ll check with square. It is frustrating not being able to take orders as I am constantly getting an error. Thanks for the reply and I’ll post back on here once I hear back from square * [Elvira K.](https://wordpress.org/support/users/treibalen/) * (@treibalen) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12937120) * Hi there [@tgar8033](https://wordpress.org/support/users/tgar8033/), * I’m sorry to hear that the issue is not resolved. * While you’re checking with Square, can I ask you to run one more test for us which may help determine what’s going on? * – enabled logging in WooCommerce > Settings > Payments > Square: [https://d.pr/i/SwW3xc](https://d.pr/i/SwW3xc) – place a test order on your site. You can create a test product with a $1 price to do that. – check logs in WooCommerce > Status > Logs > choose `square_credit_card` from the drop-down: [https://d.pr/i/eNZDfM](https://d.pr/i/eNZDfM) * Do you see any error there? If yes, can you please share it with us? Please redact any personal and sensitive information from there before posting. * Looking forward to hearing back from you! * Thread Starter [tgar8033](https://wordpress.org/support/users/tgar8033/) * (@tgar8033) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12950579) * hello Elvira, followed all your steps and this is what i get: * 06-07-2020 @ 15:00:11 – Square.js Response: Array ( [digital_wallet_type] => NONE [card_brand] => VISA [last_4] => XXXX [exp_month] => X [exp_year] => XXXX[ billing_postal_code] => XXXXX ) * 06-07-2020 @ 15:00:12 – Square.js Response: Array ( [code] => INVALID_ENUM_VALUE[ type] => INVALID_REQUEST_ERROR [message] => is not a valid enum value for `verification_details. billing_contact.country`.: verification_details.billing_contact.country ) * Any idea what could be wrong! thanks so much once again for your help * [Elvira K.](https://wordpress.org/support/users/treibalen/) * (@treibalen) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12959545) * Hi there [@tgar8033](https://wordpress.org/support/users/tgar8033/), * Thank you for the log! It is very helpful. * I saw the same error on sites where some of the checkout fields have been hidden. * Did you alter any of your checkout fields? If yes, does the payment go through if you roll back these changes? * Let me know how that goes! * Thread Starter [tgar8033](https://wordpress.org/support/users/tgar8033/) * (@tgar8033) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12978428) * [@treibalen](https://wordpress.org/support/users/treibalen/) thank you so much for the help! it worked! * [Elvira K.](https://wordpress.org/support/users/treibalen/) * (@treibalen) * [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12985955) * Hi there [@tgar8033](https://wordpress.org/support/users/tgar8033/), * You’re very welcome, I’m glad to hear that you figured it out 🙂 * I’ll mark the thread as Resolved now. Enjoy the rest of your day and stay safe! Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Enabling tokenization for subscriptions’ is closed to new replies. * ![](https://ps.w.org/woocommerce-square/assets/icon-256x256.png?rev=3234354) * [WooCommerce Square](https://wordpress.org/plugins/woocommerce-square/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-square/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce-square/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce-square/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-square/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce-square/reviews/) * 7 replies * 3 participants * Last reply from: [Elvira K.](https://wordpress.org/support/users/treibalen/) * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/enabling-tokenization-for-subscriptions/#post-12985955) * Status: resolved