#sahinu88_api

1 messages ¡ Page 1 of 1 (latest)

onyx vergeBOT
#

👋 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/1440003138886308011

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

brazen star
#

Hi there, looking into this now

torpid gate
#

Hi nobs,

thank you. if you need any more details, please let me know

brazen star
#

Okay, I've been investigating and seeing the inconsistencies you're describing. I was able to find in our logs that the billing portal page is using pmc_1QNCGKRwyTkLXGxpbVBgfVxb. According to your dashboard, everything for that configuration is disabled except for SEPA, as you described
https://dashboard.stripe.com/acct_1QNCFlRwyTkLXGxp/settings/payment_methods/pmc_1QNCGKRwyTkLXGxpbVBgfVxb

But according to our internal tooling, Link is enabled for that configuration. Just to double check, did you make any changes to that configuration recently?

torpid gate
#

We created for our platform (Boxbase) a second configuration, but didn't touch the default one. I think today just to test we disabled everything and enabled again the default we had at the beginning.

#

the configuration on the client side (connected account) shows that they only have SEPA enabled. but not on the customer billing portal

brazen star
#

Got it. Would it be alright if I have our bot send you a DM to convert this into a case? That way I'll be able to follow up internally to determine the cause of this inconsistency

torpid gate
#

yes that would help i think. if you need, i can provide you further context if necessary.

not sure if maybe the api version we are using could be an issue (which is not the latest)

#

i'll be off now but i am available later if i should provide any more context/information.

so thank you for the time being for your help und we'll also check what we can do on our side