Changing Stripe Gateway Plugins

Hi @toulip,

Our biggest concern is: after moving to your plugin, will our active subscriptions continue to properly and automatically renew using the existing customer data and tokens already had been created from the previous plugin?

Yes, your active subscriptions will continue to process and automatically renew. This plugin knows how to read the data from your current plugin and use that to process the renewal payments. Your customer’s payment info etc will also be automatically migrated over.

Switching to our plugin is very seamless. The only thing you need to do is Connect the plugin via the API Settings page then enable any payment methods and options that match your business needs. Everything else will be automatic.

You can always do a trial run on your staging site to test and see that the migration happens automatically.

Kind Regards,

Hello Mr Clayton,

Thank you so much for your quick response.

Sounds great! I will do so.

Btw, does it matter the order of the actions that I should take?

I mean I need first to enable your plugin, set up my settings, and finally deactivate the old plugin?

Thanks again!

Btw, does it matter the order of the actions that I should take?

Good question. I would recommend installing this plugin, activating it, then connecting it to your Stripe account. Enable all the payment methods like credit cards, etc. Then you can disable the other Stripe plugin.

You can enable the ACH payment method later since you don’t currently have any subscriptions for that payment method.

Kind Regards,

Hello again Mr Clayton,

Thank you so much for the instructions provided above.

I will do as described and of course let you know if I face any issues upon the procedure of transition.

Thanks again, have a great day!

Hello again Mr Clayton,

I wanted to ask something extra.

After I read the WooCommerce subscriptions documentation, I found a topic talking about changing payment gateways plugins and what then will happen to active subscriptions.

Similar to my case.

So, I found that in order to avoid any issues with existing subscriptions and their automatic recurring payments, I can keep the old Stripe Plugin along with yours one.

However, for the old plugin, I will only need to disable the payment gateway from Woocommerce->Settings->Payments. I will not deactivate the plugin.

This way I can make sure that all existing subscriptions will continue to work until they expire.

Finally, I will activate your plugin and enable your payment gateway from Woocommerce->Settings->Payments. This way, all new subscriptions and orders will see only your payment gateway at the checkout.

Please, let me know what you think and if there are any potential conflicts caused by keeping both plugins activated this way.

Thanks in advance,

George.

Hi @toulip

So, I found that in order to avoid any issues with existing subscriptions and their automatic recurring payments, I can keep the old Stripe Plugin along with yours one.

That isn’t necessary. We have many merchants that switch over and don’t leave the other plugin enabled. If you have doubts, you can always test on your staging site to confirm what I have said.

Kind Regards,

Ok, sounds good.

But, what I must check on the staging site? I cannot charge the clients from a test environment to see if their payments go through successfully.

For what exactly I will need to look at the staging website to verify that everything will work as promised on the live one?

Thanks in advance,

@toulip

You can set the other Stripe Plugin to test mode on your staging site and then purchase a subscription using a test card. You can then switch over to our plug-in and then process the renewal and you’ll see that it all works.

@mrclayton

This makes sense!!

Well, I will do so and let you know here how this went.

Thank you so much again for your valuable help.

Your support was great!

Best Regards,

George.

@mrclayton hello!

I am sending you to let you know that I have just tested the full transition on a staging environment, and everything worked as promised! Magnificent work!

On another topic you may be aware of and could help us…

We are now going to add the ACH Stripe payments as a new checkout option. We saw that it is required a Plaid account to do so. We created one and then made test transactions and everything again worked great! To go live now with Plaid, we need to subscribe for a premium plan with them in order to get the required production secret key.

We saw that they offer 2 options, a pay as you go one, and a subscription plan that costs 500$/month.

Since we are going to use Plaid only for your plugin, do you know from previous clients of yours if the pay as you go option is enough for the plugin to work properly?

Finally, are you aware of their fees (pay as you go) based on your plugin’s request to their API?

Thanks in advance,

Hello again @mrclayton,

I am sending you this message to update you on my previous concern.

I have already contacted the Plaid sales team and now I am aware of what and how they charge for their service.

I only have one question for you which I guess you are aware of and could help:

The Plaid sales team told me that there are 3 ways to call their service.

1. Auth
2. Identity
3. Balance

Every way has its own unique pricing policy, but no significant differences.

Could you please let me know which of them your plugin uses to connect to their service?

Thank you so much in advance,

George!

Hi @toulip,

The plugin uses the Auth product.

Kind Regards,

@mrclayton Thank you so much for this!!

Once again, great and quick support from your side!

Have a nice day!

Best Regards,

George!