alienjackhammer

We are getting intermittent checkout failures. The plugin logs show the failure occurs when attempting to save a new card to CIM during checkout:

• Request: createCustomerPaymentProfileRequest
• Response: E00114 Invalid OTS Token
• This happens after Retrieved opaque card data and after validating the customer profile (getCustomerProfileRequest OK).
• The plugin aborts payment when saving fails: Payment processing failed … error_message: Invalid OTS Token … is_store_api: false

Request: Please update the flow so that if CIM save fails with E00114, the plugin still charges the order using the opaque data (or changes sequence: create payment profile first, then charge via profile), instead of failing the entire checkout. Also confirm whether the plugin is reusing the opaqueData token across multiple API calls or delaying token use long enough to expire.

I used my purchasing account (search66@gmail.com) to open two tickets. It’s been about a month since my last one. And the TOC JS was injecting itself into my site even though it wasn’t in use. I ended up writing a code snippet to remove it.

/**

• Smart Dequeue for AIOSEO Table of Contents (Pro & Free)
• Scans registered scripts for the specific TOC file and removes it.
  */
  function fuzion_remove_aioseo_toc_smart() {
  global $wp_scripts; if ( ! is_a( $wp_scripts, ‘WP_Scripts’ ) ) {
  return;
  } foreach ( $wp_scripts->registered as $handle => $script ) {
  // Check if the script source URL contains ‘table-of-contents’ AND ‘all-in-one-seo’
  if ( strpos( $script->src, ‘table-of-contents’ ) !== false && strpos( $script->src, ‘all-in-one-seo’ ) !== false ) {
  wp_dequeue_script( $handle );
  wp_deregister_script( $handle );
  }
  }
  }
  // We use a late priority (100) to ensure we run AFTER AIOSEO has added the script
  add_action( ‘wp_enqueue_scripts’, ‘fuzion_remove_aioseo_toc_smart’, 100 );
  add_action( ‘wp_footer’, ‘fuzion_remove_aioseo_toc_smart’, 1 ); // Double check for footer scripts

No. I thought the newest updates to woocommere and/or wordpress would have fix it… Still in the same boat.

Thanks for the clarification. Given the earlier issues where Cart and Checkout blocks were rendering as Unsupported in the editor, I’m going to avoid transforming into blocks… I’ll just live with the ability not to edit the cart/checkout and maybe down the road an update will fix it. Not sure, honestly.

I will try adding a new page with a checkout block and see what happens. As far as pressing the button… It automatically installs some plugin called Fluid Checkout (which is odd).

I put activated a new theme and disabled plugins; still same issue.

I’ll give it a shot. Thanks.