datter_paymentelement-subscription | Stripe Developers | Page 1

jolly quartzBOT Jul 17, 2024, 3:54 PM

#

👋 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/1263161993175502881

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

frail seal Jul 17, 2024, 3:59 PM

#

Here are the ~200 lines of code

📎 message.txt

jolly quartzBOT Jul 17, 2024, 4:02 PM

#

mossy mantle Jul 17, 2024, 4:02 PM

#

Thanks for the info, still looking in to this. Does this happen when any payment method is selected? I am not immediately aware of when elements would attempt to confirm an intent without PM info but am looking in to it and will get back to you with what I can find

stable lava Jul 17, 2024, 4:07 PM

#

datter_paymentelement-subscription

frail seal Jul 17, 2024, 4:07 PM

#

FYI I have only enabled "cards"

stable lava Jul 17, 2024, 4:07 PM

#

I'm taking over, I'll wait for your reply as I can't really look for the needle in the 200 lines of code

#

I think right now we need

the exact error message you get
what part of your code (client-side or server-side) is returning that error
the exact PaymentIntent id associated with the error

frail seal Jul 17, 2024, 4:12 PM

#

Thanks;

"Processing error" client-side, "payment_intent_unexpected_state" with more info on the request id req_WB20yNbQuS9dQO,
from the api logs in the stripe dashboard
from stripe dashboard, but it is the client-side implementation of the pyments element that makes the confirmIntent() call
pi_3Pda5RGppVLMkw060IKO9N6Z

stable lava Jul 17, 2024, 4:12 PM

#

from stripe dashboard
what does that mean? the Dashboard can't really cause an error like that

frail seal Jul 17, 2024, 4:13 PM

#

it isn't; the error was found in the api logs in the stripe dashboard, after investigation of the simple "processing error" stripe returns for the payments element

#

so the error is seen on req_WB20yNbQuS9dQO, where it states:
"You cannot confirm this PaymentIntent because it's missing a payment method. To confirm the PaymentIntent with cus_QUZBSIJ8ULQZPY, specify a payment method attached to this customer along with the customer ID."

stable lava Jul 17, 2024, 4:16 PM

#

Okay so that happens client-side when you are confirming the PaymentIntent by calling confirmPayment()
Your code is not passing elements properly I think. You are doing const {error} = await confirmIntent({ stripeElements, clientSecret, confirmParams: ... but I think it should be const {error} = await confirmIntent({ elements: stripeElements, clientSecret, confirmParams: ...

frail seal Jul 17, 2024, 4:17 PM

#

Checking now

#

doing that there are no errors, but the new customer has a new subscription assigned to it, but no payment method...

stable lava Jul 17, 2024, 4:23 PM

#

It's all good, you'll get there, one step at a time. Can you share exact information what you mean by "no payment method"? If you could share the exact Subscription id and the exact Customer id I can have a look

frail seal Jul 17, 2024, 4:26 PM

#

Thank you,
Subscription id: sub_1PdaZPGppVLMkw06VtjXyXlw
Customer id: cus_QUZircVMFXfRVz

stable lava Jul 17, 2024, 4:51 PM

#

Damn I'm sorry I replied but in the wrong thread 🤦‍♀️

#

Okay so that Customer is created on your server. That Subscription is created with the underlying PaymentIntent.
As far as I can tell you never confirmed that PaymentIntent client-side. So add logs before and after your confirmIntent() call to figure out what's going on

frail seal Jul 17, 2024, 4:52 PM

#

Hahha it happens to the best of us!
I'll add logs before and after, run some tests and reply here when I am wiser on what is going on

stable lava Jul 17, 2024, 4:53 PM

#

sounds good

frail seal Jul 17, 2024, 5:22 PM

#

so i did some refactoring of the code, and it seems it never fired properly. Now however I am getting the following error as a response from Stripe running stripe.confirmPayment(): You specified "never" for fields.billing_details.name when creating the payment Element, but did not pass confirmParams.payment_method_data.billing_details.name when calling stripe.confirmPayment(). If you opt out of collecting data via the payment Element using the fields option, the data must be passed in when calling stripe.confirmPayment().
Do I need to supply a name of the customer, or am I misunderstanding something, and in any case can't it be inferred from the customer object when creating the subscription tied to that customer?

stable lava Jul 17, 2024, 5:24 PM

#

If you explicitly pass never then you tell us "never collect it, I will give it to you instead" so you have to explicitly pass it

frail seal Jul 17, 2024, 5:26 PM

#

okay, the reason for my setting it to "never", is that i do not want a field to appear asking for anything but the card data, since we have everything else on file in the database of the logged-in session (e.g. the user trying to subscribe).
should i pass all the details to confirmPayment (email, name, address.postalcode, address.country etc.), or can I make stripe reuse the data from the custoemr object?

stable lava Jul 17, 2024, 5:27 PM

#

yes you should pass it on confirmPayment()

frail seal Jul 17, 2024, 5:29 PM

#

okay, I'll try some more and get back to you 🙂

#

if i set the payments element to "never" for address, i need to supply line1 and more. I have instead chosen to set address.country to "never" and supply it in confirmPayment() instead. Can I be sure stripe does not create a field for name, phone, email and the such, if that data is already created on the customer object associated with the subscription?

#

also a few questions remain:

the subscirtption is now confirmed with the payment intent as expected, so that issue is resolved. now I can see, that the default payment method is not tied to the customer, just the subscription. Initially i followed Stripe's guide to create the intent before the payments element, where it successfully tied the default payment method to the customer, but now after having followed the guide to create the payments element before the intent, it no longer does.
automatic tax calculation has been disabled for some reason, but I want to show the price of the subscription excl. vat taxes, and the taxes themselves on the invoice from stripe, but now it only invoices the amount without vat

stable lava Jul 17, 2024, 5:40 PM

#

Can I be sure stripe does not create a field for name, phone, email and the such, if that data is already created on the customer object associated with the subscription?
no you can't be sure. We definitely do that already for payment methods that require this. Some need a name, other a full address, others an email. And PaymentElement collect what's required so it doesn't collect name or address for card.
So if you really want to avoid re-collecting you should disable them all and explicitly pass all the information on confirmPayment()

frail seal Jul 17, 2024, 5:40 PM

#

roger that

#

did you see my other message? 🙂

stable lava Jul 17, 2024, 5:48 PM

#

yep sorry cycling through threads

#

now I can see, that the default payment method is not tied to the customer, just the subscription
yes that's expected behaviour. You configured it explicitly when you created the Subscription. We don't support automatically making the PaymentMethod the default on the Customer, it's always on that specific Subscription that you are confirming the PaymentIntent for.

#

automatic tax calculation has been disabled for some reason, but I want to show the price of the subscription excl. vat taxes, and the taxes themselves on the invoice from stripe, but now it only invoices the amount without vat
I'd need another concrete example to look at and I would need the exact code that creates the Subscription

frail seal Jul 17, 2024, 5:53 PM

#

$stripe->subscriptions->create([
            'customer' => $customerId,
            'items' => [[
                'price' => $planPriceId,
            ]],
            'billing_cycle_anchor_config' => ['day_of_month' => 31],
            'proration_behavior' => 'create_prorations',
            'payment_behavior' => 'default_incomplete',
            'payment_settings' => ['save_default_payment_method' => 'on_subscription'],
            'expand' => ['latest_invoice.payment_intent', 'pending_setup_intent']
        ]);

#

thank you for your time and help. above is the code that creates the subscription

stable lava Jul 17, 2024, 5:55 PM

#

okay so you didn't enable automatic tax calculation there right?

#

You're missing automatic_tax as documented here https://docs.stripe.com/tax/subscriptions I think

frail seal Jul 17, 2024, 5:56 PM

#

sorry, it must've gotten removed when i refactored the code. Have a great rest of your day, and thanks again!

#datter_paymentelement-subscription