Kristina

Hi @dawidadach!

The problem is that in ClientTokenGateway::_doGenerate()method there is a weird response returned from POST request. “Weird” means that there is an array returned with an empty string as a key, and an array with token as a value.

Have you tried switching to a default theme and disabling all plugins except for WooCommerce and Braintree? Then testing to see if the weird response is still returned? If not, can you please try that and let me know the results?

If that weird response still returns when the site is in that “vanilla” state of a default theme and only those 2 plugins active, then we’ll know we don’t need to look at the other plugins or theme as possibly causing the problem here.

Thanks!

Hi there!

Can you be a little more specific about what isn’t working? Replacing code probably isn’t going to help here. If you can put the code back the way it was and then explain what exactly isn’t working, I may be able to help more.

Hi there!
I see what you mean. With checkout on a single product enabled, the paypal button shows up on the single product pages. It seems like you could simply click the PayPal button to checkout, but you have to add the product to your cart first.
It’s only a single click so I think it’s still “express” – the customer doesn’t even have to go to the cart page. But I know it’s confusing and that’s where it’s not very “express”.

I suggest adding that feedback on the extension repository in GitHub.

• This reply was modified 7 years ago by Kristina.

Hi there!
You haven’t missed anything. In order for your customers to create an account on your WooCommerce store, they have to go through the checkout process. It’s still simple. They just enter a password in a field on the checkout page. It’s not an extra step or anything.
No account will be created on your store if they are redirected to PayPal from the product page.

You may want to try another PayPal option or maybe even Stripe to streamline the payment and account creation process for your customers.

Hi there!

It sounds like you’re having some trouble after the last update. I recommend testing for theme or plugin conflicts. When errors like this show up suddenly after an update, that is frequently the cause. One of the other plugins on your site (or perhaps the theme) has code that is not compatible with the latest update of WooCommerce.
Testing for a theme or plugin conflict is the quickest way to figure out if this is the problem. It only takes a few minutes.

Here is how:

1. **Try temporarily switching your theme to a WordPress default theme** like Twenty Seventeen or WooCommerce’s default theme Storefront. Place a test order. If you’re directed to the order received page and the item quantity is correct, then you know the problem is the theme and you can reach out to the theme developer for a fix. If the issue is not resolved, please proceed to the next step:
2. **Temporarily disable all your plugins except for WooCommerce.** Place a test order. If you’re directed to the order received page and the item quantity is correct, then you know one of the plugins is the problem. To figure out which one, re-enable your plugins one by one (testing in between) until you find the one causing the conflict.? You can leave it disabled or reach out to the plugin developer for a fix.

I recommend using a staging site that is an exact clone of your current site. If you can’t do that and need to test on a live site, I recommend installing this free [maintenance mode](https://www.ads-software.com/plugins/wp-maintenance-mode/) plugin so that your customers cannot see the changes that will occur in your site while you test (preferably during a low traffic time).

Hi Marcy!

USPS is only available for US based stores & Canada post is only available for Canada based stores.

WooCommerce can only read one store location. If you’re shipping from multiple locations, WooCommerce can’t factor that in. You may want to consider a drop shipping extension like this one: https://woocommerce.com/products/woocommerce-dropshipping/

• This reply was modified 7 years ago by Kristina.

Hi there!

This extension does not yet support Apple Pay or Android Pay. You can read more about that here.

I hope that helps!:)

Hi there!

I know this can be so frustrating when it seems like everything is exactly the same as on the previous server, but it’s not working! It’s hard to know what’s happening here because we can’t see exactly what is happening, but maybeour troubleshooting suggestions here will help.

I know this is obvious, but something is different about the client token on the new server than the old server. Let’s target that first.

? Check that you are not using production API credentials in the sandbox or vice-versa.
? Check that your Merchant ID, Public Key, and Private Key are correct, & that you’re connected to the right Braintree environment.
? Double-check that your connection settings are correct
? Ensure your shop currency matches the currency of your Braintree account.

I hope that helps at least a little. Let us know if you make any progress.

Hi there!

I believe another person had the as imilar question. Is that what you’re describing too?
You’re setting some custom fields on the order and those fields show up fine on the order if the customer uses Stripe or PayPal. However, if the customer uses Apple Pay, those fields do not show up on the order? Do I understand that correctly?

Hi there!

I understand you’re setting some custom fields on the order and those fields show up fine on the order if the customer uses Stripe or PayPal. However, if the customer uses Apple Pay, those fields do not show up on the order? Do I understand that correctly?

I’m not a developer, but understanding what you’re describing can help point you in the right direction.

Hi there!

Yes! It is planned for version 4.0 which should be coming out soon. I don’t have an ETA, but I know it’s being tested now.

Hi there!

Have you tried using a default theme like Twenty Seventeen? That would be the next thing I’d check.

Hi there!

Where are you seeing this warning? There shouldn’t be a php warning if your site is using php 7. I don’t see this on my test site which is using php 7.

Hi there!
This plugin uses version 2015-04-07 of the Stripe API as you can see in our documentation here: https://docs.woocommerce.com/document/stripe/#section-17.

I understand you get a message in the stripe panel that says you have an outdated API version and you could upgrade it. I’m not sure what exactly you’re trying to do, so that would be hard to answer that question.
Does the error message tell you what API version you’re using?

Hi there!

SEPA payments are not yet integrated with the WooCommerce Stripe gateway, but we are working on it for the 4.0.0 version as you can see in this git hub thread: https://github.com/woocommerce/woocommerce-gateway-stripe/issues/156.

You won’t be able to set up SEPA until the Stripe 4.0 version comes out.