#DevJoseph55

1 messages · Page 1 of 1 (latest)

calm plumeBOT
magic hinge
#

Hi there, so you want to collect a payment from a customer, but transfer to amount to multiple connected accounts?

obsidian creek
#

yes thats correct @magic hinge

magic hinge
obsidian creek
#

but does that support the tax information being automaticly uploaded for sellers @magic hinge ?

#

and is there any way to attach items to payment intents so that the receipt generated shows the items?

magic hinge
#

By tax information being automaticly uploaded for sellers, do you mean Stripe Tax? https://stripe.com/docs/tax

Stripe Tax

Calculate and collect sales tax, VAT, and GST automatically on your Stripe transactions—low or no code integrations available.

obsidian creek
#

I have products in stripe with attached tax categories, and when I created invoices it was automatically calculated, however creating the payment intent directly I'm not sure if that is handled @magic hinge

magic hinge
#

OK. I believe you are referring to Stripe Tax. Stripe Tax works with Invoicing, Billing, Payment Links and Checkout integrations. Using PaymentIntents API alone doesn't provide enough information to calculate the tax.

obsidian creek
#

is there a way to have stripe tax support, but also direct an invoice payment to multiple connect accounts? @magic hinge

haughty gazelle
#

👋 taking over here

#

So you are already woking on a workaround by collecting a SetupIntent, then for each Seller product you create an Invoice, with Stripe Tax enabled, and charging them per Invoice, correct

#

When you create Invoices, do you, as a Platform, own all the Products and Prices belong to your account and create Invoice accordingly?

obsidian creek
#

we represent sellers and upload different products on their behalf @haughty gazelle

#

when we upload them, the Products and Prices are under the platform account

#

We were working on the SetupIntent workaround above but wanted to see if there is a more appropriate solution that includes Tax support and doesn't charge the customer multiple times

haughty gazelle
#

So Checkout is an easy option. It works with Stripe Tax and you can specify multiple line items, each with 1 Products that you as the Platform owns, automatically tax-calculated. After the Checkout Session is made, you just perform multiple Transfers as the "Separate Charges and Transfers" my colleague linked in

obsidian creek
#

In order for tax to be collected for a connected account, does the product have to be created on that connected account? We are a platform like etsy where we have products listed but we do not actually 'Own' the products, if that is the case its possible we shouldn't have them on the main platform acct.
Also, you said this works for 'Checkout' to transfer afterwards, but would 'Invoicing' allow the same thing? @haughty gazelle

#

and if they are on different connected accounts then would it be possible to create one invoice still and then transfer?

haughty gazelle
#

I am not sure about legal requirement of if you need to have those Products on each of Seller account. It sounds like yes, but if you do that you won't be able to either use the Checkout approaches or the Invoice approaches. It's a question to Support team honestly.

And for "Checkout" I meant the Stripe Checkout product (Checkout Session). "Invoicing" is different but should works with multiple Products and Stripe Tax too:
https://stripe.com/docs/tax/checkout
https://stripe.com/docs/tax/invoicing
The main different is Checkout collects the customer's payment method for you, in frontend, similar to PaymentElement. But Invoice doesn't since it's simply a backend API call. Literally you need to use a combination of PaymentElement (collect the SetupIntent, separately from frontend) + Invoice (actually charge by creating PIs)

obsidian creek
#

Oh interesting, alright a Stripe Tax question then, does the connected account that the product is created on have the tax tallied to them at the end of the year on their 1099? A big reason we chose to add our products into stripe was to make sure this piece was handled @haughty gazelle

#

we already have most of the setup intent and invoice work done as we were leaning towards keeping the users on our site through checkout, but if checkout allows for only one payment vs 2 on a users card we would probably want to pivot to that. if we do move the products to the connected accounts, would we still have to generate 2 vs having one? or would we not even be able to charge the customer as the customers are all on the platform acc as well?