Title: Tokenization too strict!
Last modified: August 6, 2021

---

# Tokenization too strict!

 *  Resolved [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/)
 * Our online store averages about 10 orders a day. Since I updated the plugin to
   3.3.4 this afternoon, half of our orders have been stuck in Pending Payment. 
   The user is getting the error that their card is banned for too many attempts,
   but this is their first order of the day (some order weekly). When I went into
   the payment settings, there were no cards in the tokenization box to clear to
   allow payments to go through. I had to disable iFrame tokenization to try to 
   allow orders to go through.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ftokenization-too-strict%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 15 replies - 1 through 15 (of 15 total)

 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14748984)
 * Hi [@maggiecameron](https://wordpress.org/support/users/maggiecameron/)
    Are 
   you able to use a plugin to clean up transients in your database? I suspect that
   old transients may be the cause.
 * After cleaning out the transients, set your CardPointe WooCommerce settings to
   for the new card tries to something higher.
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14753334)
 * Thank you. I have cleared both Woo and WordPress transients. We set the tries
   to 5 instead of 3 and re-enabled iframe tokenization.
 * We have not had an attempted purchase since then, but I will reply if the problem
   persists. Thanks again!
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14753386)
 * [@maggiecameron](https://wordpress.org/support/users/maggiecameron/) Thanks for
   the follow up. I’m going to close this thread, but feel free to re-open if you
   need assistance.
    If you still have issues with the new 3.3.4 security features,
   please try downloading and using the 3.3.2 version until we can resolve your 
   issue. [https://downloads.wordpress.org/plugin/cardconnect-payment-module.3.3.2.zip](https://downloads.wordpress.org/plugin/cardconnect-payment-module.3.3.2.zip)
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14761454)
 * I need to reopen this thread. The suggestion above worked for a while, but the
   same thing is happening again. The most recent customer has two cards saved in
   the payment gateway and even tried to enter a third card. All getting same message.
   In addition, none of the banned cards are available for deletion in the payment
   gateway plugin settings. I will roll back to the previous release after 2pm today.
   The store has a high volume of traffic until then.
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14761868)
 * [@maggiecameron](https://wordpress.org/support/users/maggiecameron/) Yes, I would
   advise that you roll the plugin back as soon as you can, and make sure you use
   the iframe setting for security reasons.
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14763323)
 * Ok, we are rolled back to 3.3.2 and have iframe setting ticked. What’s next? 
   Thank you!
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14765053)
 * [@maggiecameron](https://wordpress.org/support/users/maggiecameron/) Make sure
   you are using the ReCaptcha and Iframe settings. 3.3.2 does not ban cards or 
   orders. We are looking into the issue internally, and once we have a reliable
   candidate, we can release a new version.
 * Thanks for your patience and understanding.
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14765928)
 * Yes, we also have ReCaptcha running. Thank you for looking into this!
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14803964)
 * See above. I’m still running 3.3.2 because of that tokenization issue. How will
   I know when it’s safe to upgrade?
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 9 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-14804014)
 * [@maggiecameron](https://wordpress.org/support/users/maggiecameron/) Once we 
   can get approval to make the settings optional, I will update this thread. You
   are safe to stay on the version you are currently running, as long as you keep
   ReCaptcha turned on and are using the Iframe methods.
 *  Thread Starter [maggiecameron](https://wordpress.org/support/users/maggiecameron/)
 * (@maggiecameron)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15058381)
 * Hello, just checking on the status of this. We are running 3.3.2. Did the 3.3.5
   release address this? We are doing fine on 3.3.2–just wanted an update.
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15058682)
 * [@maggiecameron](https://wordpress.org/support/users/maggiecameron/) We have 
   not received any approval to make the settings optional, as of yet. The only 
   difference between your version, and the latest, are the tokenization security
   settings. I suggest reaching out to your rep to request this change.
 *  [iulights](https://wordpress.org/support/users/iulights/)
 * (@iulights)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15060040)
 * Hello,
 * I am having a similar issue.
 * I set the “Maximum Credit Card Attempts” to 5. This is supposed to limit the 
   number of credit card attempts PER ORDER that a customer can try to 5 for one
   credit card.
 * What it actually does it limit the number of uses our customers can have with
   one credit card to 5 attempts across all orders.
 * Basically if any of our customers try to place 5 orders in one day, the first
   4 orders will process through without a problem then the 5th order will ban their
   card. Then I have to go delete it from the BANNED cards list.
 * I need this feature fixed so that the credit card attempts are only limited to
   a PER ORDER basis. This is how the feature explains that it is supposed to work.
 * Please advise on when I can expect this fix to take place.
 * Best Regards,
 *  Plugin Author [RexAK](https://wordpress.org/support/users/rexak/)
 * (@rexak)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15060067)
 * [@iulights](https://wordpress.org/support/users/iulights/) You’ll need to start
   a new support thread, as this one is closed and I will not be notified of further
   responses.
    In the meantime, I’ll check the plugin code to see if I can get this
   resolved for you.
 *  [iulights](https://wordpress.org/support/users/iulights/)
 * (@iulights)
 * [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15060162)
 * Ok Thanks! I started a new topic with this issue.

Viewing 15 replies - 1 through 15 (of 15 total)

The topic ‘Tokenization too strict!’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/cardconnect-payment-module.svg)
 * [CardPointe Payment Gateway for WooCommerce](https://wordpress.org/plugins/cardconnect-payment-module/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cardconnect-payment-module/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cardconnect-payment-module/)
 * [Active Topics](https://wordpress.org/support/plugin/cardconnect-payment-module/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cardconnect-payment-module/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cardconnect-payment-module/reviews/)

## Tags

 * [tokenization](https://wordpress.org/support/topic-tag/tokenization/)

 * 15 replies
 * 3 participants
 * Last reply from: [iulights](https://wordpress.org/support/users/iulights/)
 * Last activity: [4 years, 7 months ago](https://wordpress.org/support/topic/tokenization-too-strict/#post-15060162)
 * Status: resolved