#Reed-stripe-tax

1 messages · Page 1 of 1 (latest)

spice flint
#

Hi there

#

This is possible if you use Standard Accounts with Direct Charges

#

Your users would need to set up their Stripe Tax registration via their own Dashboards

#

But then it would be compatible

quaint zenith
#

Thank you! Would that affect our ability to retain shipping charges?

We don't want to add an extra payment layer for our customers to pay for their shipping, we'd like to retain the shipping amount to cover our UPS invoice.

spice flint
#

Can you clarify what you mean by that?

quaint zenith
#

Oh, yes, would this be a use of Application Fees?

spice flint
#

I'm not sure I 100% understand

#

Yeah I assume what you are saying is solved by Application Fees

#

But I'm not positive exactly what you mean

quaint zenith
#

We're providing UPS labels on our UPS account

#

So we're getting invoiced directly for our customers' shipping

#

Rather than invoicing our customer for shipping on a monthly basis, and risking late payment, we'd like to retain the shipping amount upfront at time of transaction

#

So from what you're saying (and again, thank you very much), we can put in the full charge, with the shipping amount as an application fee

spice flint
#

Yep you are basically saying you, as the platform, pay the shipping cost. Not your Connected Account users.

#

So you build the shipping amount into the charge to the end-customer and then you take an Application fee that covers that shipping amount to pull the necessary funds for shipping into your platform.

quaint zenith
#

Exactly, thank you!

spice flint
#

👍

quaint zenith
#

I have a related follow-up question, will Stripe Products work the same way with a Standard Connect account

#

That is to say, we'd like to mirror the product information that our customers enter into our platform over to Stripe Products (just for their Standard Connect Account) so that we can use the Orders API beta.

half dust
#

Hello, bismark had to step up but I can help. Catching up on this thread...

quaint zenith
#

Hi Pompey, thank you!

half dust
#

I think that this will work the same as long as you keep the product data the same (keep in mind that it will not sync between accounts).

#

Can you tell me a bit more about what you are using the Stripe products for here?

quaint zenith
#

Our model is something like this:

We build custom eCommerce frontends on a platform backend. Each of our customers has a separate site, eventually with the option to list on a common marketplace. We want to make sure they can use Stripe Tax, so we're going to implement either the Orders API or the Checkout API, which get tax code info from the Products API.

Each customer would need a separate list of products, as there may be naming conflicts.

Is the products API appropriate for this, or should we prepend some kind of clientID before the product name to distinguish them?

half dust
#

That should work as long as long as you keep track of which product maps to which account.

#

Can definitely prepend things if it helps for your organization but that definitely makes sense as a way to provide this data for Stripe Tax

quaint zenith
#

Thank you! So just to confirm there's no way to divide the Stripe Products list up for each of our customers, and manage each from our platform.

#

That is to say, Stripe Products will not instance per Standard Connect account?

half dust
#

Not really with Standard accounts unfortunately. With standard accounts you are making calls directly on the other account and API objects can only live on one account which means you need to create copies on each account that you are working with.

That being said, one thing that may work for you is using the product_data hashes when creating your Checkouts and Orders. Basically they allow you do define products ad-hoc, so you can have the pull the product info from your platform account and then pass it on in each API call where you are creating an order or checkout session https://stripe.com/docs/api/orders_v2/create#create_order_v2-line_items-product_data