#sina
1 messages · Page 1 of 1 (latest)
Unfortunately not, it will be best to listen to the webhook events events and make the API call once the transfer is created
OK, thanks. I also have a question about ACSS debits since the documentation is not really clear on what parameters we should pass for our use case.
We're a retail POS for gyms and similar fitness studios. There's going to be a front-desk person presenting the ACSS mandate to the client and then marking in the system that they agree to it.
For the Payment Intent, what should the values be for 'confirm', 'off_session', 'mandate', 'mandate_data' for our use case
https://stripe.com/docs/payments/acss-debit/accept-a-payment
This one but it's probably the most vague article I have found in the stripe documentation
Thank you. And can you tell me a bit more about your use case here? Are your front desk people putting in the other details or did the customer put in their details themselves beforehand or something?
So the customer would have a profile in the CRM already with their name, address, email.
This is how our payment form would look for the front desk person to put in the rest:
My hope is that the staff member can submit this form, and then the 3 day grace period passes, and the customer is debited and sent the mandate confirmation from Stripe via email.
Then they can save their bank account on file to bill them their membership auto-payments monthly or weekly
Thanks for the info. I am unsure how having someone else input the mandate might affect the settings you need
I will consult a colleague on this and get back to you with what I can find
Appreciate it
hey! overall I don't think this is specifically how we designed this product, it's all intended to be used such that the end-customer interacts directly with your web page. You can at least technically build this using the API. I'm only an engineer so I can't really tell you how supportable that method of integration would be in terms of our policies if it's not the end-customer at the frontend.
For the Payment Intent, what should the values be for 'confirm', 'off_session', 'mandate', 'mandate_data' for our use case
Hard to answer that without knowing if you're planning to use our frontend components likeconfirmAcssDebitPaymentor not, so it depends how closely you're following https://stripe.com/docs/payments/acss-debit/accept-a-payment .
On your side you might have things to think about in terms of data protection or local laws with your employees handling bank account numbers of customers but that's something you'd need your own advice for.
Overall maybe a better option here is that you have a QR code at your desk, and the the customer scans that and visits your site to pay? It removes a lot of complication.
Thanks. I will have our merchant team look into all the laws and policies, for now I would like to see if it's technically feasible to implement it in this way such that the transaction succeeds. We have several payment partners in Canada and already offer ACH with them there in this manner, though I understand there is a difference between EFT/ACH and ACSS (not sure if Stripe supports the former in Canada)
We're using our own payment form (screenshotted above)