#matih_api
1 messages · Page 1 of 1 (latest)
👋 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/1419614829026476112
📝 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.
- matih_api, 3 days ago, 23 messages
When I check the payment_methods belonging to the connected account acct_1S2n*******dd4 i see this:
👋 Happy to help!
You are making a Direct Charge on a Standard Connected Account acct_1S2n57A8af6LJdd4
The Swish PaymentMethod needs to be enabled in their Stripe Account
I just checked their account and I see it's not enabled
You should reach out to them and ask them to enabled (as they are standard Account)
Because Swish is still in private beta, they need to reach out to Stripe Support and get onboarded in order to get access to Swish payments
https://docs.stripe.com/payments/swish
(Like you did for your platform account)
so this action has to happen for every onboarded account??
how is this not an integral part of the KYC-process?
all our swedish connected accounts need to have this enabled after they've completed the onboarding process. on our backend, we check whether the connected account is Swedish or not, before adding "swish" to payment_methods.
@spiral folio considering the amount of clients we're already in talks with, and the additional amount we're going to take on, it's not feasible to manually onboard them one at a time
Yeah I understand that, but this feature is still in private mode, probably it's worth to reach out to Stripe Support and see if they can onbaord all your connected Accounts at once.
Just I want to confirm one thing, when you create your connected Account, are you requesting swish_payments capability ?
i don't recognize that key, no
when i tried this previously, it would return an error. with the platform having swish enabled, will i be able to add this capability when creating the AccountLink?
you'd request it when creating the account, or va the Dashboard for existing accounts: https://docs.stripe.com/connect/payment-methods
yes, i know this. but that was not my question 🙂
But the gate for the private access isn't applied correctly to your platform for Connect access so you need to speak to support about that
What was your question then?
ok? what is the question we need to raise in order to have it correctly applied?
my question was:
with the platform having swish enabled, will i be able to add this capability when creating the AccountLink?
That you want to enable Swish payments for your Connect platform doing direct charges
I answered that: no, not the Account Link. You specify the capabilities you want on Account creation: https://docs.stripe.com/connect/account-capabilities#creating
aha, i see
but according to your colleague it seems that the platform already is setup for this? the issue seems to be the connected accounts?
and looking at https://dashboard.stripe.com/acct_1RgjNpAQJySqIEX2/connect/accounts/acct_1S2n57A8af6LJdd4/settings/payment_methods it seems that Swish is "ON"
I think they misspoke. The account does not have access to the Swish beta for Connect direct charges
according to emails i've seen from stripe customer support swish beta is enabled. what am i missing here?
i managed to run this on our staging servers (with test keys)
Screenshot is not helpful without a corresponding object ID
It's enabled on acct_1RgjNpAQJySqIEX2 for non-Connect payments
ok, that seems to be the account id of the platform. correct?
Yes
and it needs to be enabled through all other connected accounts, and for this to be able to happen we need to continue discussions with stripe support?
You can do non-Connect, direct Swish payments on that account. But the gate is not applied correctly to give Swish access for the Connect payments like the example you shred
It doesn't need to be applied on each connected account, just applied to acct_1RgjNpAQJySqIEX2 for Connect
let me explain the setup quickly:
- a swedish company (personal trainer) signs up with our platform
- they complete the onboarding with stripe, they're now a connected account
- an athlete signs up to the platform
- they see a training session which they're interested in paying for, they click "pay now" and we will create a customer in stripe
- they should now be able to pay with swish
I know the setup, I'm looking at the request that failed and the two account IDs associated with that request
Won't work for two reasons I've already outlined:
- Your connected accounts don't have the Swish capability
- Your platform does not have private access to do Swish direct charge (Connect) payments
- i understand the first bullet, and my question is: will this be solved by setting https://docs.stripe.com/connect/account-capabilities#creating ?
- i don't understand the second bullet, you previously stated:
It's enabled on acct_1RgjNpAQJySqIEX2 for non-Connect payments
does this mean that we need to further discuss this issue with Stripe Customer Support?
- Yes
- Yes
ok, thank you.
if i try to set the capabilities now, would i get an error message from stripe api? or should i wait until Stripe Customer Support has reverted with a positive reply before implementing anything extra?
Your platform does not have private access to do Swish direct charge (Connect) payments
or is this something you would be able to change?
I'm not sure if it would error, you can try
Afraid not as there's additional considerations for Connect
thank you for your help. i will forward this to management team and they'll continue discussions with your support
quick question; are there any platforms currently active on stripe with swish-enabled connected accounts?
(do not need the names, only yes/no)
I don't know I'm afraid. It's all still in beta obviously
i see. how long has stripe implementation existed in beta?
Sometime in 2024 it launched I think
req_Y5oHf9utiowZCU could you please check this request?
why was it successful, although the test connected account was not created with the swish capability?
Because it's in test mode and capabilities are largely discarded/ignored there:
Sandboxes and test mode might not enforce some capabilities. In certain cases, they can allow an account to perform capability-dependent actions even when the associated capability’s status isn’t active.
oh, i see. i think that's the reason for a large part of the confusion on my side
Yeah it catches people out for sure and one of the few test/live differences
again, thank you for your time and patience 🙂
No problem, glad I could help!
you can't check any records?
Not something we'd disclose or share I'm afraid
the reason i'm asking is; if you havent onboarded any platforms in this matter, perhaps there's a (political) reason for why. and it would save us a lot of time if we'd know whether this is a futile request or not
It's supported, as I've explained and is documented
thank you again