Hi @diegomassaro ,
Thanks for providing all that additional info. Based on the logs, I see “No such payment_intent,” this means that Stripe couldn’t find a record of the payment attempt using the provided ID. This typically happens if a payment attempt never actually reached Stripe, which is why you didn’t see the funds.
From your screenshot, since the order is marked “processing,” it likely means that the orders were placed but the system is still waiting for the payment confirmation from Stripe. Without this confirmation, no funds will be transferred to your bank account. The orders will remain in “processing” until the payment is successful or the order status is manually updated. Check your Stripe configuration and Content Security Policy (CSP) settings to ensure payments can process correctly.
Refused to apply inline style because it violates the following Content Security Policy directive: “style-src ‘self’”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-1bd1ss83rhoRESXnUSD+xUzVPZzKrKQPYKkWOj5TJIc=’), or a nonce (‘nonce-…’) is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the ‘unsafe-hashes’ keyword is present.
To explain further, the CSP error in your console indicates that your website is blocking inline styles due to your current Content Security Policy settings, which are designed to improve security. This can prevent payment scripts from Stripe from running correctly, which might explain why payments aren’t being processed.
Here’s what we suggest: First, check if you have any plugins or site customizations that might be introducing inline styles. If you find any, try to move these styles to external CSS files.
If the issue persists, you may need to modify your CSP to allow Stripe’s scripts to run. You can add Stripe’s domain to the CSP directive or look into using nonces for inline styles related to payment processing.
Let me know how it goes.