#swe_api
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/1306916519229521971
๐ 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.
Hi, let me help you with this.
What kind of emails do you mean exactly?
When PaymentIntent's receipt_email is set, an email will still be sent regardless of settings: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-receipt_email
I am talking about direct debit - pre-debit and mandate emails. These emails are mandatory in Stripe according to compliance
Then they will be sent regardless of settings.
We want to send the predebit emails from our end, we do not want Stripe to handle those emails for us.
What do you suggest in that case?
Oh, sorry, my bad. It seems like you can control it via Dashboard settings: https://docs.stripe.com/payments/sepa-debit#debit-notification-emails
But, source level settings took precedence over dashboard settings in intents API ๐ค
We want to understand how do I disable the notification for source tokens converted to payment methods.
Even in intents API, we want Stripe not to handle notifications for us for existing source tokens.
It says
Turn off Stripe emails in the Stripe Dashboard email settings. However, if you use the Sources API, you can only control emails using mandate.notification_method
It seems like for Sources it ignored the Dashboard settings completely.
For Payment Methods I believemandate.notification_methodwill take higher precedence since it's more specific.
Since they're migrated, they will work just like other PaymentMethods.
But, there is no field in payment methods to get this value - mandate.notification_method
How do I know what notification method is used for PM Token
Indeed, sepa_debit options doesn't seem to allow you to choose it: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_options-sepa_debit-mandate_options
Since it always collects the email address, it will send out predebit notes via email. And you should be able to control it via Dashboard Settings.
Irrespective of past settings in source token? I am talking about the use case where the source token is migrated to payment method.
๐ taking over for my colleague. Let me catch up.
Sure,
are you using PaymentIntents or SetupIntents?
We are using payment intents
the notion of mandate.notification_method is only available for sources since you can create the source without the presence of the customer on session
with new setup you have now, you don't need that since the customer is on session and would know what to expect for the mandate
in all cases, you can send the customer https://docs.stripe.com/api/mandates/object#mandate_object-payment_method_details-sepa_debit-url which details the specifics of their mandates
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Thsi is not about mandate, it's about the pre debit notification. If the notification is disabled at Stripe, it means that it won't be sent right?
irrespective of the settings at source?
there won't be a source in the PaymentIntent/PaymentMethod integration
yes that's correct