#birdy247

1 messages · Page 1 of 1 (latest)

hushed hawkBOT
tough obsidian
#

Hi
Can you share more details please? do you have a requestId ?

worthy quest
#

I will get one

#

Or maybe this is better

tough obsidian
#

The payment is in a processing state, which is normal DirectDebit is an sync payment method

worthy quest
#

req_PRPkywRQN6LhC1

#

Yes, but why is it giving the customer the option?

tough obsidian
#

Option for what ?

worthy quest
#

We have never tested this, nor enabled it. Customers are using it and its caused us a major headache

#

To use direct debit

#

Its a payment element

tough obsidian
#

Ah you mean you want to disbale it and not displying it as a payment method ?

worthy quest
#

Yes

#

Until we have implemented it our end

tough obsidian
worthy quest
#

Can we do this for all connect accounts?

worthy quest
#

Its only just started appearing

tough obsidian
#

Yes, I understand that, we are working on a feature that will allow managing all payment method in a single place on the dashboard

tough obsidian
worthy quest
#

It seems stripe has suddenly opted everyone into this

#

Our customers are reporting "failed payments" where money is then coming out of the customers account... because we have never tested nor considered a BACS payment method

#

Its caused alot of friction for us and maybe lost clients

#

How can we stop this payment method appearing for any of our connected accounts

#

This is what we have in our payment_methods

#

I just spoke to a client and they say they have never enabled this, but its suddenly started showing at checkout

tough obsidian
worthy quest
#

Depsite our platform being unable to handle this!?!?

hushed hawkBOT
tough obsidian
worthy quest
#

But thas only on our account

tough obsidian
#

and for any impacted connect account

worthy quest
#

I am talking about connected accounts using our platform to manage their subscriptions

#

If you are suggesting we have no control over this, then I am very disapointed

#

If Stripe can seemingly turn on payment methods which break our integration then thats a terrible design and you are asking to upset the connected platforms

#

Surley as the connected platform, we control what payment methods can be used

#

If the client wants more control, they can use stripe directly without our integration

#

We have 400+ connected accounts. Its just not feasible for us to contact them all and say "turn off this feature"

#

Is that the only solution you have?

#

To contact them all and ask them to disable until we handle this payment method?

solemn spruce
worthy quest
#

🤷‍♂️ This is really bad for us

#

Stripe has literally laid a land mine without warning

#

This all started around end of Nov/start of Dec

#

Why is it that you never told us in advance?

solemn spruce
worthy quest
#

I will do

#

In the meantime, we need to get our developers to ensuring we can support this

#

We currently support card payments, apple pay, google pay and klarna

#

These are synchronous payment methods

#

And our integration is geared up to work this pay

solemn spruce
#

yeah that all makes sense

worthy quest
#

Now we must support DD, can you signpost me to the documentation, so we at least know how we should be handling this

solemn spruce
#

I can't really find any great docs on it unfortunately so there's not one perfect link I can think of. Technically https://stripe.com/docs/billing/subscriptions/bacs-debit#payment-success but I don't think that doc is very useful.

What I think I'd suggest is using payment_method_types as I mentioned above to explicitly control what payment methods you want the Subscriptions created on your connected accounts to use and explore in that direction rather than trying to support the other payment methods quickly.