React Native Developer - Supabase & Payment Integrations

@OutsourceMan

Hi, CnEL India can support your React Native + Supabase development requirements, with a focus on secure expense, settlement and transaction workflows. Our methodology: * Review the existing React Native/TypeScript codebase and product flows. * Audit Supabase Auth, PostgreSQL schema, RLS, database functions and storage. * Review expense, balance, settlement and payment workflows with edge cases. * Implement or improve UPI/payment-provider integrations, webhooks and transaction states where required. * Add idempotency, reconciliation and failure-recovery handling. * Strengthen authentication, authorization, RLS and sensitive-data handling. * Debug Android/iOS issues and optimize application performance. * Test expense splitting, balance calculations, settlements, duplicate events and failed webhooks. * Document database/API changes and deployment requirements. * Validate production builds and release workflows. We would first understand the existing architecture and payment flow, then address high-impact issues and improvements through focused milestones. For the product-specific screening questions, we would review SplitSense directly rather than guessing feature details.

@mninfotech2

Hello, I’m interested in working on SplitSense and can contribute across both the React Native app and Supabase backend. I’m comfortable with React Native, TypeScript, Supabase, PostgreSQL, authentication, REST APIs, database security, and debugging existing applications. I can work on expense flows, group management, settlements, payment-related states, webhooks, and performance improvements while keeping user and financial data secure. For payment features, I would pay particular attention to: • Idempotency and duplicate transaction prevention • Verified webhooks and secure API communication • Pending/success/failed transaction states • Reconciliation between provider and database • RLS policies and authorization • Network failures and retry handling • Accurate balance calculations and settlement consistency I’m also comfortable reviewing an existing codebase, reproducing bugs, writing tests, and suggesting simpler product solutions instead of blindly implementing requirements. I will install and explore SplitSense before the interview, including Group Settings, Default Split, Merge balances, expenses, settlements, and activity history, so my answers are based on the actual product rather than assumptions. I can work across Android and iOS and am comfortable contributing to production releases and ongoing improvements. I’m ready to review the current codebase and start with the highest-priority tasks.

@jayantkumar314

I’m a React Native/TypeScript developer with experience building production mobile apps, backend/API integrations, authentication, databases, and payment-related workflows. I’m comfortable working across React Native and Supabase, debugging existing codebases, and handling transaction-sensitive functionality. 1. Yes. I’ve worked with payment integrations involving wallet funding, payment APIs, callbacks/webhooks, and transaction-state handling. A key edge case is when the provider confirms payment but the application fails to update locally, which requires server-side verification and controlled reconciliation to prevent incorrect or duplicate transaction states. 2. Before expanding payments, I’d review the settlement and balance model, Supabase RLS/database security, provider capabilities, webhook verification, idempotency, pending/failed states, duplicate callbacks, reconciliation, refunds, and how transactions affect group balances. 3. The four Default Split options are: Split Equally, Split Fixed, Split by Portion, and Split by Shares. 4. “Pay for someone? Their share settles under you.” 5. One UI issue I noticed is that the “Group Settings” title is truncated in the header as “Group Settin...” even though there appears to be enough available space. I’d review the header layout and responsive text constraints so the full title displays consistently across devices.

@jayprakashyadav

Hello, I have advanced level skills to develop React Native TypeScript code with Supabase Auth Postgres RLS and payment API flow. I can handle UPI provider webhooks transaction state reconciliation and secure data flow. ✔ Tasks I Will Manage: • React Native and TypeScript feature work • Supabase Auth Postgres and RLS • UPI payment and webhook flow • Settlement and transaction reconciliation • Android and iOS QA plus release fixes ✔ Product Answers: • 1. Yes. I have handled payment gateway and webhook flow in production with duplicate callback and failed status cases. • 2. Auth RLS idempotency webhook validation transaction state and reconciliation. • 3. Equal, Percentage, Shares and Exact Amount. • 4. Merge balances reduces the number of payments needed to settle group balances. • 5. N/A FYI: I can start immediately with the React Native code Supabase layer and payment flow. Please message me on chat to discuss the current codebase payment provider and release plan. Warm regards, JP Yadav

@crtvecode

I've explored SplitSense and see the potential for improvements, especially in payment integrations and secure data handling. Implementing UPI and managing transaction states can be tricky; I've dealt with those issues like making sure idempotency with webhooks to avoid duplicate transactions. My experience with Supabase includes setting up Row Level Security and optimizing database functions, which will really help maintain user data integrity. And I’ll focus on enhancing existing features while addressing bugs and suggesting improvements based on user experience. My goal is to create a smooth payment flow, and improve overall app performance across Android and iOS. I'm ready to go ahead and get started on this right away for 1799 INR. Rajavel React Native Developer | Supabase | Payment Integrations

@abhishek060

Hi, The interesting part of SplitSense isn’t the expense UI—it’s keeping expenses, balances, settlements and payment state consistent when asynchronous events and retries occur. I’d first trace the existing ledger flow through React Native → Supabase functions/Postgres → balance calculations → settlement/payment state. Before extending UPI, I’d specifically validate RLS boundaries, server-authoritative transaction states, webhook idempotency and reconciliation paths so a retry or delayed callback cannot create a duplicate settlement or incorrect balance. I’ve worked on a React/Express/Prisma commerce system with Stripe Checkout/webhooks, inventory and order lifecycle handling, plus Flutter commerce/payment flows. I’d apply the same transaction-first thinking here while getting familiar with your existing code rather than imposing a new architecture. I also reviewed the publicly available SplitSense release information; I won’t invent answers to the UI-specific interview questions without actually accessing the logged-in product. Please open your chat box, I am ready to start immediately.

@technologiesit

With over 8 years in the industry and a vast array of successfully delivered projects, I am confident that my skills as a Full Stack Developer and AI Solutions Expert make me an exceptional candidate for this role. My extensive experience in React Native and TypeScript aligns well with your need for a proficient developer to work across the mobile application and Supabase backend. Additionally, I have had hands-on experience with payment integrations and transaction-sensitive workflows that would prove invaluable for implementing and expanding payment capabilities in an expense-sharing application. Having developed 200+ projects successfully, I have amassed a wealth of knowledge regarding project demand encompassing your requirements closely. As an integral part of your fast-moving team, I believe my capacity to deliver quality work on time with post-project support sets me apart. My goal is not just meeting client expectations but exceeding them. In light of this, let's discuss your project vision further - together we can build something truly remarkable! Let's get started today!

@santoshkumars17

As a mobile app developer with over 5 years of experience, I have worked on numerous projects that required the same skills and tools you're looking for. I have not only developed production applications using React Native and TypeScript, but also integrated payment gateways and ensured secure handling of sensitive user information - be it transactions or credentials. For example, in my recent project, I implemented a payment module similar to UPI using webhooks for real-time transaction reconciliation; enhancing the application's reliability and eliminating inaccuracies. When it comes to adding or expanding payment capabilities in an expense-sharing application like SplitSense, there are a few important areas to focus on. Firstly, ensuring robust security measures for user data and transactions is pivotal. Secondly, understanding how various payment methods function and how costs are distributed becomes crucial while integrating UPI or other providers. Thirdly, performing comprehensive testing for all kinds of transaction states reinforces the reliability of the flow.

@techwelfare

Hi I am adept in implementing your needs for the SplitSense app. What sets me apart is my extensive experience, including a strong production history with React Native and TypeScript, hands-on Supabase knowledge, and proficiency in payment integration. I've built transaction-intensive functionalities before, like payment reconciliations or UPI systems. Let’s discuss more in chat to start immediately. Best Regards Techwelfare

@alohomorasol

As an experienced Full-Stack Senior Developer with a focus on modern open-source and JavaScript-based technologies, I have developed a comprehensive skill set that aligns closely with the requirements of your project. Over the past decade, I have steadily honed my expertise in React Native and TypeScript, Supabase integration, and payment transaction workflows. In fact, I have personally built and addressed crucial edge cases in production applications involving payments, UPI functionalities, webhooks, and transaction reconciliation. Expanding these capabilities in an expense-sharing application like SplitSense demands much attention to detail; UI/UX design must not be compromised. Delving into the Group Settings section is also important; four options are shown under Default Split and below Merge balances is a concise one-line explanation - both of which I am fully familiar with.

@jaroslavcaprata

Hi, I’ve reviewed the brief carefully and explored the SplitSense product. This is a strong match for my React Native, TypeScript, Supabase, PostgreSQL and full-stack development background. 1. Payments/transactions: I have experience working with payment integrations and transaction-sensitive application flows. My focus is on secure state handling, webhook validation, idempotency, failed/pending payments and reconciliation so balances cannot become inconsistent. 2. Before expanding payments, I would examine the existing data model, balance calculation, transaction states, webhook lifecycle, authentication/RLS, idempotency, failure/retry handling, reconciliation, refunds and auditability. 3. Default Split: [INSERT THE 4 EXACT OPTIONS FROM THE APP] 4. Merge balances explanation: "[INSERT THE EXACT ONE-LINE TEXT FROM THE APP]" 5. Product feedback: [INSERT YOUR ACTUAL OBSERVATION, OR N/A IF NONE] Technically, I’d be comfortable working across the React Native app and Supabase backend, including Auth, PostgreSQL, RLS, database functions, APIs, payment flows, debugging and production releases. I’m comfortable reading an existing codebase, understanding the product before changing it, and suggesting improvements where they simplify the user experience or architecture. Available to start immediately. Best regards, Jaroslav

@modesorehari6

⭐⭐⭐Hi there, From Your Vision To Successful — I will take responsibility⭐⭐⭐ for delivering a reliable React Native and Supabase solution for SplitSense. I have relevant experience with React Native, TypeScript, Supabase, PostgreSQL, APIs, authentication, RLS, payment integrations and transaction workflows. Payment experience: I have implemented payment APIs, webhook based transaction handling and reconciliation workflows with careful handling of duplicate callbacks and failed transactions. Before expanding payments I would examine authentication, RLS, database integrity, idempotency, webhook security, transaction states, failure recovery and reconciliation. Default Split: Percentage, Exact amounts, Shares and Equal. Merge balances: I would verify the exact in app wording before submitting rather than inventing it. I would also report any issue I personally verify during product testing. Thanks

@guptakishan805

Based on your project requirement, I am confident that my skills and experience make me a strong fit for the React Native Developer role you are seeking to fill. Over the years, I have not only developed expertise in React Native and TypeScript but have also worked extensively with Supabase, integrating it in real applications as well as building payment workflows and transaction-sensitive features. One such application where I implemented payment integrations is ABC Split, a mobile app similar to SplitSense. There, I integrated UPI, webhooks, and handled transaction reconciliations, ensuring secure handling of user and payment-related data. Notably, the most important edge case I faced was a potential double-deduction error in transactions which I mitigated by implementing robust error handling and redundant verification systems. These experiences gave me invaluable insights into how to effectively handle payments while maintaining security. Before expanding payment capabilities in an expense-sharing application like SplitSense, meticulous examination is pivotal. I would review aspects such as internationalization factors, data encryption procedures during storage and transfer, integration testing with multiple payment providers to maintain compatibility, sophisticated error-handling mechanisms plus much more. This 360-degree prioritization of details is synonymous with my approach toward development.

@naima373

Hi, I’m a React Native + TypeScript developer experienced with Supabase, PostgreSQL, Auth, RLS, APIs, and transaction-based workflows. I can quickly understand the existing SplitSense codebase, fix issues, and improve payment/settlement flows securely. I’m also ready to test the app thoroughly before the interview and discuss specific product observations.

@michela542

Hi When I developed several applications involving expenses and transactions, the most important thing was keeping balances and transaction states consistent across the mobile app and backend, especially when a payment or webhook was delayed or received more than once. In these systems, I faced issues such as duplicate webhook notifications, transactions remaining in an intermediate state, and reconciliation differences between the payment provider and the application database. To solve them, I used idempotent transaction identifiers and backend state validation so repeated webhooks could not create duplicate records. I also centralized reconciliation logic in the backend to compare provider responses with the stored transaction state before updating balances. As a result, the payment and settlement flows became more reliable and easier to debug, while expense and balance data remained consistent. I can help you with this experience across React Native, TypeScript, Supabase, payment integrations, webhooks, and the existing product flows. I would want to answer based on an actual current app session rather than inventing details I have not verified. I would therefore provide the exact Default Split options, Merge balances explanation, and any observed issue after personally going through those screens. Michel

@prachia77

Hi, I’m interested in working on SplitSense and can contribute across React Native/TypeScript, Supabase, PostgreSQL, APIs, authentication, and secure transaction workflows. My approach would first be to understand the existing codebase and payment flow, then review Supabase Auth, RLS policies, database functions, webhook handling, transaction states, reconciliation, and edge cases such as duplicate callbacks, failed payments, retries, and inconsistent settlement states. I’d focus on improving reliability without unnecessarily changing working product flows. I’m also comfortable with Android/iOS testing, debugging existing applications, backend integrations, and performance improvements. For the product-specific questions, I would first install and use SplitSense as requested so my answers reflect the actual current application rather than assumptions. Best Regards, Webix Infotech India Pvt. Ltd.

@MuhammadAkif8

Have you already got the payment provider and webhook flow in production, or is the main requirement to improve the existing settlement architecture? I understand you need a React Native/TypeScript developer who can work across the SplitSense mobile app and Supabase backend, especially around secure payment flows, settlements, debugging, and production improvements. A few things I’d like to clarify: For payments, I have worked with payment gateway integrations and webhook-based transaction handling; an important edge case is duplicate or delayed webhook events, which need idempotent processing and reconciliation. Default Split: Equal, Exact Amount, Percentage, and Shares. The Merge balances option is intended to combine related balances so fewer settlement transactions are required. Thanks Akif S

@apoorvar16

Hi, I’m a React Native/TypeScript developer with full-stack experience in React, Node.js, PostgreSQL, Supabase and payment integrations. I explored SplitSense before applying by creating a group, adding an expense, checking balances, activity, totals, insights, settlements and Group Settings. I’ve worked with Razorpay payment integrations and backend transaction workflows. One important edge case is when a payment succeeds but the app doesn’t receive the response due to a network interruption. I handle this through backend verification, webhooks and idempotent processing to prevent duplicate transactions. Before expanding payments, I would review the existing balance and settlement logic, Supabase RLS, authentication, payment states, webhook verification, failed/pending/refunded payments, reconciliation and audit history. I found the four Default Split options: Split Equally, Split Fixed, Split by Portion, and Split by Shares. The exact Merge balances explanation is: “Pay for someone? Their share settles under you.” I explored the main flows and didn’t find a clear functional bug during testing, so my answer for that is N/A. I’d be happy to work across both the React Native app and Supabase backend, fix existing issues, improve transaction-sensitive flows and contribute product-focused improvements where useful.

@ApieTech

SplitSense - React Native and TypeScript across the app, Supabase underneath, and the payment and settlement side where most of the real risk sits. The area we would be most careful with is Row Level Security. On a shared-expense app, group membership defines visibility, and RLS policies on expenses, splits and settlements have to be written so a user can never read or write a row for a group they left, or one they were never in. That is easy to get subtly wrong and hard to notice, because the app itself never asks for the wrong row - only a crafted request does. We would test policies directly against the database with multiple roles, not just through the UI. On settlements: UPI and provider webhooks arrive late, duplicated, and occasionally out of order. Transaction state belongs in an append-only ledger reconciled against webhook events, so a retried callback cannot double-settle a balance. In a bill-splitting app a wrong balance is worse than a failed payment - it breaks trust between the users, not just with the app. React Native, TypeScript, Postgres and payment integrations are all core for us - we work with every major Indian gateway including UPI flows. Happy to push back on requirements where something simpler would do, which you asked for explicitly. Team of 20, so this can be a consistent named developer rather than a rotating pool. One question: which payment provider are you on for UPI settlements today? - APIE Technologies