#amrita_error

1 messages · Page 1 of 1 (latest)

shrewd tideBOT
#

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

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

blissful wasp
#

Still looking into this

cyan glacier
#

Thank you, let me know if I can provide any more info

blissful wasp
#

Ah, it's because the functionality is considered a public preview so access is controlled via API version:

You can use this public preview feature by including the version header 2025-04-30.preview or higher in your API request.
The beta SDK will use a .preview version, the non-beta does not

#
  • 2025-05-28.preview
  • 2025-06-30.basil
#

Until that feature is out of preview, you'll need to use the beta SDK/.preview version

cyan glacier
#

Can I use the feature with any non-beta version? We need to pass this L2/L3 data in production, so hesitant to switch to .preview version.

Previously we were passing level3 field of PaymentIntent with the L2/L3 data, with Stripe Go SDK v82.3.0. The level3 is not documented in v82.3.0 of the SDK (https://docs.stripe.com/api/payment_intents/object?lang=go), my understanding is that this was a preview feature that was possible to use with the non-beta version

The PaymentIntent object | Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

blissful wasp
#

Previously we were passing level3 field of PaymentIntent with the L2/L3 data, with Stripe Go SDK v82.3.0.
Do you have an example?

cyan glacier
#

Yes, log req_vFelQNqsi5q3AK

blissful wasp
#

Thanks, seems like this may have changed in the past few days then?

cyan glacier
#

Not sure. The level3 field doesn't support Unit Of Measure and Commodity Code fields. The doc for Level3 is marked as deprecated (https://docs.stripe.com/level3); I'm not sure when it was deprecated. The new fields Unit Of Measure and Commodity Code are available in AmountDetails and PaymentDetails fields of PaymentIntent.

Starting 17 October 2025, Visa will apply stricter data monitoring standards as part of their new Commercial Enhanced Data Programme (CEDP). Under the new standards, to keep the L2/L3 rates, we need to pass the Unit Of Measure field and Commodity Code. That is why I am trying to migrate away from level3 field of PaymentIntent, and trying to use the new AmountDetails and PaymentDetails field.

blissful wasp
#

I think you're going to need to write in to us and we can investigate this further. Something seems to have changed and I can't pinpoint exactly what

#

Your account has the level3 gate which was required until recently. But this transition to the public preview seems to have removed access to the feature for accounts with that gate

shrewd tideBOT
#

Hello @cyan glacier, we have sent you a direct message, please check it at https://discord.com/channels/@me/1398241806780465153

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
cyan glacier
#

Ok, thank you!! I will open the support case, thanks for your help!! 😄

blissful wasp
#

That URL will route directly to our team and we'll take it from there