chip

[acoustic smelt]

Hey there

Correct, Product IDs aren't sensitive and are fine to expose

The only thing you don't want to embed is the client secret

[little oyster]

Great! Thanks.

Sinced I have this thread, I'll take the liberty to ask another question.

I am currently integrating Stripe Connect with Standard accounts, and saving the accountId to a DB column. Although, are there any best practices to when I should save it? When the entire onboarding is completed, or should one do it once the account it created with the api?

I guess as soon as it is created, in order to let the customer continue their onboarding if not completed? Atleast that is my understanding

[acoustic smelt]

Yep

I would save it on creation

And then you listen for account.updated events

That way you can also prompt your users to return and finish their onboarding and provide them with an Account Link

(If they don't complete their onboarding that is)

[little oyster]

Great! Awesome, then I wasn't too off track 😄

btw, is it possible to somehow request payment methods to be added for Stripe?

[acoustic smelt]

Hmm what do you mean by that exactly?

[little oyster]

Well, in Norway there is something called Vipps, which is basically the biggest form of payment here.

Is that something that Stripe could add, the same way Klarna exists?

or would that perhaps be direct competition that you're integrating? 😄

[acoustic smelt]

Ah I see

A new payment method you mean that we don't yet support

You can write into our Support team via https://support.stripe.com/contact/login and they can put in a feature request for you!

The more folks we hear from that want it the more likely we are to build an integration for it.

[little oyster]

Awesome! Will do. Thanks for helping out, appreciate it 🙂

[acoustic smelt]

Sure thing!