Allow refund() to raise RedirectNeeded?

[Natureshadow]

I am writing a payment provider where the user needs to interact to do a refund.

Could we allow providers to raise RedirectNeeded in their refund method, and make BasePayment pass this exception on to the calling view?

Actually, no code changes are needed to d othat I could just let my payment provider raise RedirectNeeded, and tell users of my provider that their views need to expect that.

So this issue is mainly to discuss whether there is something I should consider (instead, or in addition).

[WhyNotHugo]

Who is redirected in this case, the client or the merchant?

[Natureshadow]

Hi,

Who is redirected in this case, the client or the merchant?

The merchant. They are required to enter a TAN to authorise the refund. I don't know if the merchant actively starting a refund is the expected workflow, but that's how we do it here at Teckids: Someone calls in sick for an event or simething, and then we cancel/refund the payment. We rely on SEPA and FinTS, and that's where our bank will ask for a TAN.

…

-nik

[WhyNotHugo]

I can't imagine any scenario where the client initiates the flow on the merchant's website, so this seems reasonable.

I don't know if the merchant actively starting a refund is the expected workflow

It is.

This is a slight API change, but not backwards incompatible, since the change only applies to a new feature, so no objections on my part; BasePayment.refund may raise RedirectNeeded