#karsh - tax
1 messages · Page 1 of 1 (latest)
hey there, taking a look
So this is not currently exposed explicitly, though we're looking at ways to make that available
Currently you'd need to ask your users during onboarding, or otherwise make some request to test this.
ie create a checkout session and detect that error
Ah I see... for us, stripe Tax is a unique selling point that we want to add to our SaaS. It makes things easier for our customers - so we basically want to 'resell' it. We will make it easy for our customers to enable stripe tax and then use it through our platform to sell their products
Hmm so the second option is the most reliable? (if they don't set it up during onboarding, but later, then we should check again if it's set up)
Yes, at this point that'd be the only way. I'd suggest you have your UI ask them if its set up, and only verify after they tell you it is
I mean your application where you onboard users, sign up for an account etc
Thanks! Any way I can get a ping when it's exposed in the API?
"Have you set up Stripe Tax in your Stripe Dashboard?"
If you right in to support and mention my name I can track the work internally and reach out when I get updates 🙂
And one more q: in this checkout session for a connected acc it's showing 'COURSES' without a logo. How can I let the connected accounts customise this?
Assuming you created this using the stripe accoutn header, they'd need to set up their branding settings in the dashboard
Yes, is there another way to create it with info from our db? I expected we can pass some parameters for this into the 'create session'
Sorry, what do you mean?
The branding (icon) must be set by the connect account in their dashboard
I expected to be able to pass params to this https://stripe.com/docs/api/checkout/sessions/create
Like "checkout_title": "Black friday deal"
If you want to control more of this experience, you'll need to consider using express or custom accounts, putting the branding and customer tax configurations under your control (but this also is a big change to charge flows and liability etc)
Why would you expect a parameter like that? Did you find some reference/guide saying so?
The name displayed is the merchant selling the good/service
then the line items show the descriptions for the products being sold
We're going with standard accounts now to keep things simple and especially not ahve to worry much about liability now.
I expected that parameter naturally, I didn't see any reference no
Okay so:
- these lines (top left) are the only ones customisable with parameters creating the session ?
- And that's done by setting the
line_items.description? (I'm now actually settingline_items.titlewhicih I don't see in the documentation, is this replaced withline_items.description?)
- the best way to let users customise is by simply giving them this link? https://dashboard.stripe.com/settings/branding
Or can we 'embed' this into our ui?
Yes, though we'd suggest using price/price_data instead of the description
What is the response body you're showing in the dev tools from?
It appears that you might be looking at an internal API request used by Checkout, which may use title but that's just for mapping data to the UI and isn't necessarily reflective of the API you use for integrating
Are you all set now @cosmic wraith ?
That response is from my own server - anyway I'll try description andl ook at price/price_data
Thanks for the help, would just like to know an answer to question 3: what's the easeist way for our clients to set their branding? We send them https://dashboard.stripe.com/settings/branding ? OR can we embed do something similar to the standard accounts onboarding workflow
They use that page on the dashboard, yes
You can direct them there with some guidance about what to set to fulfill what you're aiming for
If you're creating new accounts via the API as we recommend, you can help them set this initially during your onboarding flow:
https://stripe.com/docs/api/accounts/create#create_account-settings-branding
but for standard accounts this is not available for update requests after creation