#adam_sepadebit-migration
twilit sphinxBOT
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.
- adam_api, 2 hours ago, 13 messages
uncut sparrowBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253360060298559590
đ Have more to share? Add details, code, screenshots, videos, etc. below.
balmy kernel
And we have to do it this way - as we can't do it using the sources API going forward, right ?
autumn turret
Correct
balmy kernel
Is this some sort of SEPA thing ? Or a Stripe thing ? Does it matter what value we pass for the email as long as it's valid ?
We currently have 33 customers actively paying by Stripe sepa debit for whom we have no email address - and for whom getting an email will be tricky if not impossible
autumn turret
It's a sepa rule, and it needs to be their actual email: https://docs.stripe.com/payments/sepa-debit#debit-notification-emails
balmy kernel
So when we come to use the migration tool (to migrate all our sources to setup/payment intents) will the ones without an email address not migrate ?
uncut sparrowBOT
whole needle
hi! if you have a customer like that the tool won't migrate it and gives an error about it in the output.
velvet vector
adam_sepadebit-migration
whole needle
if it helps :
RECOVERABLE: A usable contact email could not be found. Check for unexpected strings, correct suffixes (.com, .net, etc.), and leading/trailing whitespace if the email isn't noticeably incorrect. Please set the correct email on the Source owner hash or the attached Customer and then re-run the tooling. See https://docs.stripe.com/api/sources/update#update_source-owner-email or https://docs.stripe.com/api/customers/update#update_customer-email for reference.