Building reliable payment systems and services

##About the conference
Payments have evolved significantly since the evolution of smartphones and the rise in digital goods. Integrating payments inside your app or web service can either be a daunting task or easy to deploy, depending on who you partner with.

How can you build reliable and scalable systems within such a mesh simultaneously governed by compliance standards?

##We’re looking for talks or workshops broadly on the following topics:

1. Dealing with failure in service availability.
2. Tackling failure and integration challenges with legacy banking technology
3. Frameworks and solutions available for building wallets apps.
4. Web services
5. Building infrastructure in compliance with PCI standards.
6. Interoperability between services.
7. Facilitating escrow.
8. Building for B2B AND B2C - Getting started
9. Tools to handle stored payment data in terms of reliability, robustness and security.

##Target Audience:

1. Engineers.
2. DevOps practitioners.
3. Product managers.
4. CTOs.
5. CEOs and startups.

##Format
Single day, single track conference.
We are inviting proposals for:

• Full-length 40 minute talks.
• Crisp 15-minute talks.
• Sponsored sessions, of 15 minutes and 40 minutes duration (limited slots available; subject to editorial scrutiny and approval).
• Hands-on workshop sessions, 3 and 6 hour duration.

##Selection process
Proposals will be filtered and shortlisted by an Editorial Panel. Please make sure to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience and delivery style. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the Editorial Panel better judge your proposals. We might contact you to ask if you’d like to repost your content on the official conference blog.

We expect you to submit an outline of your proposed talk – either in the form of a mind map or a text document or draft slides within two weeks of submitting your proposal.

You can check back on this page for the status of your proposal. We will notify you if we either move your proposal to the next round or if we reject it. Selected speakers must participate in one or two rounds of rehearsals before the conference. This is mandatory and helps you to prepare well for the conference.

A speaker is NOT confirmed a slot unless we explicitly mention so in an email or over any other medium of communication.

There is only one speaker per session. Entry is free for selected speakers. As our budget is limited, we prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. HasGeek provides these limited grants where applicable: two international travel and accommodation grants, three domestic travel and accommodation grants. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer). Speaker travel grants will be given in order of preference to students, women, persons of non-binary genders, and individuals for Asia and Africa first.

##Commitment to open source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a “sponsored session”.

##Important dates:
Deadline for submitting proposals: 15 April, 2017
Conference dates: 8 July, 2017

##Contact
For more information about speaking proposals, tickets and sponsorships, contact info@hasgeek.com or call +91-7676332020.