1129627 - Implement failure url

Status: RESOLVED WORKSFORME

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Description

[Andy McKay]

We need to implement a failure url on Boku, so that when a failure occurs in Boku it is handled correctly. According to tech support, we will need to specify: fail-fwdurl.

So this bug is about:
* adding in the fail-fwdurl to the prepare call
* when a failure occurs we need to:
 * cancel the transaction in ui
 * mark the transaction as errored in solitude

Comment 1

[Andy McKay]

I've started passing through fail-fwdurl as noted in the doc. When we try to test a failure (e.g. MX11) we see the message: 

https://www.dropbox.com/s/fqaehg1t6d4vnco/Screenshot%202015-02-05%2012.09.17.png?dl=0

"No Spend Limit Message Configured"

Is this something we are expected to do?

Comment 2

[John Tan [Boku Merchant Support]]

"MX11" is a test number that results in the "No Spend Limit Message Configure" being returned.

Each test number results in a specific error being returned, except MX00 (which simulates a successful transaction) and MX03 (which goes to the In Progress / PIN entry screen)

Once you see the error, click the "CONTINUAR" button, and the fail-fwdurl screen will be displayed.

Comment 3

[John Tan [Boku Merchant Support]]

More on test numbers can be found in Appendix "A" of the Boku Technical Reference document.

Comment 4

[Andy McKay]

So on a device with a SIM with no money, what happens? I can't test this so does a message "No Spend Limit Message Configured" appear, or does something else appear?

Comment 5

[lsaunders]

From John 
"MX11" which leads to the "no Spend limit" error message being displayed test number "MX11" will only return "No spend limit configured"
If you had no balance left, you'd get a different error message
The error returned if you had no remaining balance would be MX02
"Sorry, we could not make payment. No charges were applied." or "Disculpe, no se pudo realizar su pago. No se aplicaron cargos."

Comment 6

[Andy McKay]

This works just fine for me on payments-alt. We bounce back to the waiting page. Boku sends the server to server signal, we mark the payment as cancelled. The suggestion from John is that the error message will be replaced by something sane for our end users.

This won't work locally in development because the server to server call fails.

I did: https://github.com/mozilla/webpay/pull/593 just to make me feel useful