#milan_api
toxic sealBOT
👋 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/1427432064327745536
📝 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.
- milan_unexpected, 4 days ago, 21 messages
unkempt shard
hello! fyi i am looking into this now
i think you should be able to pass this in via the payment_method_data.billing_details.address.postal_code call (docs)
is there any chance you have an example request ID so i can look at how you're creating and confirming your PaymentIntents currently?
keen nacelle
Trying now. I don't see that via SDK so I'm trying via AddExtraParam()
Magic! That worked. pi_3SHv2pDFt6iTMCHH0UY8zswC
And you do recommend automatic_async for running a standard transaction correct? That was another recommended change.
Unrelated note before we get back to work -https://www.youtube.com/watch?v=hywLF1IbReI
unkempt shard
And you do recommend automatic_async for running a standard transaction correct?...
yep! automatic_async is currently the default because it has lower latency vs automatic. obviously if you have a use case that requires manual capture it's fine to stick with that.
https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method
unkempt shard
Unrelated note before we get back to work -https://www.youtube.com/watch?v=hywLF...
hehe neat
keen nacelle
Great! Thank you.
Question 2 - Any updates on the nuget package? We're being told we need to switch to the level3 items now, but the nuget package doesn't support it yet. How do we proceed?
(and I sent you the wrong link. the spacex one is better and it's ahead a few minutes)
unkempt shard
Great! Thank you.
Question 2 - Any updates on the nuget package? We're being to...
i am less sure about this, give me just a bit to double check some things for you
just double checking, are you referring to this public preview feature?
https://docs.stripe.com/payments/payment-line-items
keen nacelle
Yes
Now I could just use the AddExtraParam() approach to modify our request, however, I don't see how to change the version header in the request using the nuget package. Maybe that is an easier approach if that's possible.
unkempt shard
i am preeeetty sure AddExtraParam() is necessary here, but i have to admit the .NET SDK is one of the ones i am less familiar with so i am currently researching the recommended path here
have you already tried out the examples provided in the guide? e.g. this one
curious if you're getting an error if so
keen nacelle
I can use that, but I have to change the version in the header first, don't I? I haven't tried without that
unkempt shard
the examples in the doc don't include the version change, so i would maybe just give that a go real quick and see if it works
i'm working on spinning up a test of my own right now
keen nacelle
Ok. I'm retesting the other change with the postal_code. I'll move to that in a minutes.
Oh and I have another difficult question for you after we finish this one.
If you have time today
toxic sealBOT
keen nacelle
I just tried this with the current version header and Stripe's API doesn't recognize payment_details.order_reference
It looks like the only way to make this work is to update the header on the request. However, the nuget package doesn't have the preview header (the current one is Basil, I believe).
plush olive
Hi there, taking over and catching up. Could you give an example how you are updating the request header?
keen nacelle
That's the thing. I don't see a way to do that via the .NET SDK.
I think if there was a way, I could get this working. Is there a way that I'm missing?
plush olive
I think that's not possible
Because stripe-dotnet is strongly typed, the requests you send align with the API version current at your stripe-dotnet version’s release time.
Let me look around
keen nacelle
Otherwise, we have to pull down the SDK, compile it and check it into our source....or deploy it as a private nuget. Either is too much just to make this work.
Ideally, Stripe pushes back this hard deadline until their SDK is ready. It doesn't make sense to have a hard deadline on a preview.
plush olive
v49.1.0-beta.1 supports 2025-09-30.preview so it should be able to cover 2025-04-30.preview for the feature
keen nacelle
Right, but that introduces the issue I cited in my comment above.
plush olive
Yeah I agree.. dotNEt is a strong typed language and we need to anchor a different SDK version for a different API version :/
keen nacelle
So is there another option? Or can Stripe just wait until this is out of preview to make it a requirement? It seems a bit unrealistic to force this when it's in a preview state.
I have to step away but please let me know what your suggest would be. I'm hoping they just move back the date....or update nuget. Either would be the customer-friendly approach.
Thank you for your help. I'll catch up on this later.
plush olive
Sorry, I am confirming and it looks like this is the case unfortunately. You need a beta SDK version for the preview API version, and need a preview API version later than 2025-04-30 to enable Payment line items
Have a good night! Feel free to open a new thread when you are back and we would be happy to continue to help
keen nacelle
I'm back and I was able to pull down the preview version of the nuget. However, I'm getting an error stating payment_details.order_reference isn't recognized.
Received unknown parameters: payment_details.customer_reference, amount_details.shipping.amount, payment_details.order_reference
Ignore that. I think I figured it out.