[derwiki]

Table stakes but likely won’t be enough. If it’s a stolen card, the owner will charge back and you can’t keep the deposit. If you get too many chargebacks your payment provider will drop you. If you charge someone for damage they did that they don’t want to own up to, they will issue a chargeback. You will likely win the dispute if you can point to ToS violations but it’s a huge pain and ties up money for a few weeks.

In your example, the car rental company is doing something on the backend to determine your trustworthiness before they give you the car—you should consider a similar approach.

[chris140957]

So, I’ve had a quick look through the stripe docs and am now planning to:

- add stripe radar to identify payments made on stolen cards

- add the ability to request a security deposit, which puts a hold on the customers card

Would that cover most issues?

[derwiki]

Depends on how good Radar is these days. I’d recommend some sort of identity verification service for new accounts. Not a full background check but a few additional hurdles weed out many unsophisticated fraud attempts. Anecdotally, a friend told me that calling new signups and manually verifying them works well. At this stage this would have the bonus for you of learning more about the folks using your system.

[chris140957]

This is actually covered by stripe connect - users wanting to accept card payments through Rentify need to go through stripe’s is verification process, which involves uploading copies of your ID. Stripe also provides chargeback protection, which I have enabled, which covers any costs due to fraud

[derwiki]

That’s great to hear; that’s a huge value add if it’s effective!