#nickjw
1 messages · Page 1 of 1 (latest)
Unfortunately since Checkout is Stripe-hosted, you don't have a lot of options for handling it yourself. I would recommend using Stripe Radar in this case and then checking in with our support folks to see if there are other workarounds, as they have a workflow for getting you to card testing specialists who can help talk you through mitigation steps: https://support.stripe.com/contact
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Ok thank you. One more question... is it possible for us to set up stripe-hosted checkout pages for our standard account customers where we can send an application fee to our platform account?
Yup, that's covered in our connect docs: https://stripe.com/docs/connect/charges
i'm not familiar with setting up stripe-hosted checkout pages (since we've built our own UI on our platform). Can you link me to doc that shows how to do this?
Also is it possible to add some kind of bot prevention tool to stripe-hosted checkout pages (like reCAPTCHA)?
Checkout already has implementations for stopping automatic card testing in most cases. There isn't really a good way outside of Radar to stop manual card testing.
here's the quickstart guide for Checkout: https://stripe.com/docs/checkout/quickstart
This page shows that a server is required in order for this set up to work. Is that the case? Or can people just set up a stripe-hosted Checkout page without building any kind of server?
You need to be able to redirect to the Checkout page, so usually people use a server with a link to Checkout