#ermahgherd
magic lynx
jovial seal
Are these invoices tied to a pre-existing subscription?
native falcon
New subscription. Customer gets error The payment is blocked due to a high likelihood of chargeback. You can learn more about this at https://support.stripe.com/questions/sepa-debit-chargebacks-faq
No risk evaluation.
jovial seal
Subscriptions that were created with the price prior to it being archived will be unaffected. However, you won't be able to create new subscriptions with that price after it's archived
Above should be unrelated to price archiving
Can you share the Payment Intent?
Or invoice id
jovial seal
Ah yeah looks like it's due to our new mitigation efforts described here: https://support.stripe.com/questions/sepa-debit-chargebacks-faq
native falcon
What's the reason code?
jovial seal
I don't know that there is one. Unfortunately I'm not an expert on this payment method type, and declines generally are better questions for our support team, so I recommend reaching out there for a more clearcut answer: https://support.stripe.com
native falcon
Okay. BTW, I get it's safe to dump id's in public chats?
jovial seal
Stripe object id's are safe to share and aren't sensitive. Things like webhook endpoint secrets and api keys aren't safe though
native falcon
obviously not publishable keys...
jovial seal
But just payment intent ids, invoice ids, payment method ids, checkout sessions, etc are totally fine