Nik McLaughlin

Hey there,

It’s been a long time since we heard from you, so I’m going to mark this topic as resolved. I hope Steve’s suggestions above have been helpful!

If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.

Thanks,
Nik
SkyVerge

Hi Felicia ( @feliebaby ),

Nik here from SkyVerge Support, thanks for getting in touch!

First I’d like to apologize for our delay in getting back to you here, especially for a critical payment issue such as this!

Based on the issue that you’re seeing, I’d like to see what the communication between our plugin and Braintree looks like when this error is occurring. We can do this by enabling debug logging for the gateway. In order to avoid sharing sensitive information publicly, could you please raise a support request via our support form mentioning this thread so we can follow up and examine the logs from your site there?

All the best,
Nik
SkyVerge

Hi Ali!

Following up on this, I heard back from our engineers today and they are looking to have this resolved within the next week or so.

Could you let me know if you have any other questions in the meantime, or if you had any luck with those fraud rules?

Cheers,
Nik

Hi Ali ( @develooperr ),

Thanks for checking back in on this!

I haven’t heard any updates on this just yet, so let me check in with a few of the folks involved to see where things stand.

Could you let me know if you were able to get any of those basic fraud rules enabled since we last spoke and if you’ve seen any change in behavior from the gateway based on that?

Talk soon!

Nik
SkyVerge

Hi there!

Following up here to let you know that we’ve looked into this further and unfortunately it looks like our code doesn’t currently allow for the Apple Pay button to be relocated cleanly. Unfortunately these buttons are rendered as part of a protected class that we would not be able to relocate with a simple snippet, and as such would require some more in-depth development work to free this up.

I’ve logged a request to improve this functionality for a potential future release. This is passed along to our product team to review, and while I can’t say if or when this might make it on our roadmap, I wanted you to know we appreciate you bringing up this opportunity to improve our gateway here!

In the meantime, you may be able to do some limited re-ordering of these cart buttons with some additional CSS. This will depend largely on your site’s theme and other stylings, and I’m afraid we aren’t able to assist with that kind of customization directly, though in my research the flex-direction property seemed the most promising, which you can find documented here.

I’m sorry that I don’t have better news for you on this, though I hope it’s helpful to know where things stand! I’ll go ahead and mark this thread as resolved, but feel free to reach out with a followup if you have any other questions, we’re happy to help!

All the best,
Nik

Hello again!

I spoke with our engineers and I’m afraid we don’t currently have a hook in place that would allow the positioning of this button to be easily changed by code.

However, we’d like to put together a short snippet for this as we think it’s something that could be widely useful to anyone with an Apple Pay implementation. We’ll need a bit more time to get this together, though I wanted you to know it’s being worked on!

I expect to have an update for you on this by the end of the week, so I’ll be sure to follow up then. Feel free to let me know if you have any other questions or concerns in the meantime!

Cheers,
Nik

Hi there @zsaqadra !

Thanks for getting in touch about Apple Pay on our Braintree for WooCommerce plugin, and for sharing the screenshot there as well!

This looks like the expected placement for the Apple Pay cart button by default, although I can see how moving it down below the “Proceed to Checkout” button might provide a more natural flow to the page, especially when the Paypal Checkout button is there as well.

While we don’t have a built-in way to relocate this button, this may be achievable with some additional customization. I should note that such customization wouldn’t be covered under the terms of our support policy, though I’m happy to provide some recommendations to get you going in the right direction!

I’ve reached out to our engineers for insight on our options here and will let you know what I hear back.

All the best,
Nik
SkyVerge

Hi Teresa ( @thardy99 ),

Gotcha, thanks for confirming this for me! I can see how that would be expected given that most postal/shipping systems will allow you to use either version, so it’s helpful to have that cleared up.

I’m going to mark this thread as “resolved” now, but if you run into any other questions or issues, please feel free to create a follow up — we’re happy to help out ??

Cheers!
Nik

Hey there @thardy99 ,

Nik here, thanks for reaching out about our Braintree for WooCommerce plugin!

Great find! I’m glad to hear you were able to sort out this issue with the WooCommerce taxes!

It sounds like this was a mismatch between the ZIP used in the tax rules and that listed for the shop address (i.e. on the WooCommerce > Settings > General page). Is that right? Or was there a different address that you had to update?

I’d love to clarify this for my own understanding as well as anyone else who is facing a similar issue ??

Thanks again!
Nik
SkyVerge

Hey Jason ( @galapogos01 ),

Glad to hear it! Thanks for confirming!

I’m going to mark this thread as resolved, but if anyone here runs into any other questions or issues, please feel free to create a follow up — we’re happy to help out ??

Cheers!

Nik

Hi All! ( @joldeski @galapogos01 @hrvojea )

Writing back to let you know that we just released v2.6.0 of the plugin which includes a fix for this issue.

Thanks so much for bringing this to our attention!

Would you let me know if you’re able to update to the latest release and confirm that this has resolved the errors you were seeing on your site?

Cheers!

Nik
SkyVerge

Hi there!

@joldeski , thanks for confirming the snippet is working for you in the meantime, glad to hear it!

@galapogos01 , thanks for the additional details here! Our developers are working on this at the moment and while I don’t have an exact release date, I can see the patch is now under review. As long as no serious issue is found during testing, we’ll hopefully have a new fix out soon!.

Thanks again for your patience!

Nik
SkyVerge

Hi all! ( @joldeski @galapogos01 @hrvojea )

Quick update here: we’ve been able to replicate this issue on our end and our engineers are working on a solution. For context, this appears to be an incompatibility issue that comes up when running Braintree alongside other payment gateways which is causing these errors when our plugin checks to see if Apple Pay should be initialized.

While we are working on a more permanent solution, you should be able to prevent these errors in the meantime by disabling Braintree’s Apple Pay initialization using the following filter:

add_filter( 'wc_payment_gateway_braintree_activate_apple_pay', '__return_false', 11, 1 );

I should note that a customization like this is not covered under our support policy, so we won’t be able to help with implementation directly. However, if you aren’t sure how to add custom code to your site, we do have this blog article that walks through some popular options.

If you aren’t able to implement that filter, or don’t want to disable Apple Pay on your site, the plugin should continue functioning despite the errors in the meantime and we’ll be sure to update here when we have a fix.

Cheers,
Nik
SkyVerge

Hey @develooperr

I’ve added this issue to our tracker for our team to investigate. 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.

In the meantime, I noticed that your Braintree rep also mentioned enabling some of their basic fraud tools as part of the Card Verification features intended use. Could you let me know if you’ve been able to enable any of these tools and if you’ve seen any change in behavior from the gateway based on that?

Best,
Nik

Hey there,

Thanks @joldeski for letting me know!

It would also help us to know which version folks are reverting back to in order to prevent these error messages.

Jason ( @galapogos01 ), I know you had mentioned downgrading specifically before. Could you let me know which version of the plugin you’ve downgraded to?

Cheers,
Nik