#dimi-cli-forward

1 messages · Page 1 of 1 (latest)

pure jay
flint marten
#

hi 👋

#

if I try with stripe listen --forward-to https://localhost:443

#

then I get a url of http://https://localhost:443

pure jay
#

I don't think it will work if you don't have a valid TLS certification

#

it's localhost, you should configure it to support http I would say

#

hum

#

I just tried and it works fine for me

#

I did stripe listen --forward-to https://localhost:8888 and get events forwarded to my localhost server (which fail since I don't support HTTPS)

flint marten
#

oh

#

--skip-verify

#

Hey, can I ask you another q?

#

about Custom Connect accounts onboarding

pure jay
#

of course

flint marten
#

I am sending an account link request:

pure jay
#

(protip: never send pictures of code 😉)

flint marten
#

oh ok

pure jay
#

Discord has code formatting, wrap between three ` before and after!

flint marten
# 
const link = await this.stripe.accountLinks.create({
      account: stripe_account_id,
      type,
      refresh_url,
      return_url,
      collect: "eventually_due",
    });
#

I've used it a lot, just use slack @ work so I've forgotten

#

So anyway, the issue is, as part of creating the accounts at Stripe, before linking them

#

I am sending the following:

# 
 capabilities: {
        transfers: {
          requested: true,
        },
      }
#

and

# 
 country: "GB",
      business_type: "company",
#

however, as part of onboarding, for some reason, Stripe's custom onboarding flow

#

doesn't ask us for bank details to create and verify an ExternalAccount for that user

pure jay
#

What's the account type? You said Express but we do ask for bank account details during onboarding. So I'm guessing you are using custom instead

flint marten
#

yes, custom 👍

flint marten
pure jay
#

ahhhh sorry, I got a parallel thread about Express 🤦‍♂️

#

And so yeah, we do not collect bank account details for Custom accounts today. This is something you, as the platform, have to collect yourself

flint marten
#

oh ok

#

so we can't use the custom onboarding from stripe for those

#

we have to use the api

#

however, we can still rely on webhook updates for whether this external account was verified and can receive payouts now?

pure jay
#

there's no "verification" for bank account so no

#

but the rest is correct, you just won't get any event about the bank account being verified

flint marten
#

thanks!

#

do you know any other causes of

#

No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe? https://github.com/stripe/stripe-node#webhook-signing

#

besides not passing a raw body, I can confirm the body is a Buffer

# 
const constructed_event = this.stripe.webhooks.constructEvent(
        body,
        signature,
        this.secretsService.get("stripe_webhook_secret"),
      );
#

and the signature is the stripe-signature header

#

I can confirm that the secret is also correct with the webhook config at the stripe web dashboard

#

and it's in test mode

#

could it be because I am sending the event from a local test with stripe-cli?

pure jay
#

it is almost and utterly always the raw body :p

#

there are dozens of code examples that subtly differ based on your stack/environment for stripe-node

#

but if it's not that, it's usually that you have the wrong webhook secret

flint marten
pure jay
#

no idea what you printed lol

#

that's not text at least

flint marten
#

it's the body

#

in the node debug console

pure jay
#

ah sorry I missed your reply my bad