• My company is trying to switch the credit card processor and payment gateway on our WooCommerce website. But we’re having a problem. We have site members, which are handled in WooCommerce as a type of subscription. Customers have always been able to store their payment information with the site’s payment gateway, so that their membership automatically renews every month using the stored payment method.

    Now we want to switch to a new credit card processor and a new gateway, to save money and also make ACH payments accessible. But the new gateway doesn’t have any of the old gateway’s stored payment info, so all those hundreds of subscriptions switch to “manual renewal” and each user would have to reenter their payment information into the new gateway. For multiple reasons, this isn’t acceptable.

    How can we get the stored payment information to the new gateway, in a form that can be used to pick up the rolling renewal payments without forcing our end users to reenter their payment information??

Viewing 1 replies (of 1 total)
  • Plugin Support Mahfuzur Rahman(woo-hc)

    (@mahfuzurwp)

    Hi @jswoolf01,

    Migrating stored payment details between gateways is generally not possible due to security and PCI compliance restrictions. Since the new gateway doesn’t have access to the old stored payment methods, existing subscriptions default to manual renewal.

    One approach is to keep the old payment gateway active alongside the new one so that existing subscriptions continue processing through the original gateway while new ones use the new gateway. Over time, as subscriptions naturally renew or expire, more users will transition to the new system.

    Another option is to notify users and request them to update their payment details. WooCommerce Subscriptions allows sending renewal reminders with a link for users to add a new payment method, making the transition smoother. While this requires user action, clear communication can help minimize friction.

    Thank you.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.