#benclum11
topaz waspBOT
Hello benclum11, we'll be with you shortly! 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.
• benclum11, 23 hours ago, 9 messages
worthy hollow
here's the "a mandate is required" log: https://dashboard.stripe.com/test/logs/req_AnZOunqI514dS7
whole dagger
Still looking. Need a few
worthy hollow
here's another thing I tried but got a 500 error: https://dashboard.stripe.com/test/logs/req_MQNUto4teZGRFK
whole dagger
Do you see the same error if you confirm the PaymentIntent and only pass the PaymentMethod ID and Mandate ID and don't pass setup_future_usage at all?
worthy hollow
yeah same error: req_Vf5uFefnvgRNvT
whole dagger
Thanks for testing.
We are still investigating
Can you try using https://stripe.com/docs/api/invoices/pay instead of confirming the PaymentIntent directly?
worthy hollow
if it helps, I also tried passing an empty string to payment_settings[payment_method_options][acss_debit] but it still added the payment method options when the subscription/payment intent was created: https://dashboard.stripe.com/test/logs/req_vPONVy9kUyoEeK
on POST /v1/customers/cus_OtFGQdqfrN4jqf/subscriptions
whole dagger
I think the only flow that is supported right now for this is to use a SetupIntent to collect the PaymentMethod and then set that PM as the default on the Customer or Subscription like we show here: https://stripe.com/docs/billing/subscriptions/acss-debit#save-payment-method-for-future-subscriptions
I'm a bit surprised by that
And I'll file feedback internally
But I think for now the route you are trying to go with confirming the Subscription PaymentIntent just isn't possible
worthy hollow
yeah that's what we're doing. we create the setup intent, attach it to the customer, and create the subscription. the payment intent requires confirmation and when we confirm it, it fails
whole dagger
Ah!
Sorry totally missed that
What if you just call confirm for the PaymentIntent without passing anything?
Or just call the Invoice /pay endpoint?
worthy hollow
same error as #1 in my original message: https://dashboard.stripe.com/test/logs/req_rgT2Af60mVhkaf
A mandate is required. Please either provide the id of an existing mandate on confirmation, or provide payment_method_options[acss_debit][mandate_options].
whole dagger
Okay and same thing for /pay from Invoice endpoint?
And can you try one last thing which is using payment_behavior: 'allow_incomplete' instead of default_incomplete?
worthy hollow
different error for /pay: https://dashboard.stripe.com/test/logs/req_h4Pz29rVFvdRCw
and for the payment_behavior, the payment_intent still required confirmation even with allow_incomplete: https://dashboard.stripe.com/test/logs/req_BuVYnirytZ2aPg
whole dagger
Looks like you are on a very old API (you are using our Customers API to create Subscriptions). Have you tried using the Subscriptions API directly (https://stripe.com/docs/api/subscriptions/create).
whole dagger
Sorry I meant try allow_incomplete with the Subscriptions API
I assume that is why that did nothing prior when you tested allow_incomplete
Since you were trying to use that on the Customer API
worthy hollow
gotcha, looks like the same result though: https://dashboard.stripe.com/test/logs/req_WncBmiPsbZ1MpT
whole dagger
What the heck!
topaz waspBOT
worthy hollow
from my understanding, acss_debit is unique in that the first payment always requires confirmation due to country laws. but I guess I could be wrong.
whole dagger
Alright before I file a comprehensive bug report, which I'll be doing any way since this flow the way you are trying it should just work, can you do one more test and literally go through what the docs show (https://stripe.com/docs/billing/subscriptions/acss-debit#save-payment-method-for-future-subscriptions) in terms of setting the PM up with a SetupIntent and then setting it as the default on the Customer and then create a Subscription with allow_incomplete and don't set the default_payment_method on the Subscription itself?
worthy hollow
oh my word I found the issue.... the stripe price currency didn't match the mandate currency.
once I changed the currency on the price, confirming worked.
worthy hollow
haha I know right. but glad I found it