CSC-field suddenly disappeared

Error demonstration:
page: https://podolskacoaching.com/checkout-en/
Try to change country.

User data with saved card:
https://podolskacoaching.com/wp-login.php
[email protected]
123456

Hi @dimafirst,

Thanks for getting in touch about our Braintree for WooCommerce plugin! I’m happy to help out here ??

The screenshots and details you sent were a lot of help, thanks for that! I wasn’t able to replicate the issue of the CSC field disappearing for the countries I tried.

Could you please let me know which country you selected when the CSC-field disappeared?

Thanks!
Christine

Hi @christineskyverge
Thanks for your reply!

This error appears with any Country change, when card saved.

For example, i’m add another card to account (screenshot1) and when i change Country to Canada – CSC field is gone (screenshot2).
1) https://prnt.sc/u90ado
2) https://prnt.sc/u90b1g

This also happens with Twenty Twenty theme.
I don’t see any errors in console.

Hope for your help.

Hi @dimafirst

Thanks so much for the extra detail, it’s a big help!

I tested this again on your site for saved cards and was able to replicate the CSC field not displaying.

I’ll go ahead and loop our engineering team in on this and we’ll be back in touch once we take a closer look at what’s going on. Thanks for your patience here!

To help move this along, could you please Debug Mode for the Braintree plugin? You can do that by following these steps:

1. Go to WooCommerce > Settings > Payments
2. Click on Braintree Credit Card, then for Debug Mode, select Save to Log

In the meantime, please feel free to reply to this thread if you run into further questions or updates.

Thanks!
Christine

• This reply was modified 4 years, 2 months ago by Christine, SkyVerge Support.
• This reply was modified 4 years, 2 months ago by Christine, SkyVerge Support.

Hi @christineskyverge

Did you talk about this setting? :
https://prnt.sc/uavio7
Okay. I will do this.

But, as I understand, field-error we see before payments processing start.

I will wait for more information, what else we can do.

Hey @dimafirst,

Tamara here, stepping in for Christine. I apologize for the delay in getting back to you. I’m happy to help here ??

I’ve been performing some tests locally and I’m having a hard time replicating the issue consistently. I’m checking in with some of my colleagues to see if they can replicate the issue so that we can file a report for the developers to look into this and address the issue. I’ll circle back as soon as I have some news.

Could I help you with any other questions in the meantime?

Thanks,
Tamara

Hi @tamarazuk!
Thanks for your reply.
Problem still exists.
Did you succeed replicate issue?

I will patiently wait for more information:)

Hey @dimafirst,

Thanks so much for your patience! I was able to replicate the issue after some additional tests.

Thank you so much for reporting this to us!

I’ve added this to our issue tracker for the developers to get this patched up. While I don’t have an estimated time for resolution right now, please know that our team is now aware of the issue and will work to incorporate a fix into the plugin as soon as they can.

Again, thanks so much for the report! Is there anything else I can help out with?

Cheers,
Tamara

Hi @tamarazuk ??

Ok, we’ll wait for update.

I think, it’s early “mark as resolved” this topic ??

I have no more questions, let`s wait fix into the plugin.

Thank you for your help!

• This reply was modified 4 years, 2 months ago by Dima First.