Up to now we have described the following user experience for third party apps
User pushes a "buy button" on the merchant site. This causes the browser to display matching apps (or their instruments)
The user selects an app and the browser hands control to the app.
The user then selects a way to pay from within the app.
It has been pointed out that when there is only one match, it would be a bad user experience to have to select the same information twice. Therefore, it has been suggested that, in essence, we combine 2 and 3 above into a single selection when there is just one match.
I don't yet know whether this should be a requirement; my guess is that it should not be, but that everyone will seek the improved user experience anyway. The question is: what information is required (if any) to enable this better user experience? What does the specification need to say?
For example, if we support the ability of mediators to display specific payment instruments (e.g., by showing a card nicknamed "My favorite credit card") then ideally I should be able to click on that
in the mediator to complete payment. One way this could work would be that when I click, the mediator hands off control to the third party payment app, which immediately returns data given the payment method in question (a credit card). So step 3 turns out to "still exist" but it happens without additional user interaction.
Is this how others view third party payment app interactions working?
adrianhopebailie
commented
8 years ago
Up to now we have described the following user experience for third party apps
It has been pointed out that when there is only one match, it would be a bad user experience to have to select the same information twice. Therefore, it has been suggested that, in essence, we combine 2 and 3 above into a single selection when there is just one match.
I don't yet know whether this should be a requirement; my guess is that it should not be, but that everyone will seek the improved user experience anyway. The question is: what information is required (if any) to enable this better user experience? What does the specification need to say?
For example, if we support the ability of mediators to display specific payment instruments (e.g., by showing a card nicknamed "My favorite credit card") then ideally I should be able to click on that in the mediator to complete payment. One way this could work would be that when I click, the mediator hands off control to the third party payment app, which immediately returns data given the payment method in question (a credit card). So step 3 turns out to "still exist" but it happens without additional user interaction.
Is this how others view third party payment app interactions working?
Ian