#the-mortiest-morty_api

1 messages · Page 1 of 1 (latest)

west mossBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1438158622663118938

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

burnt lark
#

@fallen vigil Looping you back in, sorry, previous thread got closed before I could reply.

silver compass
#

👋 Hey, taking over here, just taking a look to see if there's any other way to set this on the account

silver compass
#

From what I've found internally, you may actually be able to set the field as described previously, even though this doesn't appear to be a field in the docs, so it would be worth trying this

burnt lark
#

I already tried it, using the stripe-ruby gem. That gives me: "Received unknown parameter: settings[sepa_debit_payments]. Did you mean bacs_debit_payments?"

So no, doesn't seem to work 😬 Or is it possible I would get a different result if I send a request directly, not using the gem?

silver compass
#

Yes, if you try directly with curl or similar, it may work

burnt lark
#

Hmmm... I might try it, if I get desperate, but it wouldn't be ideal 😄
Can you tell me whether there should be a way to set it through our dashboard? Or is that only possible, if we give the connected accounts dashboard access as well?

west mossBOT
silver compass
#

I believe you should be able to set this from the dashboard by navigating to your payment settings, selecting SEPA Direct Debit, and clicking the configure button

burnt lark
#

The payment settings of our platform account or of the connected account?

#

Are you talking about this page?

Screenshot_2025-11-12_at_15.07.26.png
proven hill
#

hey there, just stepping in for my teammate who had to step away

#

From what we're reading, it looks like for connect scenarios where this would apply (direct charges or destination with on behalf of), you need to set this on the connected account via the API

proven hill
burnt lark
#

I think I found how to set it on our platform account. However, does that transfer to connected accounts?

burnt lark
proven hill
#

Ah ok, you're not specifying a connected account using the stripe-account header here

#

Can you try adding that?

#

For you platforms own settings, that needs to be via Dashboard

burnt lark
#

This is the request to create the account in the first place, so I don't have the ID yet. But let me try, if I can update an existing account like that 👍

proven hill
#

I'm not sure if its possible to set this during creation

#

Can you try updating this for an existing account thats already enabled for sepa?

burnt lark
#

That works!!! 🙏 Thank you very much!

It also works, without setting the stripe-account header, apparently... Using the update action on the connected account directly was enough. The request was req_vnc7BOX66j2boQ

#

Just curious, is it an oversight that this field is not documented for the "Update Account" action, or is this hidden on purpose? 😄

#

Again, thank you! This is a relieve 😌

proven hill
#

I'm not sure, but going to raise that feedback internally to determine if it should be 🙂

#

Glad that worked for you!