#momo_api
1 messages · Page 1 of 1 (latest)
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1386960189273411605
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- momo_webhooks, 6 days ago, 18 messages
hello, if your Checkout Session doesn't include automatic_tax.enabled, are you using manual tax rate?
hmm..based on req_OpnPMzaN4ovJW1, this checkout session is not collecting tax.
yes
What will happen if we don't pass the tax related fields?
then the checkout session will not collect tax.
there are two ways to collect tax with Stripe Checkout — using Stripe Tax (automatic_tax), or using Tax Rates
When we call the Create a Checkout Session API and set automatic_tax[enabled] = true, we receive the following error:
"Automatic tax calculation in Checkout requires a valid address on the Customer. Add a valid address to the Customer or set either customer_update[address] to 'auto' or customer_update[shipping] to 'auto' to save the address entered in Checkout to the Customer."
What does this mean and how should we handle it?
we want to using Stripe Tax (automatic_tax)
Is there a way for us to enable automatic tax calculation in the API, without providing the customer’s address in advance, and instead rely directly on the billing information entered by the user during Checkout?
It means you are creating a Checkout Session that wishes to calculate tax automatically, but the customer object (cus_SYXTC6Sr1arpJ6) doesn't have a saved address for Stripe to know where the customer is based — we need this information to calculate tax.
as per the error message, if you want to create a checkout session passing an existing customer that doesn't yet have a saved address, you can set "auto" to customer_update.address and customer_update.shipping to let the customer enter their address during checkout.
What will happen to us if we don't collect tax?
this is not a question I or my team can answer because it will depend on where your business operates and the tax regulations there. I'd recommend speaking to a tax advisor about this
After we’ve set the two address-related parameters, do we still need to set automatic_tax[enabled] = true?
Yes, setting automatic_tax[enabled] = true is what triggers Stripe Tax to calculate tax for the checkout session.
ok,I'll try
and then will not receive the error message?
passing automatic_tax[enabled] = true with customer_update.address and customer_update.shipping should not give you the same error.
For this request ID: req_FbHfdQeIDQLvpe, we did not pass any payment-related parameters, but we still specified card and link as the payment methods. However, no other payment options were displayed.
using payment_method_types [0] tells Stripe the payment methods you want the created checkout session to display.
If you want the created checkout session to use payment methods you enabled in the Dashboard, then you should not pass payment_method_types .
[0] https://docs.stripe.com/api/checkout/sessions/create?lang=curl&api-version=2025-05-28.basil
but we do not pass the payment_method_types,this parameter was passed by default in the API request.
I'm sorry, are you referring to this request: req_OpnPMzaN4ovJW1?
Yes I can see payment_method_types is not used in req_OpnPMzaN4ovJW1. This means the created checkout session will use the payment methods enabled in your Dashboard's settings.
I'm not quite sure about what you meant by "this parameter was passed by default in the API request." - could you elaborate?
We can see in the backend that these payment methods have been activated, but on the payment page, only Card and Link Pay are displayed.
This is because some payment methods do not accept recurring payments. In req_OpnPMzaN4ovJW1, the checkout session is configured to create a subscription and EPS, for example, doesn't support recurring payments: https://docs.stripe.com/payments/eps
Note that in general, Stripe also displays compatible payment methods to your customers based on chosen currency, any payment method restrictions, or their location. You may find this guide helpful: https://docs.stripe.com/payments/dashboard-payment-methods?payment-ui=stripe-hosted
Does Apple Pay support recurring payments?
Yes it does. [0] But the customer needs to be using a supported browser and device to be able to see Apple Pay. You can use the supported browser section on this page [1] as a guide.
[0] https://docs.stripe.com/apple-pay
[1] https://docs.stripe.com/elements/express-checkout-element#supported-browsers
I get it