#akzentmayer_docs
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/1425234285698482256
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there,
can you share more details about the email you received?
For more context, we do not call PaymentIntent.create directly in our main implementation of Stripe
Are you using L2/L3 data in your integration anywhere?
I'm not sure how to tell that
You would be participating in the L2/L3 or Level 2/Level 3 program and potentially save card network fees.
Ok so I'd need to check with our finance team/Stripe account owner on whether or not we're electively participating in that already? The email makes it seem like we are, but I'm not sure if it the messaging was generic.
Would I be able to tell from the Stripe dashboard?
It sounds a bit generic. That is true. But if it turns out that you do, the email also recommends reaching out to Stripe support, which is a bit different than this discord channel.
Gotcha
Do you know whether or not these changes would apply to implementations that don't directly call PaymentIntent.create ?
I don't see how that would apply to subscriptions currently. But it's also only in a "public preview" state currenlty. So that might change in the future. Generally I would recommend reaching out to support to verify, that your account is not impacted by the changes mentioned in the email. They will be able to tell immediately if you participate in the program and can give further advice on what might need to be updated in your integration