After e-commerce, digital payments are again changing the way we buy and sell. As a developer you have a chance of building the app others will come to depend on.
HasGeek is organizing a new conference on the payments landscape, with a choice of topics bridging the gap between developers and business, merchants and buyers, and banks and regulators.
We are now accepting submissions around the theme of digital payments.
- Demystifying the payments landscape, specifically -
- Foreign exchange
- Cross-border funds transactions: what is legal, what is not?
- New developments in the payment landscape like:
- The Unified Payments Interface
- Future course
- Subscription billing
- Split payments?
- Operational guidelines
- Payment banks
- Use of chatbots by wallets as interface with customers
- Bitcoin and blockchain
- Ethereum, etc.
- AEPS (aadhar e-payment system)
- International payments in India
- The Unified Payments Interface
- Payments instruments
- At Point of Sale (POS)
- The smartphone as payment instrument:
- Identity verification
- Portability across platforms (Android, iOS)
- Resilience under loss of access to network
- Money transfer at POS (to a brick-and-mortar vendor)
- Structure, implementation, and effects of the ongoing demonetization scheme
- Workshops around open APIs from banks and PSPs
We are inviting proposals for:
Full-length 40 minute talks.
Crisp 15-minute talks.
Sponsored sessions, 15 minute duration (limited slots available; subject to editorial scrutiny and approval).
Hands-on Workshop sessions, 3 and 6 hour duration.
Proposals will be filtered and shortlisted by an Editorial Panel. We urge you to add links to videos / slide decks when submitting proposals. This will help us understand your speaking experience, and if further practice is required. 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 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.
We will notify you about the status of your proposal within three weeks of submission.
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 will provide a grant to cover part of your travel and accommodation in Bangalore. Grants are limited and made available to speakers delivering full sessions (40 minutes or longer).
50p will be held at the MLR Convention Centre, JP Nagar.
For more information about speaking proposals, tickets and sponsorships, contact email@example.com or call +91-7676332020.
Everyone can see your credit card details. Seriously.
Paying via Credit/Debit cards (or NetBanking) one huge leaky cauldron on mobile apps.
We have a new food delivery or clothing merchandise startup popping up every day, and those enormous discounts pull you into making purchases from them from the get go.
But when you put in your payment details in your random built-in-a-month startup-level-amateurly built app, you have no clue how many people are seeing your secure payment method details.
How are payments in mobile apps integrated these days :
- A startup builds an app (which doesn’t have basic security measures, saves keys in unencrypted flatfiles)
- They need to add payments wihtin 2 days . . so let’s use an SDK - Razorpay/Paytm/Zaakpay etc
- Use the SDK like a black box, just feeding it an API key
- The SDK uses a payment method like Freecharge/PayU/Paytm
- The Payment Wallet uses a payment fullfilment service like Juspay, Citrus
- That uses a bank gateway like ICICI/Citibank
- Oh wait, where does the app run ? Android.
- OEM has access to Android base classes and the runtime. Most OEMs are known to spy on users, some have virii.
- User’s phone could be rooted, have xPosed installed, could be using a VPN.
The list just goes on, for all the places from where the details could leak. The OEM can sniff any text entered or displayed in an app.If not the OEM, on a rooted app, anyone else can reflect into your Java classes and sniff data. The SDK can monitor the payment details. The payment fullfilment service works via a Webview, and they can too.
How compromised are we exactly when we pay using our cards/netbanking when buying that delicious chicken wrap from the latest food startup’s app ?
Arnav teaches Android and NodeJS at a programming bootcamp, Coding Blocks, in Delhi. He has been an avid Web and Android developer for over 5 years now, with contributions to many FOSS projects like Arduino IDE, CyanogenMod, the Linux kernel and even Google’s vanilla Android OS Project (AOSP).