#Reid

1 messages · Page 1 of 1 (latest)

rugged tundraBOT
cobalt estuary
#

Hi there

#

What type of payment method?

#

Card?

oblique glade
#

ACH. We have a system in place that handles our refunds for connect accounts, but one of our refunds failed. We have been unable to determine why it failed, so I was going to attempt to curl another refund ( without the charge_reversal ). I was testing this in the test mode to see if it would behave as expected.

cobalt estuary
#

It should be ~instant in test mode I believe

oblique glade
#

or reverse_transfer, I got that wrong.

cobalt estuary
#

When you say your "refund failed", did you see an error?

#

Do you have an ID I can look at?

oblique glade
#

I did one a few minutes ago, and all I see on the dashboard is Refund pending due to bank processing

#

Sure: py_1M5LMlFXc3zoUgUuBkGR2bPp

#

( this is the one in our non test env that is the reason I am attempting this )

cobalt estuary
#

Hmm I just tested refunding an ACH transaction in test mode and mine was instant (as soon as I refreshed page it switched from pending to refunded)

oblique glade
#

this is the one I did in test mode that is still pending: py_1MFipFKUAU7fxfqYaaAdC8hL

cobalt estuary
#

Huh yeah we don't expose the failure codes for ACH but that one failed for an "invalid account number"

#

Nothing is wrong with your integration here

#

If you see ACH refund failures that are unexpected, the customer will want to reach out to their bank to ask why the refund failed.

#

It is possible they closed their bank account for instance

oblique glade
#

The one in non test mode was for invalid account number?

cobalt estuary
#

Yes

#

That is the response the bank sent us

oblique glade
#

On the end of the customer that is recieving the refund?

cobalt estuary
#

Correct

oblique glade
#

Interesting. That is very good to know. I will level this up to our customer support people then because that is not something that curling a new refund for would fix. Thank you!