Cross Platform Bank SMS Aggregator
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted7 hours ago
I would like to turn my idea into a production-ready mobile application that instantly tells my staff how much money has been transferred in, no matter which bank a customer used. The core flow is simple:
• A customer completes a transfer on their own phone.
• Our app, running on that same customer device during checkout, reads the bank’s confirmation SMS automatically.
• The amount, sender name and reference number are pushed to our cloud dashboard and merged with any other payments that have just come in, so the cashier sees a single, up-to-the-minute balance.
Scope and technical wishes
– The very first release must work on both Android phones and iPhones.
– Payment confirmation must be captured by reading the bank SMS automatically; manual entry or scans are only fall-backs for a later phase.
– Because the SMS originates on each customer’s handset, the app needs a permission flow that is quick, clear and secure.
– A lightweight back-end (your suggestion of Firebase, Supabase, Node.js or similar) will store the parsed messages and expose a real-time balance endpoint or WebSocket so my POS screen can stay in sync.
Deliverables
1. Cross-platform mobile app (single code-base preferred) that can:
• Request and obtain SMS-reading permission on Android.
• Implement the best possible alternative on iOS, given the OS restrictions, while keeping the user journey smooth.
• Parse major local bank SMS formats (I will supply samples).
• Post the extracted data (amount, sender, bank, reference, timestamp) to the back-end.
2. Simple web dashboard showing today’s total received amount and a running log of transactions.
3. Source code, build instructions and a short video walkthrough so I can demo it to restaurant and supermarket owners.
Acceptance criteria
• A test transfer SMS from any sample bank is reflected on the dashboard within five seconds.
• Duplicate messages are ignored; totals stay accurate after multiple simultaneous payments.
• No personally identifiable information is stored other than what appears in the SMS itself.
If you have prior experience with Flutter, React Native or Kotlin + Swift and know the quirks of SMS permissions, I’m eager to hear how you’d architect this and what timeline you foresee.
• A customer completes a transfer on their own phone.
• Our app, running on that same customer device during checkout, reads the bank’s confirmation SMS automatically.
• The amount, sender name and reference number are pushed to our cloud dashboard and merged with any other payments that have just come in, so the cashier sees a single, up-to-the-minute balance.
Scope and technical wishes
– The very first release must work on both Android phones and iPhones.
– Payment confirmation must be captured by reading the bank SMS automatically; manual entry or scans are only fall-backs for a later phase.
– Because the SMS originates on each customer’s handset, the app needs a permission flow that is quick, clear and secure.
– A lightweight back-end (your suggestion of Firebase, Supabase, Node.js or similar) will store the parsed messages and expose a real-time balance endpoint or WebSocket so my POS screen can stay in sync.
Deliverables
1. Cross-platform mobile app (single code-base preferred) that can:
• Request and obtain SMS-reading permission on Android.
• Implement the best possible alternative on iOS, given the OS restrictions, while keeping the user journey smooth.
• Parse major local bank SMS formats (I will supply samples).
• Post the extracted data (amount, sender, bank, reference, timestamp) to the back-end.
2. Simple web dashboard showing today’s total received amount and a running log of transactions.
3. Source code, build instructions and a short video walkthrough so I can demo it to restaurant and supermarket owners.
Acceptance criteria
• A test transfer SMS from any sample bank is reflected on the dashboard within five seconds.
• Duplicate messages are ignored; totals stay accurate after multiple simultaneous payments.
• No personally identifiable information is stored other than what appears in the SMS itself.
If you have prior experience with Flutter, React Native or Kotlin + Swift and know the quirks of SMS permissions, I’m eager to hear how you’d architect this and what timeline you foresee.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.