Concerned about switching plugins

  • Resolved alifallahrn

    (@alifallahrn)


    1 year, 9 months ago

    Hi there,

    We are currently using the “WooCommerce Stripe Gateway” plugin for Credit Card payment, but we tested your plugin for Apple Pay and found it to be satisfactory.

    Before implementing your plugin in our production environment, we have a question: If we decide to completely switch to your plugin for both Credit Card and Apple Pay payment options, will there be any issues with the subscriptions that were previously purchased using the “WooCommerce Stripe Gateway” plugin and paid for with Credit Card?

    Is it possible to migrate these subscriptions or do you have any other suggestions?

    If a migration is not possible, could we continue to use the “WooCommerce Stripe Gateway” plugin for Credit Card payment and your plugin for Apple Pay instead?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    1 year, 9 months ago

    Hi @alifallahrn

    Is it possible to migrate these subscriptions or do you have any other suggestions?

    You don’t need to do anything, our Stripe plugin is designed to automatically process renewal orders that were created using the WooCommerce Stripe Gateway plugin. This allows you to seamlessly migrate to our plugin.

    We always recommend testing on your staging site as a sanity check but we’ve had many merchants make the switch. All you have to do is install our plugin and it will handle processing the renewal orders for subscriptions created using the other Stripe plugin.

    Kind Regards,

    Thread Starter alifallahrn

    (@alifallahrn)

    1 year, 9 months ago

    Hi @mrclayton

    Thank you, We activated it in production without any issues.

    However, we have noticed that the structure of payment method tokens for the previous plugin was “src_XXXXXXX,” but the structure for your plugin is “pm_XXXXXXX.”

    Is this a normal situation? Can we be sure that previous users with a different payment method token structure will have their subscription renewed smoothly?

    Thanks

    Plugin Author Payment Plugins

    (@mrclayton)

    1 year, 9 months ago

    However, we have noticed that the structure of payment method tokens for the previous plugin was “src_XXXXXXX,” but the structure for your plugin is “pm_XXXXXXX.”

    That’s normal and expected. Our plugin uses the payment method API via Payment Intents which is the recommended approach by Stripe. Their Payment Intent API can handle “src_” and “pm_” payment types. Your subscriptions will renew smoothly.

    Kind Regards,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Concerned about switching plugins’ is closed to new replies.