#ntountasakis

1 messages · Page 1 of 1 (latest)

split oreBOT
stoic turtle
#

Should say request body, not request payload.

oblique sierra
#

Hello! Can you explain more about what you're trying to do? When the refresh_url is accessed it's expected there would be no request body.

stoic turtle
#

I'm implementing a new seller signup as apart of stripe connect. After creating a connected account, I'm then sending the user a account link so they can walk through the express sign up. As I'm all testing this with the stripe cli, after generating the account link I'm waiting about 10 seconds or so to paste the link in the browser thus triggering the refresh_url as the one-time link is expired.

#

I'm generally expecting a https request body to look like this, however I'm finding that when my server endpoint is hit via this workflow the body is undefined.

oblique sierra
#

Are you using Custom connected accounts?

stoic turtle
#

This is an express user

oblique sierra
#

When the user is sent to the refresh_url it's a GET request, so there's never going to be a request body. I think what you might want to do instead is add a query parameter to the URL so you can tell who it is. Something like https://example.com/some/path?someParam=someValue

stoic turtle
#

Oh, it's not a POST?

oblique sierra
#

No.

stoic turtle
#

Ah okay, I will change this on my end. Thanks for the help Rubeus! When I was simulating the stripe workflow via curls I was sending it with a post payload because in the stripe dashboard I see under API logs POST commands run against /v1/account_links but that's of course... from me running the stripe cli command.

oblique sierra
#

Yep! The flow is:

  1. POST to /v1/account_links to create an account link
  2. Send the person to the Account Link URL you get back
  3. They go through onboarding
  4. They get sent (via a GET redirect) to the return_url you specified

Or, if the link is no longer valid, they'll get send (via a GET redirect) to your refresh_url instead.