Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not attempt application fee refund if refund was not successful #3206

Conversation

jasonwebster
Copy link
Contributor

This was a regression made in adc5a88
which was trying to make the App Fee refunds not impact the overall
status of the Refund response. That was achieved, but it also made the
unintentional change of always trying to refund the application fee
regardless of the refund succeeding or not. There was previously no test
coverage of this behaviour.

@jasonwebster jasonwebster requested a review from Senjai May 1, 2019 17:29
This was a regression made in adc5a88
which was trying to make the App Fee refunds not impact the overall
status of the Refund response. That was achieved, but it also made the
unintentional change of always trying to refund the application fee
regardless of the refund succeeding or not. There was previously no test
coverage of this behaviour.
@jasonwebster jasonwebster force-pushed the fix_stripe_failed_refund_fee_refunds branch from 80ac2bb to c28cabb Compare May 2, 2019 17:41
@jasonwebster jasonwebster merged commit e860ede into activemerchant:master May 6, 2019
@jasonwebster jasonwebster deleted the fix_stripe_failed_refund_fee_refunds branch May 6, 2019 15:40
whitby3001 pushed a commit to whitby3001/active_merchant that referenced this pull request Sep 3, 2019
…ctivemerchant#3206)

This was a regression made in adc5a88
which was trying to make the App Fee refunds not impact the overall
status of the Refund response. That was achieved, but it also made the
unintentional change of always trying to refund the application fee
regardless of the refund succeeding or not. There was previously no test
coverage of this behaviour.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants