Just to elaborate:

It is a matter of the oAuth implementation. You use ‘init’ hook to check for authorization token.

Instead if you use the wc-api, you can just use the woocommerce_api_class_name to do the same. This way the code will be triggered only for their implementation and there will be no conflict. For this you will need to change the redirect_uri of the auth process

Hope that helps

Any chance you can look into it? I’m just passing on the advice from our developer.. If not, let me know and I’ll discuss with him about changing this.

Cheers

It’s an issue that will occur with anyone using the wc-api. For instance any other plugin from WooCommerce Extension directory using wc-api (not just our custom development).

You use ‘init’ hook to check for authorization token. Instead if you use the wc-api, you can just use the woocommerce_api_class_name to do the same.

This way the code will be triggered only for their implementation and there will be no conflict. For this you will need to change the redirect_uri of the auth process.

Does that make sense? Thanks

update: this was our fix:

// stripe - wc-vendors - fix

if ( function_exists( 'stripe_check_connect' ) ) {
   remove_action( 'init', 'stripe_check_connect' );
   add_action( 'parse_request', 'stripe_check_connect', 15 );
  }