danae39

Hey @woodypad!

Thanks for confirming that the 8.0.1 alpha worked! We’ve just released 8.0.1 with this fix.

Regarding…

The text entered in:?Display settings > Name
is not shown in the checkout, but the standard text “Pay with credit card / debit card” is always shown

I’ve created the following GH issue to handle this setting while we introduce the new functionality that would replace it. Thanks for the report! ??

Hey there ?? Quick update over here.

We have this alpha version for 8.0.1 that should fix this issue.

Please feel free to give it a go. The changes should be safe at this point but we recommend using a staging site for this since it’s an alpha version.

Hi there,

Thanks for trying to contact us via WooCommerce.com! I’m afraid I couldn’t find your support request. We’ll continue to look for it, but since you didn’t receive the confirmation email, would you please try reaching out to us again through our internal support at WooCommerce.com?

In the meantime, you mentioned that SEPA was showing up before the update. Did you use to see it in the WooCommerce Payments options, or was it on the checkout page only?

If it was on the checkout page only, would you please confirm this was being provided by WooCommerce Payments, and not an external extension like SEPA Payment Gateway for WooCommerce?

SEPA is currently a [closed beta](https://woocommerce.com/document/payments/additional-payment-methods/?quid=93545c7ca28807de42a354b0b5f1af45#introduction) in WooCommerce Payments, and I’m not seeing it enabled in your Stripe dashboard. The settings in the Stripe dashboard aren’t altered by plugin updates, so I’m trying to think what could have changed.

We’ll be around!

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?

Hello @landed!

We’d be glad to help you handle the mapping and reduce the errors.

We can provide you with better assistance when we have a good understanding of what you’re experiencing. Checking out what you’re seeing is pretty helpful, thus our request for a screenshot. I get doing this extra step might seem tedious but I trust it’d pay off.

In an attempt to skip the screenshot step, let me try to reply to what I’ve understood the issue is, and please let me know if I’m getting it wrong.

> So I am asking where does the mapping happen?
> In one case I am looking to add age group to fix the ‘Missing value [age group]’ error.

From what I’m seeing, this mapping is handled automatically by the plugin. There isn’t a setting to handle this right now, but there are a couple of requests to implement it. Adding your support there will push this feature to get implemented sooner.
Thread one
Thread two

One option to achieve this is by seeing if extending the plugin via customizations is feasible. A developer would be of help with that, but the plugin’s source code is available for anyone to check out.

In case you’d rather have a working solution, if this is for products, looks like our plugin Google Product Feed has this feature you’re looking for in it.

Please let us know if these aren’t related to the problem you’re getting. We’ll be glad to assist you further. If they are, it’d be great if you showed your support to the ideas I linked before to get this implemented. We can also pass the request to the developers in that case.

Hoping this is of help! We’ll be around.

• This reply was modified 3 years, 7 months ago by danae39.

Great! Our pleasure, @richsadams. Thankss

Glad things are fine now! My pleasure, Tom. Thanks again for reporting the issue (:

Hey guys! Sorry for the issue, and big thanks for reporting it.

We’ve just released 7.4.3, things should be fine there. Mind giving it a try? You might need to clear the browser’s cache on the first load. We’ll be around!

Danae

Big thanks for letting us know, Tom!

We’ve just released 7.4.3. Please give it a try, things should be fine there.

Hi Tom,

Thanks for reaching out!

This should be solved in our latest release, 7.4.2. Would you please give it a try and let us know how it went? We’ll be around.

Danae

Hey! Thanks for answering back!

I haven’t tried just yet but I’ll do and update the thread here.

Thanks again, and wish you a nice day!

Awesome! Thank you ??