
staveau • about 9 years ago
MasterCard Developer Zone links
We believe that developers who use MasterCard APIs should be treated differently than the rest. That is why we are pleased to offer prizes, complete with available power-ups, to those who use MasterCard APIs during the TechCrunch Disrupt Hackathon on September 6th and 7th, 2014.
Prizes:
•Best use of MasterCard API earns each team member (up to four members) a $400 MasterCard gift card, usable wherever MasterCard is accepted.
Prize Power-Ups:
◦+$100 per team member if the Simplify Commerce API is used
◦+$300 per team member if two or more MasterCard API services are used
•Each member of the runner up “best use of MasterCard API” team (up to four members) will receive a $200 MasterCard gift card.
And to make it transparent, our judging criteria will be quite simple.
- Business Value: Value to MasterCard and its key stakeholders (e.g. consumers, issuers, merchants and other partners)
- Creativity: How well does this improve the current retail experience? How have you leveraged the Simplify Commerce platform to develop a novel and user-friendly product?
- Completeness of Solution: Does the solution encompass aspects to advance the concept to the next stage?
For these MasterCard specific prizes, MasterCard team will be judges. We will be there to help you during the length of the event. We will be walking around or be available at our table to answer your questions.
Of course, a hackathon would not be complete without free t-shirts and swag, so be sure to check in with an onsite MasterCard Developer Zone team member for additional gear!
In order to make sure you can hit the ground running during the hackathon and read through service documentation in advance, we recommend that you register at the following links:
Featured API: Simplify Commerce
https://www.simplify.com/commerce/login/signup
MasterCard Developer Zone
https://developer.mastercard.com/plugins/user-registration/user-registration.action
We look forward to seeing you at the event!
Comments are closed.
0 comments