WooC vs. Braintree Gateway/Apple Pay Faceoff!!

  • Resolved justme69

    (@justme69)


    5 years, 11 months ago

    HELLO to all who read this. And thank you in advance for your support!! You’ll be my hero of the year if you figure out the culprit!!

    I’m on WP Version 4.8.2
    WooCommerce Version 3.2.2
    Braintree for WoodCommerce 2.6.52
    (Honestly terrified to update some of these versions currently)

    ————————-

    [Disclaimer] I’m unsure if my problems are WooC cart related OR Braintree for WooC related. Obviously both are integrated/work together. Tech support for Braintree for WooCommerce (Clayton) seems to think this is not related to their plugin but rather WooC settings.

    It’s mostly Apple Pay I’m thinking!!

    —————

    What’s happening?

    I had Apple Pay on the Cart page (for quick transaction located above “Proceed to Checkout”) and also on the Checkout page. **These Apple Pay buttons have been removed temporarily until I can figure out the issue (which I sadly think has existed for months without my knowledge – thought biz was just slow).

    I currently have three types of products: Two donations that do not require shipping and one product that does involve shipping.

    Seems I can do a credit card OR Paypal transaction for both donations (no shipping) and also the product that involves shipping… both test good.

    When I add Apple Pay into the equation, trouble arrives.

    – IF I do a transaction that does NOT involve shipping USING the Apple Pay button (doesn’t matter whether from cart page or top/bottom of checkout page), it processes successfully.

    – If I do a transaction that involves my one product with shipping, errors happen on all Apple Pay buttons regardless of whether done on cart or checkout page.

    My Woocommerce settings:
    (I only sell to and ship to USA and feel like I have those settings corrects).

    Here are screenshots of my settings on non-secure html page: https://curtseye.com/wooc.html

    What exactly are my errors?

    *Apple Pay enabled on cart and checkout*

    I figured I’d continue this part on link provided above too.

    Please let me know how else I can help YOU help ME.

    Best, Curtis

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter justme69

    (@justme69)

    Update:

    1) Braintree Gateway (Corp) isn’t showing anyt issues on their end with my account.

    2) I updated WooCommerce Version 3.2.2 and Braintree for WoodCommerce 2.6.52 to most recent versions. Peformed multiple tests using Apple Pay. The non shipping products (donations) tested perfect. The shipping products failed. Using Paypal and CC for both products with and without shipping tested perfect.

    Something is off with shipping data being shared into WC or Braintree for WC plugin at cart and/or checkout. My iOS/Apple Pay credentials are all filled in properly but most of the places I use it are Points of purchase vs. websites.

    Anyone??

    Thread Starter justme69

    (@justme69)

    Maybe someone (anyone) can suggest a better place to get support.

    I’ve kind of concluded that there are issues with how WC and Braintree for WC work together when it comes to Apple Pay and products that need shipping addresses. I feel like I’ve uncovered that the sell to and/or ship to locations affect success rates/errors on Apple Pay specific transactions.

    I also think that too many Apple Pay customers/iOS Apple Pay Wallets are not configured properly and maybe WC and other plugins can’t or don’t do things to address this reality (mostly when there’s shipping infor involved OR if there is a apt/unit # involved that might be on the same line as address OR second line of address).

    But, I’ve not had anyone from WC here or elsewhere reply with anything to look at.

    Clayton with Braintree for Woocommerce Plugin has been the only one working on potential solutions (big thumbs up).

    Thanks again for anyone that chimes in.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WooC vs. Braintree Gateway/Apple Pay Faceoff!!’ is closed to new replies.

Tags