Make it clear what "record refund" form does

[mattwire]

Overview

It was not clear to me if the "Record refund" form was capable of talking to payment processors etc. - it's not.

Before

Not clear as to whether this form might talk to a payment processor or not.

After

Clear:

Technical Details

Comments

@adixon @JoeMurray @eileenmcnaughton Just wanted to ping you here to check my assumption is correct? Eg. IATs doesn't have any overrides/hooks for that form that actually allows a refund to be requested for example?

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[adixon]

Yeah, worth making that clearer for sure. We've definitely been on side of not hooking into refunds at iATS for reasons of risk, but I'm not sure that's always true for other payment processors - I had thought you were working on something that allowed refunds in stripe via the civicrm web interface?

[mattwire]

@adixon Yes, I have a refunds UI via mjwshared - see https://docs.civicrm.org/mjwshared/en/latest/refunds/ but it doesn't use this form and it confuses me and clients who are using my refund UI. So this text helps clarify the difference.

[eileenmcnaughton]

seems fine - we can just make the text conditional if we add processor support