#Rob Coursera-ACH-refunds
1 messages · Page 1 of 1 (latest)
Do you have a the ID of a refund that is seeing that message?
Never mind. So here is a doc on how ACH credit transfer refunds work. The funds won't go back to the ACH credit transfer source, we send an email to the customer so they can enter their bank account info and get the funds back. The message you are seeing indicates that the refund is waiting on the customer to enter their bank account details https://stripe.com/docs/sources/ach-credit-transfer#refunds
@astral linden does that unblock you?
I see
So in the case of my test mode transaction, I did not receive an email
Is that because of test mode? Is there a way to get this email?
Refund in question https://dashboard.stripe.com/test/payments/pi_3JhcwXHz07ypukwL1ivfn386
you need to make sure you set the email associated with the Source to your own account/email address to get the email
Hmm, as you can see from the link, the associated customer is "rhealy@coursera.org", which is my email
Any other reason I did not receive an email?
This is the source in question https://dashboard.stripe.com/test/sources/src_1JhcwaHz07ypukwLIwugKT8g
yeah that's the thing, that's your email, not the email associated with that account (the owner) so it won't work
easiest is to create a separate account for just yourself and use the email for that account
Oh sorry, I am confused. In Pompeys message above, they state "we send an email to the customer so they can enter their bank account info and get the funds back"
Is the customer in this instance not my email address? That was why I expected to receive an email
Also, who is the owner here?
the owner is the customer
in Test mode, we don't send emails to any address, otherwise you'd spam real people by randomly testing email addresses
so the only case where we will send the email in Test mode is if the owner's email address (what would be the customer's email in production) is set to the same email address as the owner of the Stripe account
so in Test mode, as the developer, you test this by creating a Source that has the email address associated with the owner of the Stripe account and that email address will receive the email for a refund in Test mode
Ahh I see, sorry for the misunderstanding. thank you for the information. How do I see who is the owner of the Stripe account?
all good I didn't even know this myself (I asked a colleague and had to debug my own code to make it work)
https://dashboard.stripe.com/settings/team might have the information
(Depends on your own permissions)
Haha that's funny. I love a good nostalgic debug session
Hmm looking at that link, it just shows all the users. I am an administrator, but there are multiple
So what would deem someone an "owner" of the account?
one has the owner permission. I unfortunately can't tell you with on Discord.
Really my recommendation: create a separate Stripe account, it takes a couple minutes (no need to activate anything) and you can test this quickly
Okay I will give that a try. Finally I have a question about why I asked here in the first place.
We have multiple customers paying through our Stripe platform using ACH as their payment method. However, we recently had an issue where our support rep shared the wrong ACH bank details to a customer, and so one customer ended up sending funds to another customers Stripe ACH source.
This automatically paid that customers outstanding invoice. So now we are in a strange situation, because we can't just refund the invoice, using the information you have given me above, that would email the wrong customer for the refund.
What do you suggest we do to fix this situation?
that is really tricky unfortunately and I don't think there's any safe way to do this. It's something I'd expect you to discuss directly with Stripe support instead of here really
But at a high level the best option is likely to refund out of band for that one yourself as a company (outside of Stripe). Some hacks might be to change the email address for that specific source so that they get that email and then later you detach the Source and get a new one but that seems overly risky and complex to me. I don't think there's a good approach for cases like this