Fatal error problem with Stripe Pay Now button

  • Resolved kovka01

    (@kovka01)


    7 months, 1 week ago

    Firstly I would like to thank you for you plugin, it’s a gem! I have used it before.

    Now I get the Fatal error message in a site…
    I only need the Buy Now button for Stripe, not a subscription.
    Using Divi on the site.

    Stripe is connected. API keys are live, OK. (It was working great in test mode.)
    As I create the button I tick: use the general keys.
    All look great, but as I click to the button, getting this message:
    Fatal error! Payment with ref_id swpm_xxxxx|xxxx can’t be found
    So I have tried to fix it with Perplexity AI.
    – No cache plugin is turned on
    – I have turned off the firewall for a while
    – Added a webhook, using this ending: /?swpm_process_stripe_webhook=1
    Than changed it to this: /?swpm_process_stripe_sca_buy_now=1
    The webhook uses two events: checkout.session.completed and payment_intent.succeeded . (Tried it with more, but it hasn’t made a difference.)
    – Added a Restricted key
    – Cancelled every data, and re-connected everything again, step by step.

    Nothing worked.

    The log file only shows:
    [2025/08/08 12:50:55] – SUCCESS: Stripe SCA Buy Now IPN received. Processing request… [2025/08/08 12:50:55] – FAILURE: Fatal error! Payment with ref_id swpm_xxxx|xxxx can’t be found

    So I activated the old, ugly Legacy Pay Now button, enabled it at Stripe, and it works.

    But I would really like to have the new one.

    What more should I do?

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    7 months, 1 week ago

    Thank you for reaching out to us. Please check the following documentation for the Buy Now “Stripe” button. Let me know if you originally followed these instructions yourself.

    https://simple-membership-plugin.com/sca-compliant-stripe-buy-now-button/

    Kind regards.

    Thread Starter kovka01

    (@kovka01)

    7 months, 1 week ago

    @mbrsolution Yes, exactly.

    Plugin Support mbrsolution

    (@mbrsolution)

    7 months, 1 week ago

    What shortcode are you currently using?

    You might also like to carry out the following troubleshooting steps.

    https://simple-membership-plugin.com/payment-testing-checklist-for-simple-membership/

    Let me know how you go.

    Kind regards.

    Thread Starter kovka01

    (@kovka01)

    7 months ago

    OK, I have tried these steps before writing to the forum.

    Actually it worked in Sandbox mode, but in Live mode it never worked.

    The debug showed the messages I have written before.

    The shortcode for the new button is: [swpm_payment_button id=”1658″]
    I have to cancel it from the site, as it is not working.

    Hope it will work. It would be better.

    Plugin Support mbrsolution

    (@mbrsolution)

    7 months ago

    Can you check to make sure the following feature Enable Sandbox or Test Mode is disabled? This is located under WP Membership => Payments => Payment Settings => General.

    Let me know if this helps you.

    Kind regards.

    Thread Starter kovka01

    (@kovka01)

    7 months ago

    Of course it is disabled. Otherwise I could not use the Legacy payment button.

    Plugin Support mbrsolution

    (@mbrsolution)

    7 months ago

    Thank you for sharing that information. I have submitted a message to the developers to investigate further your issue.

    Kind regards.

    Thread Starter kovka01

    (@kovka01)

    7 months ago

    Thank you @mbrsolution .

    Hope they will find the answer soon.

    BR

    Plugin Author wp.insider

    (@wpinsider-1)

    7 months ago

    Hi, This stripe button issue usually happens when there is a theme or plugin conflict on the site. Please try the following test to confirm:

    https://simple-membership-plugin.com/forums/topic/test-for-plugin-and-theme-conflict-before-posting-an-issue-or-a-bug/

    In order to investigate and resolve any potential conflict, we need to be able to reproduce the issue on our test environment. If the issue involves a free theme or plugin, we can usually install it ourselves and attempt to replicate the conflict directly.

    However, in your case, it appears the issue involves a premium (paid) theme that we do not have access to. Unfortunately, without access to the same theme, we’re unable to recreate the issue and identify the source of the conflict. This limits our ability to provide a targeted solution, as we are essentially working blind in this scenario.

    If the conflict is happening with an item that you cannot get rid of, then as an alternative, you might be able to use the following Stripe plugin for membership payments:

    https://wordpress.org/plugins/stripe-payments/

    We have an integration documentation here:

    https://simple-membership-plugin.com/stripe-payments-plugin-integration-for-membership-payment/

    Thread Starter kovka01

    (@kovka01)

    7 months ago

    Dear @wpinsider-1 and @mbrsolution ,

    Thank you for your answer.

    The “unknown” paid theme that is used on the site is Divi.
    According to statisticts more than 4.000.000 sites are using this theme, paid version, which means a lot.

    I would not like to put more and more plugins to the site, though I will consider to check the process you have shown as an alternative. (With Accept Stripe Payments.) What I really like in Simple Membership is that it is really simple. I do not need to create a product, and so on.

    Please consider to check out the “new” button working mode at Divi theme / builder. Just add it to the list of things to develop.

    Could you possibly promise that?

    Meanwhile I will continue to use the Legacy button.

    Plugin Author wp.insider

    (@wpinsider-1)

    7 months ago

    I’m aware that many users successfully use that theme alongside our plugin. However, I’m not entirely sure which specific configuration within the theme is triggering the conflict. Personally, I haven’t used that theme before, so I’m not familiar with all its customization options or potential compatibility issues. I plan to obtain a copy of the theme and dedicate some time to testing it in order to better understand the problem and try to reproduce the issue.

    Plugin Author wp.insider

    (@wpinsider-1)

    6 months, 3 weeks ago

    @kovka01 We have made some changes to the plugin that should solve this issue with the Divi theme and our Stripe subscription button conflict.

    We intend to release this version in the next few days or so (after we complete some more feature work for the plugin). However, in the meantime, I am going to give you an updated copy of the plugin so you can use it and see if this works better on your site.

    You can download an updated copy of the plugin from our site using the following link. Let me know if this makes any difference:
    https://simple-membership-plugin.com/wp-content/uploads/simple-membership.zip

    If you want to try this update, first delete the currently active copy of the plugin then upload and activate the above mentioned one. You won’t lose any data (members, payments, buttons, settings etc.) in the process so it is safe to do this.

    Plugin Author wp.insider

    (@wpinsider-1)

    6 months, 3 weeks ago

    I have now completed testing using the Divi theme and it works correctly with the new version of the plugin.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Fatal error problem with Stripe Pay Now button’ is closed to new replies.