#chambaz
trail onyx
Hello! Stripe Tax is supported in Checkout, Invoices, and Subscriptions. It's not currently supported if you create Payment Intents directly. We have some documentation about this here: https://stripe.com/docs/tax
Can you tell me more about your specific use case so I can advise you further? When you say "loop through customers and charge them" what does that mean exactly?
forest swan
Hey thanks for the response. So right now customers are pre ordering and saving their payment details via Future Payments (setup mode) with Checkout. When it comes time to fulfill our orders we will be looping through all orders (we have a firebase DB) and looking up Stripe customers to trigger a charge using the Charge API.
Is there a better approach for charging our customers who have preordered and saved payment details to ensure Tax is applied correctly?
Perhaps if we use the setup intent ID from the checkout success event?
trail onyx
Creating Charges directly is deprecated, so you should move away from that if possible.
For tax support you would need to use Invoices for this use case instead of direct Charges or Payment Intents. We have documentation for creating one-off Invoices here: https://stripe.com/docs/invoicing/integration
Do you loop through your customers on a regular basis for recurring payments, or are these one-time delayed payments?
forest swan
These are one time delayed payments. Once we are able to fulfill in real time we'll start taking payments in real time and this wont be an issue. Its just for this initial round of customers.
If we use invoices then the customer wont be charged automatically will they? Meaning it will require an action from the customer.
If creating charges directly is deprecated then what is the purpose of future payments? We thought the purpose was to store payment info to be charged at a later date
trail onyx
If we use invoices then the customer wont be charged automatically will they? Meaning it will require an action from the customer.
That depends how you configure the Invoices and use the API. You can do either.
If creating charges directly is deprecated then what is the purpose of future payments? We thought the purpose was to store payment info to be charged at a later date
Creating Charges directly is deprecated, but creating Payment Intents directly is not. See here for more information: https://stripe.com/docs/payments/payment-intents/migration
Future payments can be made by creating Payment Intents directly, using Invoices, using Subscriptions, etc.
forest swan
Ok gotcha. And to clarify Payment Intents do not work with Tax so our best bet to charge customers with dynamic tax and the card they saved is to use invoices, which we can setup to charge automatically?
(using the card saved on file previously)
trail onyx
Yep, that's correct!
trail onyx
You would trigger payment via the API using this endpoint: https://stripe.com/docs/api/invoices/pay
forest swan
Create the invoice first with collection_method set to automatic and then trigger using the pay method right?
I see the payment method ID in here too so we can make sure it uses the card saved on file
trail onyx
Yep, that's correct. You probably want to set the Payment Method as the Customer's invoice_settings.default_payment_method: https://stripe.com/docs/api/customers/create#create_customer-invoice_settings-default_payment_method
forest swan
got it!! Super helpful!
Final question, is any of this possible from the dashboard or are we really restricted to the API? It's my intention to use the API but our client is wondering if it woudl be possible to charge anyone manually (through stripe.com dashboard) if they needed to for some reason
trail onyx
Yeah, you can create Invoices that use automatic tax through the Dashboard.