#karsh - tax
1 messages Β· Page 1 of 1 (latest)
Just to confirm the earlier message was asking about support for Stripe Tax on Payment Intents, correct?
Correct
Not sure if you can see it, but this is the message "I want to set up Stripe Tax, but I only see that it's available for Checkout? https://stripe.com/docs/tax I'm using the paymentIntent API. Can I use Stripe tax? If yes can you point me to the docs please"
If so, this is not currently supported. When integrating directly with payment intents you control the calculation of the amount for the payment and send that to the API, tracking how that maps to tax etc is something you need to handle.
I see, so if I want to use Stripe Tax - I need to use Stripe checkouts, that is the only way?
https://stripe.com/docs/tax/faq#what-integrations-do-you-support
What integrations do you support?
We can support platforms integrated with Checkout, Billing, and Invoicing. We canβt support PaymentIntent users but if youβre a platform interested in building your own UI for one time payments, weβd love to hear from you about your use case! Please email us at orders-beta@stripe.com with some more details about your business.
So there are other options beyond Checkout, but Payment Intents is not currently supported
Thank you, that helps a lot. It's weird how the documentation is so extensive yet many times I have to get the right page linked by one of you π I must be searching in the wrong way
There is a lot to cover, and it can be difficult to organize/navigate depending on how you're thinking about things.
That's true. So I'd like to check a few more things if possible
- Stripe Elements are equal to using paymentintents,correct? https://stripe.com/docs/payments/online-payments
I also see in the table above that it doesn't support stripe tax
- I honestly can't remember right now why I've went with Elements and paymentintents, I think because I was limited by stripe checkouts. I do remember seeing an extensive comparison table of Checkout vs Elements/paymentintents... But also can't find it right now, do you know what I mean? I'd like to see which things I'm giving up on my using checkouts
They can be, but you can also use elements to complete payments for subscriptions, which do support Tax. Elements are the way to collect payment details securely in a browser, and apply to many different payment patterns.
Then, can Elements be used to complete payments for one time purchases? We want to offer both subscriptions and one time purchases
Yes, Elements can be used for both one time payments with payment intents and for completing payment to start a subscription
Of which only the 'completing payment to start a subscription' supports stripe tax, correct?
I'm not sure what this is referring to, unfortunately
Well you can use Stripe Tax with Billing/subscriptions, recurring subscription payments can make use of Stripe Tax. You use elements to complete payment on the first invoice to start the subscription.
Ah okay thanks, I think I got that part.
THen for question 2: do you have any other resources with information on 'when to choose checkouts or elements'?
It's a decision about how much you want to build yourself vs how much control you have over the payment experience
checkout = less work, less control
elements = more work, more control
and your particular integration needs. if you want/need to do something unsupported by checkout then it may not be an option (but we'd love to hear about that use case!)
It would help if I can list my use cases and see if we can do that with checkout
for most people, I'd recommend starting with Checkout and a basic integration pattern to get started, then figure out whether its limiting you in some way and build out a custom solution if needed while your customers are still able to pay you via checkout
we're building a platform, so we have a Connected account. We have a lot of particular features in mind for our platform that we want to use as unique selling points - other platforms in this market don't necessarily have this.
Could you tell me if we can do the following with checkouts?
- one click orders with saved payment info (like amazon)
- one click upsells (directly after purchasing a product, being able to purchase another product with 1 click)
- subscriptions (also with SEPA, with payment methods like iDeal)
- order bumps (adding a product at the last moment)
- affiliate / share money to other connected accounts (a product is sold by 2 people with their seperate stripe standard accounts, they get a split)
- payments in installments
There is some support via Checkout for some of those requirements (see links below) but broadly it sounds like you're going to want more control than Checkout offers you. Note that Checkout is a redirect flow, it's not presented within your own page.
https://stripe.com/docs/payments/checkout/upsells (upsell subscriptions from monthly to annual eg)
https://stripe.com/docs/payments/checkout/customization#link-with-stripe (one click payment for return buyers)
https://stripe.com/docs/payments/checkout/cross-sells (add an item during checkout)
https://stripe.com/docs/connect/charges-transfers (split a payment to multiple parties)
https://stripe.com/docs/payments/buy-now-pay-later#product-support (Buy Now
Pay Later payment methods and support for Checkout)
https://stripe.com/docs/payments/sepa-debit/accept-a-payment?platform=checkout (SEPA)
https://stripe.com/docs/payments/ideal/accept-a-payment?platform=checkout (ideal)
Thank you so much! Will take a look now
It's very hard to make a decision, I feel like I need to make a proof of concept of each feature that we want. But that woudl take a lot of time.... but that seems liek the only way to figure out if we're limited by stripe Checkout
Hello! Just letting you know I'm taking over here. After catching up with the messages above it sounds like one-off Invoices are probably the closest match to what you want for your one-time payments: https://stripe.com/docs/invoicing
@storm sleet Copy-pasting your question here: Creating invoices would allow me to do all 6 things that I mentioned? So it' sbasically like using the paymentintent api (with elements still?) and also supports Stripe tax?
Do you mean this list of 6 things:
- one click orders with saved payment info (like amazon)
- one click upsells (directly after purchasing a product, being able to purchase another product with 1 click)
- subscriptions (also with SEPA, with payment methods like iDeal)
- order bumps (adding a product at the last moment)
- affiliate / share money to other connected accounts (a product is sold by 2 people with their seperate stripe standard accounts, they get a split)
- payments in installments
correct
Gotcha - so to answer your question, yes, Invoices are just built on top of Payment Intents and can be used with Elements while also supporting Stripe Tax.
1. one click orders with saved payment info (like amazon)
The hosted Invoice page doesn't support this, but you could built this yourself on top of Invoices
2. one click upsells (directly after purchasing a product, being able to purchase another product with 1 click)
I believe upsells is something specific to Checkout, and is isn't offered with plain Invoices
*3. subscriptions (also with SEPA, with payment methods like iDeal) *
Yes, Subscriptions are just built on top of Invoices.
4. order bumps (adding a product at the last moment) - Modifications can be made to an invoice up until it has been finalized.
Once it's been finalized you can't add additional invoice items
5. affiliate / share money to other connected accounts (a product is sold by 2 people with their seperate stripe standard accounts, they get a split)
Yes, this is supported. You'll have to do the transfers separately if you want to split the funds across multiple connect accounts.
6. payments in installments
What do you mean by installments? If you're referring to Klarna and Afterpay/Clearpay, then no, it is not supported by Invoics
That's interesting... I would've never thought to look at invoices as the solution to my challenge...
Point 5: you mean the customer needs to go through two checkout transactions? So fill in their payment info twice?
- Installments as in, for example pay the total amount in 3 parts. Every month 1 part
No, the customer would only go through the transaction once, and when it's complete you'd transfer the funds to appropriate conent accounts
Gotcha
- Installments as in, for example pay the total amount in 3 parts. Every month 1 part
We support installments in Mexico with Payment Intents, but not in other countries. The solution would be to create a Subscription that models the installments (a monthly subscription that cancels after three months)
And you're saying invoices are built on top of payment intents, so I'd go with:
Elements client side -β paymentIntent server side β invoices ?
- Gotcha
Elements client side -β paymentIntent server side β invoices ?
Yup that's the general idea.
Okay can you help me out finding the right documentation? If I go here:https://stripe.com/docs/invoicing
Then go to: https://stripe.com/docs/invoicing/connect I see it's talking about 'direct charges' but isn't that replaced by the paymentintent API?
Direct charges is just our term for the funds flow - it does use the Payment Intent API
And I don't see anything regarding stripe tax on that page above, I do see this page https://stripe.com/docs/tax/invoicing - is this what I need?
(I don't just want stripe to calculate tax on the invoice, I want it to automatically handle the taxes for our connected accounts (at least generate the reports and possibly integrate with one of your partners so they can file it)
Are you talking about tax reporting? https://stripe.com/docs/connect/get-started-tax-reporting
wow the rabbit hole never ends haha
Well I guess that could help as well... I thought this is all Stripe has to offer for taxes
1099 is US filling?
Yeah, admittedly we don't know a ton about tax filing here - you'd have more luck asking support (https://support.stripe.com/contact). And yes, 1099 is US filling
Okay we need something for the EU and US.
With your suggested route: elements β paymentintent β invoices , I'd still need to calculate the tax by myself right? And this would be done automatically by Stripe Tax if I use checkouts https://stripe.com/docs/tax?
With your suggested route: elements β paymentintent β invoices , I'd still need to calculate the tax by myself right?
Sorry let me by super clear - you won't be creating the Payment Intent yourself. Creating an Invoice will automatically create a Payment Intent for you, which you use with Stripe elements. Invoices do automatically support Stripe Tax, and you wouldn't need to calculate it yourself
Ah I see, okay that clears it up a bit. Could you point me to the documentation for the flow you're describing please? Then I'll see how far I get π
There isn't really a single doc that covers it - you'd want to use the Invoice's PI (found at payment_intent https://stripe.com/docs/api/invoices/object#invoice_object-payment_intent) in combination with this doc (https://stripe.com/docs/payments/accept-card-payments?platform=web&ui=elements)
The warning in the second link can be ignored? This is not a method that's deprecating?
Ahh! Sorry - I meant to send you to https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements instead
The one I sent you uses our slightly older card Element. The newer docs cover a lot more with the new payment element.
I need to head out, but one of my teammates is hopping in and can answer any follow ups!
Thank you, i'll dive into these links first!
hello again π -- just let us know if you need ay more help and giving this a try