• Resolved alex_stoiu

    (@alex_stoiu)


    Hello,

    I am using Woocommerce with Stripe as the payment gateway.

    After a user purchases a product on my website, Stripe sends them an email receipt, however, since this receipt cannot be translated into my website language, I have made the necessary changes to my Stripe account, in order to stop it from being sent.

    The receipt, however, is still being sent to the customers.

    I have noticed that in the Stripe Dashboard – Emails section, next to the checkbox for enabling/disabling the Successful Payments email, there is a tooltip that states:

    “This setting is ignored when you create a payment in the API and provide the receipt_email parameter.”

    After chatting with Stripe support, here is what they said:

    “Just as a little recap, after checking with a specialist, it looks like indeed this is an expected behaviour, Woocommerce is creating the receipt field on the payment call, this means that, even though we tried to remove it, it can only be changed on their end, so you may need to reach them and ask them how to remove it, once is completed you should be all set.”

    Can you please help me with this? I would really like to have these emails stopped from being sent to my customers.

    Thanks a lot!

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

Viewing 11 replies - 1 through 11 (of 11 total)
  • Marcin

    (@robobot3000)

    Hi @alex_stoiu!

    The receipts are sent only when apply_filters( 'wc_stripe_send_stripe_receipt', false ) returns true. It means that you are using a filter such as add_filter( 'wc_stripe_send_stripe_receipt', '__return_true' ) or similar somewhere on your site. Please search the code snippets and plugins on your site and remove the filter.

    Alternatively, if you cannot find the filter, you could add one such as this: add_filter( 'wc_stripe_send_stripe_receipt', '__return_false', 999 ) which should override the existing value.

    Hope this helps!

    Plugin Support nicw.a11n

    (@nicw)

    Hi @alex_stoiu

    I can confirm what @marcin has correctly added here, that the receipt email field is only added if you are overriding the plugin settings with a code snippet.

    His advice regarding the filter is quite correct.

    Thread Starter alex_stoiu

    (@alex_stoiu)

    Hi and thank you both for your replies.

    Unfortunately I cannot find any snippets overriding the plugin settings.

    I have added the filter you provided using the Code Snippets plugin at first, and then in the theme’s functions.php file, but the email receipts are still being sent.

    Your further assistance is greatly appreciated.

    Thank you!

    Hey @alex_stoiu,

    That’s odd. By default, that filter prevents invoices from being sent by Stripe as its default is “false”, as @marcin mentioned. So, there should be something external modifying that filter.

    Do you have any other plugin that could be integrating somehow with WooCommerce Stripe Payment Gateway?

    Doing a conflict test would be a good way to test that. You can do that by deactivating all other non-related plugins and using a default WordPress theme like Twentytwentyone or Storefront. We suggest doing that on a testing/staging site to not interfere with your live one.

    Would you please give that a go and let us know how it goes?

    Plugin Support Saravanan S, a11n

    (@simplysaru)

    Hi @alex_stoiu

    If you need a guidance on conflict test, you can refer the instructions here.

    Do keep us posted on how this troubleshooting works out for you.

    Thread Starter alex_stoiu

    (@alex_stoiu)

    Hi, thank you very much for your replies.

    Unfortunately I am not able to test this flow while my theme and theme related plugins are deactivated. I am using a Paywall plugin which only works with the Jnews theme. I have kept the theme active and deactivated all plugins except the Jnews related ones (plus Woocommerce) and the receipt is still being sent. I’m guessing that I should take this discussion up with the Jnews team.

    I still, however, have another question. On the Stripe checkout page, the placeholders for the inputs containing the credit card information are showing up in the language of the browser. For example, if I have Mozilla in English and Chrome in Romanian, the placeholders will show up in either English or Romanian, respectively. Is there a way to have these placeholders translated into Romanian regardless of the browser language?

    I’ve also contacted Stripe support about this and they sent me to Woocommerce support again. Here was their answer:

    “The best way to setup the checkout language without coding would be through WooCommerce settings, in this case, I suggest you to contact WooCommerce support so they can guide you on this. They will provide you with more accurate info as the checkout was integrated and linked to your Stripe account and website”

    Anxiously waiting for your replies.

    Million thanks!

    • This reply was modified 3 years, 3 months ago by alex_stoiu.
    Plugin Support dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hi @alex_stoiu

    I hope you do find the solution as to why the receipt is being generated if you have even added Marcin’s second snippet add_filter( 'wc_stripe_send_stripe_receipt', '__return_false', 999 ) – to confirm, you are using WooCommerce Stripe Gateway by WooCommerce version 5.4.0?

    Is there a way to have these placeholders translated into Romanian regardless of the browser language?

    Yes, it is possible to do this using custom code – https://docs.woocommerce.com/document/stripe/#how-can-i-translate-the-placeholders-text-inside-the-credit-card-form

    Thanks,

    Thread Starter alex_stoiu

    (@alex_stoiu)

    I am using Woocommerce 5.6.0 with Stripe as the payment gateway (which was also integrated when installing Jnews and its related plugin Jnews Paywall). I am not using the Woocommerce Stripe Gateway plugin. If you have any other ideas that I should try further, please let me know.

    Regarding the translation of the placeholders inside the credit card form, I’ve added the custom code inside my Code Snippets plugin (adding it to my theme’s functions.php file broke the website), but to no avail. Once I change the browser language back to English, the placeholders show up in English as well.

    Thank you!

    Plugin Support Sol J. a11n

    (@solstudioim)

    Hi @alex_stoiu

    I am using Woocommerce 5.6.0 with Stripe as the payment gateway (which was also integrated when installing Jnews and its related plugin Jnews Paywall). I am not using the Woocommerce Stripe Gateway plugin. If you have any other ideas that I should try further, please let me know.

    As you’re not using Woocommerce Stripe Gateway plugin, I’d suggest to continue the talk with the Jnews Paywall team as you said before:

    I’m guessing that I should take this discussion up with the Jnews team.

    On your other statement:

    Regarding the translation of the placeholders inside the credit card form, I’ve added the custom code inside my Code Snippets plugin (adding it to my theme’s functions.php file broke the website), but to no avail. Once I change the browser language back to English, the placeholders show up in English as well.

    I am not too sure about how browsers behave to the checkout page. Also we can’t really provide any troubleshooting related to custom snippets.

    Therefore, my hands are pretty tied.

    If you need help with custom snippets, I highly recommend contacting one of the services on our customizations page: https://woocommerce.com/customizations/

    I hope that helps!

    Thread Starter alex_stoiu

    (@alex_stoiu)

    Thank you all very much for your help and support!

    Plugin Support Stuart Duff – a11n

    (@stuartduff)

    Automattic Happiness Engineer

    Hey @alex_stoiu,

    We’re happy we could help. I’m going to mark this as resolved – if you have any further questions, you can reopen it again if you need be.`

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Stripe email receipt’ is closed to new replies.