- This topic has 3 replies, 2 voices, and was last updated 9 years, 10 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Support site for Tips and Tricks HQ premium products
by
Tips and Tricks HQ Support Portal › Forums › WP eStore Forum › WP eStore Troubleshooting › adding terms and conditions checkbox as part of collect details with Stripe
Hello
The Stripe payment gateway creates its own ‘collect details’ page and I can see from testing it today that this is how the payment information is collected.
I’d like to be able to add in a checkbox requiring a purchaser to agree to T&C prior to purchasing. I’ve set up the T&C settings in WP eStore but that appears to only work with the cart (which I had as a widget in the sidebar, but set up WP eStore to go to the collect details page. I’ve since deleted the Widget.) and not with the collect details page that is set up as a default when selecting Stripe as the payment gateway
Is this a bug or is there someway I can easily add in the functionality that the WP eStore plugin offers with the Stripe Gateway in the WP Payment Gateway Bundle.
Thanks
Stella P
Hi Stella, The way it works is that customer has to agree to the terms before they can go to the collect details page. So for example, if you are using add to cart type button then the user will need to agree to the terms in the cart then they can click the checkout button which takes them to the collect details page. If it is a Buy Now type button, then they need to agree to the terms when they click the buy now button (the collect details page is shown after that).
So which type of purchase button are you using? add to cart or buy now?
I was using an add to cart button but it also appears that I could use a buy now button?
I just tried this with a buy now button, T&C showing up, thank you for this.
I fixed this as far as getting the T&C to display for Stripe – reconfigured the checkout settings page in the eStore settings. So this problem is sorted. Thanks Kym