Overview  

APX widget integrated into a non-Amazon branded subsidiary

• Widget skinned to match client brand/style
• Option 1: API based summary with widget based selection.
• Option 2: Widget based selection and summary. (preferred)
• Option 3: Additional reconfiguration recommendations.

Supplemental Axure Documents  

Twitch.com virtual currency workflow using APX widgets

(some browsers may require plugin)

In Detail  

     Similarly to adapting our Amazon Payment Experience (APX) widgets to internal clients who had experiences that varied from Amazon retail checkout, Amazon also owns a host of non-Amazon branded subsidiaries with their own payments experiences and often entirely remote payment services. An aspect of the APX project was to transition them onto the more secure Amazon payment services by integrating the APX widgets into their payment related workflows.

     The challenge was not only to style and adapt the widgets to fit the new brand but often a conceptually different architecture for payment methods, addresses, and purchasing. This required deep changes in core concepts and transitioning to other non-payments Amazon services.

     Here, we work with Twitch.com, a media streaming service, to integrate APX widgets into their virtual currency purchase workflow.   This design assumes account creation merging with Amazon and messages the use of Amazon Payments as a trust increase. I’ve matched the widget styling to the existing site design and made notes for what elements I adjusted. Twitch would then own their own stylesheets within the Amazon User Interface (AUI) universal styling architecture so that the widgets would automatically adapt as their site’s design changes over time.

     I propose three models for integration:

     1) The first allows the client to query existing preferences through an API and construct their own payment selection summary with their own purchase button. Payment selection would be handled through the use of an APX widget. It’s understandable that a subsidiary would desire to own as much of their page as possible. I included this option by request.

     2) The second option uses the APX payment selection summary widget and APX payment method selection. An API based query lacks the complex logic of the APX summary widget which can understand available options and seed preferred methods and construct complex summary displays if they choose to move to a multi-tender approach in the future. It also enforces display patterns associated psychologically with Amazon trust. This is our preferred approach.

     3) In Twitch’s existing workflow, the purchase summary exists on the left and the primary purchase button appears underneath the payment selection summary to the right. On Amazon we have experienced a higher conversion with the purchase summary on the right with the purchase button at the top of that summary. For advanced features it is also helpful to group the purchase summary and purchase button together so that features that act on the purchase event and subsequently the purchase summary exist in the same column. For example, the obligation to change purchase button text when TFX Currency Converter is enabled. The third option flips the columns and moves the button into a more efficient configuration. This is the design we would like to work towards but the decision is up to the client. The widgets support all models out-of-the-box.