#jona_78622
upbeat fiber
Hello 👋
delicate siren
Hi!
upbeat fiber
No, most authorizations expire in 7 days
ACSS doesn't support separate authorization (manual capture) either
https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-bank-debits
delicate siren
Is that a hard-and-fast rule or regulation? Or is there a way to make this work long-term?
I'm reasonably certain there are some solutions out there that have made this work over a longer period of time.
upbeat fiber
Not that I am aware of unfortunately, our team on discord won't know a ton about regulations that affect this OR if there are any exemptions.
Our support team can put you in touch with the right team who can help clarify
https://support.stripe.com/?contact=true
delicate siren
Looking at the documentation, it appears possible to setup_future_usage here (https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage)
And on the "Save Payment Details During Payment" page (https://stripe.com/docs/payments/save-during-payment), it looks like it's possible to, "Charge a deposit and store the details to charge the full amount later."
I don't see anything about a 7-day cap on this time period.
Am I missing something?
upbeat fiber
It doesn't place a hold (authorize) the payment method, it just helps you store it so that you can charge it later on.
You said you wanted to authorize the payment method now and capture funds later
delicate siren
Got it. In that approach, it looks like the hotel, for example, is freezing those funds in the customer's bank account.
What if we're not freezing those funds? What if we're simply getting authorization from the customer to charge them up to that agreed-upon amount at a later date (ie. 12 months later)? They can still use their funds as they see fit over that time period. And if a charge is required months later, we can charge them based upon the authorization they've provided?
upbeat fiber
If you're not freezing the funds (not placing an authorization) then you should be fine saving it and using it later on.
https://stripe.com/docs/payments/save-and-reuse
delicate siren
I'm still reading through this, and need a little more time. But, in the meantime, I just want to thank you for your help! You've been awesome!
I'll now return to reading this page and I'll follow up with you once I've read more of the documentation.
upbeat fiber
NP! 🙂 happy to help
radiant atlasBOT
delicate siren
Just to confirm:
Does this approach (https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements) allow us to do the following?
Step 1:
Customer authorizes our company to charge the customer's debit account up to $4,000 CDN at a later date.
Step 2:
12 months later, in compliance with our agreement, we can capture up to $4,000 from that customer's account.
lunar remnant
👋 stepping in for my teammate! Using SetupIntents to save a customer's payment details should allow you to create an off-session charge in the future. SetupIntents are not the same as auth+capture so the amount you're charging at a later date isn't relevant here.
Let me know if that's clear!
delicate siren
Thanks, Roadrunner!
Are there any caps on time period? Basically, can we charge the customer via preauthorized debit multiple years later (terms permitting, of course)?
And is there a cap on the value that can be captured? Could we, for example, capture $4,000CDN?
And does all of this work in Canada?
lunar remnant
No caps on time period or value, and this should work in Canada. That said, it's ultimately up to the issuing bank to determine whether the charge can go through or not. Saving payment details using a SetupIntent decreases the chances of potential declines.
delicate siren
OK. Thank you!!!
I think this may solve our challenge. You've been wonderful!!!
I'm sharing this with my colleague now to see if he has any questions for you while you're available.
Maybe I'll ask you a more open-ended question based upon the scenario.
Here's the gist:
We're building out a solution for long-term rentals that's similar to the check-in/out process at a hotel.
In a hotel, when you check-in, the guest preauthorize a charge for up to a specific value. At check-out, if the guest has an open balance (due to mini-bar purchases) the hotel is authorized to charge the guest for the balance due.
We're building out a solution like this for long-term rentals. So, at move-in, a tenant preauthorizes their manager to charge them up to a specific value. At move-out, if the tenant has an open balance (due to damage, for example), the manager can charge the preauthorized debit account up to the agreed-upon value.
Is this (https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements) the best approach to take? Or does Stripe offer another approach that would work more effectively?
lunar remnant
I think the key here is "long-term rentals". If you essentially want to place a hold on a customer's card, you'd use this flow: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
However, funds can only be held for 7 days for cards. If you want to place the hold for longer, you'd need to create a new hold during that 7 day window, then release the original hold, and so on until the end of the long-term rental. That's the only way to guarantee the funds on capture.
delicate siren
Got it.
So if we don't freeze funds, then there is no cap on the time period and value. Is that correct?
lunar remnant
That's correct but funds are not guaranteed
delicate siren
Can our company require that at least one payment method (ie. checking account) is on file with Stripe for our customer?
Alternatively, can we prevent a customer from deleting their payment method?
lunar remnant
You can require that but that logic would need to be built within your own application.
As for deleting payment methods, customers won't be able to delete payment details as long as you don't build this functionality into your custom application. If you're using the Stripe-hosted customer portal, you can disable the ability to update payment methods.
delicate siren
You've been wonderful! Thank you!!!
lunar remnant
Happy to help!
delicate siren
Have a great day!