#nickdnk_account-capabilities-requests
untold boneBOT
👋 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/1486804670746988585
📝 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.
- nickdnk_api, 1 day ago, 46 messages
- nick_connect-pmc, 3 days ago, 87 messages
autumn dew
Hmmmm.... 🤔
I see the Connected Account acct_1BoB66Lj11Ytqxjb is connected to two separate Connected Applications at different dates. Each corresponds to the same Platform account but they are different Client Applications.
That being said, you are using the Test mode account key and that is corresponding to the Client Application connected in Test mode...
prisma orbit
Hmmmm.... 🤔
I see the Connected Account `acct_1BoB66Lj11Ytqxjb` is connected ...
I only have one applicaiton, so maybe you're seeing live and test?
This is our "test connected account" which has probably been connected in live mode too, but we don't use that for obvious reasons
That would be two different client application IDs
Is it because Revolut is a "live mode only" merchant?
(reading the error description could imply that)
autumn dew
Yes I realize they are the same application but the way the data is represented suggests you connected to this Standard account twice. Once in Test mode and once in Live mode.
- Test mode Connection occurred at 2024-12-12
- Live mode Connection occurred at 2024-12-09
I'm still digging, just pointing out things that seem odd as I go
prisma orbit
Yes, that matches what I just said, right?
We don't use the live mode connection for anything, but it is connected on there, it's just disabled because it's not a real business - by disabled I mean live payments are not enabled
That shouldn't affect what I'm doing here though because I'm using a test secret key as you correctly confirmed
We don't need the live connection, so if that causes issues for whatever reason, I can remove it. Looking at the dates I might have even done it by mistake. It's just a matter of which environment (our staging runs on test mode) I'd have connected our test account (by that I mean our own internal test account for our service) to stripe via.
It actually looks like our test account is not even disabled in live mode anymore. It was at one point. Not sure what happened on Stripe's end. I did complain about it because I was being "threatened" that the account would be closed unless I verified it (which I can't -the business is fake and uses only test mode), so maybe that's why.
autumn dew
Ah, I think this is a case of a terrible API error message that has nothing to do with the real issue. This is especially common with permissions issues
The Restricted Key used to make the API request does not have the account.write permission.
autumn dew
I will flag internally because we have a project around improving confusing error messages
autumn dew
Ugh our logs are so much harder to read right now. I'm trying to find the first log lines for this permissions error
prisma orbit
This is what I have. Don't know if it helps you.
The account ID in the request_log_url value is the platform though, but I'm guessing that's for debugging
autumn dew
I can get all that from the request ID but thanks
prisma orbit
Alright
untold boneBOT
stuck sable
Hi there, taking over for @autumn dew as they had to step away. It'll take a moment to get caught up on the thread, appreciate your patience!
prisma orbit
No problem
prisma orbit
I have a follow-up question related to this. If users do not have access to modifying their PMC (because I set it to "connected accounts cannot modify it"), then how would it work when it "requires action" like indicated here? This tooltip implies that any user with dashboard access (all my accounts are standard connect) must do it on their own, but if I don't allow modifying the PMC, how would they do it?
Tooltip implies that using the API to activate it for a standard connect account would not work, but I'm unsure if that's what it means, or if it just means that users must do something additional on the dashboard to fully activate the payment method after I make the API call (or potentially before?).
stuck sable
Sorry for the delay here, I agree that message is unclear. I will look into it, and I'm still looking into the original question. My understanding is that the theory that it's a permissions issue is not true, so will keep investigating the logs
prisma orbit
Alright
Is this a "I'll work on it for an hour" or "i will have to follow up via email" situation? I'm not sure how to proceed building this when I can't test it
stuck sable
If you're able to stay online we can keep this thread open for the investigation. If you need to step away we can convert this into a case where you get email updates. We'll do our best to investigate this in a timely manner either way
prisma orbit
Alright, I'm in discord the next like 6-7 hours probably
stuck sable
Do you know if acct_1BoB66Lj11Ytqxjb is a Sandbox or an account using the legacy test mode? There may be an issue if it's the latter. One thing to try is using a a Live API key to see if it works (which would be pretty unintuitive, but just something to try). Or you can try to make a Sandbox and use the test API key with that request
prisma orbit
Yea it's test legacy
I have never used sandboxes, I'm not sure how they would integrate into our current staging env
I will look into it in about an hour
autumn dew
Hey, I'm back. 👋
Question: Has this specific situation, requesting capabilities on a Standard Account with a Test mode Restricted Key worked in the past?
With respect to the Dashboard message about Payment Methods, my understanding is that the Platform can configure the PMC applied to charges it creates on the Connected Account but, because Standard Accounts are full, stand-alone Stripe Accounts, the Connected Account also needs to activate that Payment Method themselves in their account settings.
You could have a PMC that is configured to allow Samsung Pay but if the Connected Account you are creating a Direct Charge on does not have Samsung Pay enabled, it won't show up.
prisma orbit
ok on the dashboard thing
The key thing: i don't know, i've never enabled capabilities via API before
autumn dew
Yeah, okay I spent some time revisiting this myself while I was away. The problem as I understand it is that you don't request capabilties for Standard Acounts because they are independent entities. It's up to them to activate the payment methods themselves.
prisma orbit
The key thing: i don't know, i've never enabled capabilities via API before
So this was not enitrely rue
I already have 1 API call during our connect onboarding
I cant say if I need to, but I do
autumn dew
My colleagues and I did some digging on the specific error message as well. The error is being thrown because Standard Accounts don't have a Test mode identity. In the internals of the Stripe codebase, they are live accounts regardless of how you are connected. Express/Custom accounts have a separate test mode identity that allows this to work.
This is also why live mode works. because the CA evaluates to Live so requests with a Live API key work while requests with a Test API key throw a "mode mismatch" error.
prisma orbit
Yeah, okay I spent some time revisiting this myself while I was away. The probl...
Okay, but I meant that this is not true. I do request capabilities for standard connect
prisma orbit
My colleagues and I did some digging on the specific error message as well. The...
But okay, I guess I cannot test it properly then
autumn dew
Honestly I think it is a weird situation but it might be possible to test this using Sandboxes. Since a Sandbox is a Standalone account that only has a Test identity.
I know you said you don't use Sandboxes but it might be worth dipping a toe in that water if you want to test this fully
autumn dew
100% and I will flag that
prisma orbit
I'm currenrtly in a deadmines run in classic wow HC with my GF so i'll proceed in a bit
I'm guessing we can close this for nwo
autumn dew
Ack.
untold boneBOT
nickdnk_account-capabilities-requests