#catto_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1351281993597583451
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello there, we list best practices in our docs: https://docs.stripe.com/disputes/prevention/best-practices
No, part of processing payments online is being responsible for chargebacks. Overall, we help with API questions here. If you have general questions about how fraud works with Stripe then you are going to be better off chatting with our Support team via https://support.stripe.com/contact/login
hmmm i see, but couldn't someone just bankrupt me if they can just make as many purchases as possible? lets say, like in a worst case scenario?
I mean, yes, if you had no fraud protection in place to prevent a malicious actor from making payments on your site when they shouldn't be able to. You can also submit evidence to issuers from card chargebacks to get them overturned in your favor.
But yes, fraud is absolutely a part of online payments and something you need to protect against.
hmmmm alright, i will probably have a read of that site, but in summary, stripe does a good job of prevent fraud?
with their built in radar?
Yes we have many controls in place to help prevent fraud out of the box.
But you should absolutely implement fraud practices on your end as well!
ah i see, do you know what practice could eliminate fraud 100% on my end?
That's pretty much impossible.
You will likely always have some amount of chargebacks related to fraud. That is just a part of payment processing as I mentioned above. However you can make this a very low amount by putting in place the necessary controls / preventions.
hmmm alright, thanks, i think id look for ways of limiting how much a customer can buy in a given week as well
because starting out im low in cash, so i wouldnt want to risk a really high charge back i think
i was thinking putting a cap on maximum cart size
but i realized they can just submit many orders
Yep putting caps based on IP address or other customer information is wise.
what if i put a cap based on the amount of purchases they made previously?
so that i know that an existing user who has already successfully paid for something and got it delivered
that their next purchase wouldnt be as likely to be fraud
Yeah all sorts of strategies. Having stuff in place like this will go a long way.
alright thanks for help