simonlayfield

Thanks for the response.

We’re now trialling the premium version, and the previously mentioned cookies are found in the initial scan and added to the ‘Manage Cookies’ section.

However, when rejecting all cookies and then navigating the site these cookies are still used.

Is there a way to ensure they don’t get used when cookies are rejected in addition to them being discovered in the scan?

Thanks

Just noting that the site is behind http auth – would this affect the scan process at all?

Unfortunately when running a scan I get 0 cookies found.

I’m not able to see which URLs were scanned specifically (there’s a limit), but it would seem unlikely that this has worked properly.

Is there a way to know for sure?

Any help would be much appreciated.

Well, of course having been trying to find a way around it for the last half hour and eventually deciding to log a support topic it starts working again 2 mins later.

*shakes fist in the air*

Ach. Anyway, it appears to be able to scan again now so I’ll run it and see if any results show.

Hey @slash1andy!

Checking here as another thread has gone radio silence (https://www.ads-software.com/support/topic/solution-for-smart-button-billing-address/).

Put simply, my need is that when a user enters their Billing information in to the WooCommerce fields in the checkout, these values should pre-populate the billing fields in the form that appears when clicking ‘Debit or Credit Card’.

The fact that they don’t means the user has to enter billing information twice which as you can appreciate isn’t a great experience.

If you could offer any guidance it’d be much appreciated!

@fhaps Sorry to bother, but I was hoping to get an indication as to whether this is something that can be solved.

If I override the createOrder function passed to the buttons, I’m able to prepopulate the Billing Address fields using the payer object:

https://developer.paypal.com/docs/api/orders/v2/#definition-payer

Unfortunately it seems as though the woocommerce billing fields are serialized and sent to the paypal sdk as a fetch request body, so I’m unsure how to pass the payer details along – or if indeed the sdk is supposed to extrapolate the payer details from the billing address fields in the first place but isn’t working as intended.

If you could shed some light on this it would be much appreciated.
Thanks

So I’m facing what I assume is the same issue – I have WooCommerce billing fields that the user completes, then the smart buttons displayed as a means of payment.

When clicking ‘Debit or Credit Card’, the user is then presented with a form displaying an additional set of billing fields which, in my case at least, aren’t pre-populated according to the previous set of billing fields.

What’s strange, though, is that if I edit the shipping fields shown below the billing fields (which are empty) those are pre-populated with the values from the WooCommerce fields.

Is there a means of disabling these billing/shipping fields altogether for virtual products?