When calling DoRefund on a transaction, it depends upon the platform used to see if the refund will work. To quote Kier: "It is the right method but transactions on the test platform at being processed by our dummy operator "TESTPAY" (until BlueVia is available) for which there is no refund agent, hence the not supported response." "In reality there are relative few operators that support refunds via an API call, so this scenario is not unlikely. Using refundType BANGO is an option, but the experience isn't wholly satisfactory as the user might not understand what this means." We should filter the refund operations by the operators that will support refund. Can someone tell us which operators will support refunds?

My understanding is that Mozilla will have a DoRefund call to Bango. The refund API between Bango and Bluevia/OB may vary or not exist, but from the Mozilla point of view there will be a refund and shouldn't need to know about each operator. How that gets handled, whether automatically or manually, is a logistics mechanism between Bango and Bluevia. Is that right?

(In reply to David Bialer [:dbialer] from comment #1) > My understanding is that Mozilla will have a DoRefund call to Bango. The > refund API between Bango and Bluevia/OB may vary or not exist, but from the > Mozilla point of view there will be a refund and shouldn't need to know > about each operator. How that gets handled, whether automatically or > manually, is a logistics mechanism between Bango and Bluevia. Is that right? That's my understanding

If you click refund without operator support we just show an error.