#smartkiparis
lime pier
edgy compass
So you can only create "locks" (AKA card authorizations) for up to 7 days. If you're using this for security deposits, you should really be actually taking the money, as opposed to creating an authorization. The reason being that the client could just close their account if they break your equipment and you'd have no way of charging them again.
To that end, you should use Stripe Connect: https://stripe.com/docs/connect/explore-connect-guide
Each client can have a Stripe account that holds their security deposit, then you (the platform) can choose how much money to take and how much money to give back.
hexed crow
And what is an optimal way to take money in that case? Could we manually confirm payments? There are no clients that are using 3DSecure, so no authorisation is needed for them
edgy compass
3DS is available for all card holders, so they should be able to though it may or may not be required. Either way, you can create payments using any of the Stripe payment products. Checkout is a good option for getting started quickly, but this resource has the "main/default" ways of accepting payments: https://stripe.com/docs/connect/creating-a-payments-page
hexed crow
Can we create and confirm payments fully on a server- side?
edgy compass
No. You have to accept payment credentials (card number, CVV/CVC, name, exp. date, etc.) on the client side. Those credentials should not touch your server
hexed crow
Ok, thanks