tal_v2-account-links-404 | Stripe Developers | Page 1

queen sluiceBOT May 29, 2025, 3:05 PM

#

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

📝 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.

tal_api, 2 days ago, 12 messages

#

valid cosmos May 29, 2025, 3:12 PM

#

Hi there, I'll be right with you. I'm working another thread.

coarse mist May 29, 2025, 3:15 PM

#

No worries.

#

btw, if I have another issue with accountLinks do you prefer I would ask here or open a new thread?

valid cosmos May 29, 2025, 3:42 PM

#

To be sure I understand your question, are you asking for the v2 equivalent of v1 events for account onboarding?

coarse mist May 29, 2025, 3:43 PM

#

Yes.

queen sluiceBOT May 29, 2025, 3:45 PM

#

buoyant tulip May 29, 2025, 3:46 PM

#

Hi 👋

I"m stepping in as my colleague needs to go soon

coarse mist May 29, 2025, 3:46 PM

#

Do I need to itterate over requirements or looking at requirements.summary.minimum_deadline is enough? or configuration.merchant.capabilities ?

#

Hi @buoyant tulip

buoyant tulip May 29, 2025, 3:48 PM

#

For v1 Accounts, we have recommended using the requirements and capabilities properties to identify if an account needs to go through more onboarding or update information.

coarse mist May 29, 2025, 3:48 PM

#

You mean v2?

buoyant tulip May 29, 2025, 3:53 PM

#

No but the same applies. This has been our standard recommendation for both v1 and v2. There are some additional nuances because the V2 account is intended to capture much more than V1.

#

For instance, the requirements property is much more complex in V2 than it was in V1

#

Which you can see in the API response to the request you shared: https://dashboard.stripe.com/test/logs/req_v2mBWDDhFf6p4z9FL

coarse mist May 29, 2025, 3:56 PM

#

I am looking at req_v26dZReVxKFGX8ppQ now. So, itterating over requirements.entries.requested_reasons for routine_onboarding would give me the idea for a complete onboarding?

buoyant tulip May 29, 2025, 3:58 PM

#

Looking at that request I see the following in the reponse

{
  id: "acct_1RU8mQ4GvjmXoPeW",
  object: "v2.core.account",
  applied_configurations: [
    "merchant",
  ],
  configuration: null,
  contact_email: "XXXXX@XXXXXX-test.com",
  created: 
"2025-05-29T15:54:09.000Z"
,
  dashboard: "****",
  defaults: null,
  display_name: null,
  identity: null,
  livemode: false,
  metadata: {},
  requirements: null,
}

so I'm not sure what you are referring to here.

#

Or do you mean that, since requirements is null, there is nothing required? If so, yes that is my understanding as well

coarse mist May 29, 2025, 4:00 PM

#

Screenshot_2025-05-29_at_11.59.50_AM.png

#

I think that is a good way to determine initial onboarding: https://docs.stripe.com/api/v2/core/accounts/retrieve?api-version=2025-05-28.preview&rds=1&lang=php#v2_retrieve_accounts-response-requirements-entries-requested_reasons-code

Retrieve an Account | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

buoyant tulip May 29, 2025, 4:14 PM

#

Yes, I concur. To be honest, I haven't spent much time with Accounts V2 since they aren't generally available yet. But the details about who needs to do what in the requirements property seems to be very complete and indicate where the responsiblity for each requirement lies.

coarse mist May 29, 2025, 4:15 PM

#

Go it!

#

Other question, for req_v2YarF0kIhw8URdmO I get 404 The API method cannot be found.

#

The request:

array:2 [▼
  "account" => "acct_1RU94d4D9AXP3zCS"
  "use_case" => array:2 [▼
    "type" => "account_onboarding"
    "account_onboarding" => array:3 [▼
      "configurations" => array:1 [▼
        0 => "recipient"
      ]
      "return_url" => "https://example.com/return"
      "refresh_url" => "https://example.com/refresh"
    ]
  ]
]

queen sluiceBOT May 29, 2025, 4:16 PM

#

buoyant tulip May 29, 2025, 4:20 PM

#

Yes I can see that. Unfortunately, this is still not a generally available feature so we have limited information about when it is or is not available. I'm looking for any info we might have on requirements for this API method.

coarse mist May 29, 2025, 4:22 PM

#

Ok. Thanks.

buoyant tulip May 29, 2025, 4:23 PM

#

Can you share the docs you are following?

coarse mist May 29, 2025, 4:24 PM

#

https://docs.stripe.com/api/v2/core/account-links/create

buoyant tulip May 29, 2025, 4:25 PM

#

Hmmm... that gives me a 404 and I've got a Sandbox account with access to V2

coarse mist May 29, 2025, 4:25 PM

#

Screenshot_2025-05-29_at_12.25.32_PM.png

buoyant tulip May 29, 2025, 4:25 PM

#

Yeah, that doesn't help.

coarse mist May 29, 2025, 4:26 PM

#

Maybe the SDK version ?

coarse mist May 29, 2025, 4:26 PM

#

buoyant tulip Yeah, that doesn't help.

Trying to hare what I see.

buoyant tulip May 29, 2025, 4:26 PM

#

I think the problem is this is still in private preview. Do you have a Stripe contact who enrolled you?

coarse mist May 29, 2025, 4:26 PM

#

Nope, not private preview.

buoyant tulip May 29, 2025, 4:26 PM

#

There is a property on your Sandbox account that literally says private preview for V2 accounts.

coarse mist May 29, 2025, 4:27 PM

#

I have no Stripe contact who enrolled me.

#

I literally toggled it on.

buoyant tulip May 29, 2025, 4:29 PM

#

Okay still digging.

#

I don't think it would be an SDK issue, since the stripe-php SDK added support for creating V2 Account links in version 17.2.0-beta.1 - changelog

coarse mist May 29, 2025, 4:37 PM

#

https://docs.stripe.com/api/v2/core/account-links/create?api-version=2025-05-28.preview&rds=1&lang=php

Create an Account Link | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

buoyant tulip May 29, 2025, 4:40 PM

#

Yup. I just prefer to review change logs

#

I've reached out to some colleagues for assistance. I was able to create a successful link with my own V2 Sandbox account so now I'm trying to figure out how your request and mine are different.

coarse mist May 29, 2025, 4:54 PM

#

Sounds good. Thanks.

buoyant tulip May 29, 2025, 5:03 PM

#

Okay so this took a while but we think we know why this isn't working. Can you try enabling your V2 Sandbox for Global Payouts by going here: https://dashboard.stripe.com/test/global-payouts ?

coarse mist May 29, 2025, 5:05 PM

#

Got that:

You cannot get started with Global Payouts because you are already in another public preview program. Contact Stripe support if you have questions.

buoyant tulip May 29, 2025, 5:07 PM

#

🤦‍♂️

coarse mist May 29, 2025, 5:07 PM

#

lol

#

btw, I am able to manualy create a connect onboarding link, it's only when using the API- so I think account permission allow for my connected customers to onboard.

buoyant tulip May 29, 2025, 5:10 PM

#

Okay I've got a couple requests for you

Can you try spinning up a fresh Sandbox account and only enroll in the Global Payouts?
Can you write in to Support so we can raise this with the product team? I will send you a DM with a link to create case that will go straight to my team.

coarse mist May 29, 2025, 5:11 PM

#

Sure. Give me couple minutes.

#

Ok, when enrolled only with Global Payouts on a newly created Sandbox I get that while testing and trying to create a Connect account:

Stripe\Exception\InvalidRequestException: Some fields in the request were invalid: 'defaults: Field is currently not available for use with Global Payouts.'; 'dashboard: Field is currently not available for use with Global Payouts.'; 'configuration.merchant: Field is currently not available for use with Global Payouts.'

#

V2 preview is disabled, you want me to ENABLE it in addition to enrolled in Global Payouts, or keep it only with Global Payouts?

buoyant tulip May 29, 2025, 5:16 PM

#

Enable V2 Preview

coarse mist May 29, 2025, 5:18 PM

#

Same.

#

btw, I toggled the v2 and now can not see that setting any longer - which is in difference from the other sandbox where I can still see that. Looks like there is an interfernce between Global Payouts and V2.

buoyant tulip May 29, 2025, 5:20 PM

#

Okay I'm going to send you a DM to create a support case so I can flag this to the V2 product teams.

queen sluiceBOT May 29, 2025, 5:20 PM

#

Hello @coarse mist, we have sent you a direct message, please check it at https://discord.com/channels/@me/1377698191633416214

🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.

coarse mist May 29, 2025, 5:20 PM

#

Ok.

#

Done.

buoyant tulip May 29, 2025, 5:29 PM

#

Great, thanks. We will raise this internally and hopefully get this addressed.

queen sluiceBOT May 29, 2025, 5:30 PM

#

#tal_v2-account-links-404

Hello @coarse mist, we have sent you a direct message, please check it at https://discord.com/channels/@me/1377698191633416214