No way to test interactive redirect loop for adding card on staging

[dobey]

Sometimes, users are redirected to a 3dsecure or Verified by Visa external web site, when adding a credit card. Sometimes, there are issues with this process, and it can be very difficult to debug, as the requests seem arbitrary, and there is no way to force such an interactive process to happen when testing on staging.

I propose to introduce some logic in the staging server to allow basic testing of this, so that we can easily verify our server and client are behaving correctly as expected in this situations. This could be done in the following manner, if I understand correctly:

1) Check for presence of "TEST3DSECURE" (or a similar value) in the name field when submitting the Add Card form.
2) Upon presence of "TEST3DSECURE" in the form, redirect to a simple page elsewhere on our server which contains two buttons, Allow/Deny.
3) Upon pressing of either button, the page will redirect back to our current pages in the same way that a successful/failed 3dsecure request does in the real world.

Having such ability on the staging server would be extremely helpful in testing these scenarios.

[Vincent Ladeuil (vila)]

from irc:

<beuno> matiasb can provide details
<beuno> but it's SCA using Pay behind the scenes
<beuno> I suspect it'll be a bit of work in both places
<beuno> but SCA should be able to swap out payment providers

[Vincent Ladeuil (vila)]

So, according to Matias, the phone uses https://sc.staging.ubuntu.com/click/payment-method/add/

If I go there, logged in with sso, I can create a card.

If the holder name is 3D then on card creation a new page is presented
allowing one to chose between different scenarios:

- The error code is invalid. The order does not proceed to authorisation
- Authentication offered but not used
- Cardholder failed authentication
- The error code is valid. It is acceptable to proceed to authorisation
- Not identified. No XID received
- Cardholder authenticated
- Payment cancelled. The order does not proceed to authorisation
- Response validation failed. The order does not proceed to authorisation

Chosing 'Cardholder authenticated' led me to https://sc.staging.ubuntu.com/click/succeeded/?

This seems to match what this bug is aking for modulo s/TEST3DSECURE/3D/ ;)

@dobey: Can you confirm ?

[Vincent Ladeuil (vila)]

https://online.worldpay.com/docs/testing has some good bits related to testing

[dobey (dobey)]

It seems using "3D" as documented on Worldpay works for this, however it seems there is no link to these Worldpay docs (or even docs describing how to use staging for testing) exists in the pay docs. I think this Worldpay link, and how to perform tests on staging in our pay environment, needs to be included in the pay docs. If necessary, we can open a second bug for that and close this one as Invalid, but the docs issue is a bug.