Stripe - Payments going missing (new Cache responsible?)

#1

Pretty serious bug - it’s now the second time in 2 weeks that a customer paid and it shows up in the Stripe-IPN log and stripe-api.log - but is missing from gateway-core-ipn.log and s2-http-api-debug log.

Relevant strip-ipn log attached - they are very log - seems Stripe notices something is going wrong? Paypal so far has been fine.debug_logs.zip (43.1 KB)

I should have taken the effort to upload the data in the first place already - but thought it may be a once off glitch. It isn’t this is more serious.

I can provide my caching options should it be related:
I have the following notice:
s2Member CSS/JS Asset Health: Review Suggested
Frontend CSS/JavaScript asset-load health has remained substantially degraded across the latest six hours without returning to normal. Delivery may currently be improving or may still be working through fallback. This is a suggestion to review the configuration, not an emergency.• WP Loader CSS fallback is unavailable while the preferred CSS delivery is still working.
• WP Loader JS fallback is unavailable while the preferred JS delivery is still working.

S2memberonlyDynamic Loader active,
beta generate static CSS
Beta Minify CSS
Beta generate and use static CSS delivery
Load Javascript text files with static files (as I use a translation plugin)
Minify static JS
Combine each type
wait before checking - 4 seconds

#2

User report of how it happened:
If it helps you debug, these were the steps I made

- I filled in the new user data (including the password)

- I selected CC payment and put in my credit card data

- As soon as I submitted, I received the notification from the card issuer to do the confirmation of the payment on my phone. Before I could do that, the registration form immediately gave an error saying something went wrong with the payment. I confirmed the payment on the phone (after the before mentioned error) and the page reloaded again by itself with the error “Password can’t be empty”.

…
…

the one thing for sure is - it doesn’t happen every time - there were many succesful payments too. So I guess a caching problem is likely? I deactivated all the new options for now on my websites until this is solved.