BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$50‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Amazon FPS Tester AppWireframe Contest. The goal of this contest is to create a wireframe for a small testing web application that will fully demonstrate the functionality of Amazon Fliexable Payments Service (Amazon FPS) component.

Round 1

For Round one you need to submit pages for the following :

  • Configuration
  • Charge Scenario 1
  • Charge Scenario 2
  • Notification

Round 2

For Round two you need to submit all pages of round in addition to all remaining pages and all subpages.

  • Configuration
  • Charge Scenario 1
  • Charge Scenario 2
  • Charge Scenario 3
  • Charge Scenario 4
  • Notification
  • Logging

Overview
Amazon Flexible Payments System is a payment system like Paypal or Google Checkout, but with better support for complex payment scenarios, such as a deferred or recurring payment. We designed and are currently developing a component to support easily using Amazon FPS.

Goals and Requirements
The goal of this contest is to build a wireframe for a small web application that will be a way to test out and demo the functionality of the Amazon Flexible Payment System Component.

Note that you do not need to review the design of the component for this wireframe, you only need to understand the functionality that is supported. You can see the supported functionality by reviewing the component spec here.

Scenarios

The scenarios we want to demo are the folowing :

  • Scenario 1. The client is immediately charged with specific amount (just once). Later the charged payment can be refunded.
  • Scenario 2. The client is immediately charged with specific amount. later the client can be charged with fixed authorized amount. Also both charged payments can be refunded later on.
  • Scenario 3. The client is immediately charged with specific amount. Later the client can be charged with variable authorized amount. Also both charged payments can be refunded later on.
  • Scenario 4. The payment amount is reserved for the client immediately. Later the reservation can be settled or cancelled.
Flow
The common flow of the listed 4 scenarios is  :
  • Get Payment Authorization : This results into redirecting the client to a CO-Branded UI page hosted by Amazon to authorize the payment.
  • Process Payment Action : This can be processing multiple payments, reserve funds and settle or cancel it later, refund completed payments.
  • Process Payment Notification : This is sent when a payment action succeeds or fails.
Required Pages
We want to build a set of pages to demo the listed 4 scenarios :
  1. Configuration: On this screen the user can set their AWS credentials (required) and configure a JMS queue (optional).
  2. Charge Scenario 1: On this screen the user can test out charging a client immediately, and also refunding an existing charge immediately.
  3. Charge Scenario 2: On this screen the user can test out charging a fixed amount, authorize a future amount to charge, initiate the future charge and refunding an existing charges.
  4. Charge Scenario 3: On this screen the user can test out charging a fixed amount and authorizing a variable future charge, initiate a variable future charge and refunding an existing charges.
  5. Charge Scenario 4: On this screen the user can test out reserving a future (reseve) transaction, and can then either settle it or cancel it.
  6. Notification : On this screen the user can see the errors (like rejecting payment) and successful payment events.
  7. Logging: On this screen the user can see the logs generated by the component.
The FPS design component is attached for your reference if you would like to take deep look into the functionality.

Target Audience
This web application will be used internally by TopCoder PMs and Copilot to test the Amazon FPS functionality.

Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
All Requested Contest Requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fix
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2012 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30024912