#ditorelo
rough gate
Hi 👋 can you share an example of a request that is encountering that error?
rough gate
Gotcha, so trying to create a Setup Intent. BACS doesn't support Setup Intents:
https://stripe.com/docs/payments/payment-methods/integration-options#additional-api-bank-debits
You will need to use Checkout Sessions to save BACS details:
https://stripe.com/docs/payments/bacs-debit/save-bank-details
violet hemlock
Right. I'll pass this on to the team
stiff onyxBOT
violet hemlock
@rough gate Is that the only way?
Your documentation says the easiest, but not the only way.
This is completely different from patterns we used for SEPA and PADs, so we're a bit stumped that we need have custom implementation for this
rough gate
I believe so. The first link I provided is where we show that BACS does not support Setup Intents, and the footnote referenced there says Checkout Sessions have to be used instead.
We focus on generally available functionality in this forum, so I'm not sure if there is some other less public approach for this. Did you try contacting the email address provided in the error message you shared? That's the only other thing I can think to suggest trying.
violet hemlock
Okay - is there a general technical email we can ask it too?
rough gate
I don't think so, the integration shaped tickets that are received by email get routed to my team as well. You will want to work with someone specifically familiar with setting up BACS rather than a general technical queue, and I anticipate the best path for that is the email address in the error message since that message is specific to setting up BACS.
violet hemlock
Right - do you know why this is?
It's just so weird that this one payment method falls of the norm.
And I'm not sure the UX/Architecture of sending people to Stripe Checkout will work for us
glad lynx
👋 Stepping in for my teammate!
It looks like this is due to compliance rules, and Checkout was built to be compliant with those rules
As a next step, I recommend getting in touch with the email address mentioned in the error to get more information about how/whether it's possible to build your own custom flow that is also compliant with Bacs rules