What We Build
- wallets and payment services: top-ups, transfers, bill payments, transaction history and notifications for every movement of funds;
- mobile and online banking: accounts, cards, statements, template payments, limit and security management;
- lending platforms: calculator and application, data sent to scoring services, decision, loan agreement, repayment schedule and payment reminders;
- payments and subscriptions: payment acceptance, recurring billing, invoices, refunds and reconciliation with provider data;
- internal dashboards for support staff, risk managers and accounting: customer and transaction search, manual reviews, reports, audit log;
- personal finance products: expense tracking, savings and spending analytics from bank accounts where the bank provides access.
How We Keep Transactions Accurate
The foundation is the transaction ledger, designed so a balance can always be explained by the history of entries rather than stored as a single number.
- A repeated button tap or a duplicate request from a provider does not create a second charge.
- Every transaction has a clear status: created, processing, succeeded, declined, refunded.
- Product data is regularly reconciled with bank or payment provider data, and discrepancies go to the responsible team member.
- Every manual operator action is logged: who changed what and when.
Verification, Regulation and Security
Most financial products require customer verification: identity checks, screening against risk lists and suspicious activity monitoring. This is usually done through specialized KYC and AML services, and we build verification into the product so legitimate customers pass through without extra effort. Licensing, rules for handling customer funds and reporting are the responsibility of your company and your legal counsel. We take these requirements into account in design but do not assess legal compliance. If the product works with payment card data, it is usually simpler to have a payment provider process it than to store it in your own system.
On security we start from the first stage: encrypted connections, role-based staff permissions, additional codes for important actions and login attempt limits. For high-risk products we recommend an independent security review before launch; our general approach is on the security and technical audit page.
Typical Integrations
- Banks and card processors for accounts, cards and transfers.
- Payment providers such as Stripe or PayPal, plus Apple Pay and Google Pay.
- Identity verification and credit scoring services.
- CRM and support systems, so an agent sees the customer's history in one window.
- Accounting systems and data warehouses for reporting.
Every integration comes with a failure plan: what the user sees when a partner is unavailable, and how the transaction completes once the connection returns.
What We Need from You
- A description of the product and its money flows, or the business model if the product is new.
- The list of partners (banks, providers, verification services) and their API documentation.
- Requirements from your legal and compliance teams on checks and limits.
- For existing products: code, data and integration access for an audit.
What Affects Cost and Timeline
- Product type: a single payment flow or a full wallet with transfers, currencies and cards.
- Number of partners that must be integrated.
- Platforms: web only, mobile only, or both plus an operator dashboard.
- Verification and reporting requirements built under your license.
- State of an existing system: if we take over a product, a code and data audit comes first.
We estimate in phases: first a description of the logic and architecture, then development by priority.
Frequently asked questions
Can we start with a smaller version of the product? Yes, and it is often the right call. The first version can cover one core flow, such as transfers, with the rest added after demand is validated.
Will you help us get a license? No, that is a job for lawyers. We can prepare a technical description of the product that you need when dealing with a regulator or partner bank.
Do you work with existing financial systems? Yes. We first review the code, data and integrations, then recommend what to develop further and what is safer to rebuild.
Who will support the product after launch? We can stay on for support and feature development, or hand the product over to your team with documentation.
Do you process card data in your own system? Usually we recommend that a payment provider handles card data instead of storing it in your system, which is simpler and safer.
What happens when a bank or provider is slow or down? We design for it: the user sees a clear status, the transaction completes once the connection returns, and nothing is charged twice.
Why Promodex
Promodex has been building digital products since 2015, with 750+ projects in total. In finance, our portfolio includes Idram, MyAmeria, Telcell Wallet and My Viva. For financial products we first map money flows and error scenarios and only then move to screen design. Designers and mobile and web developers are our in-house team, and after launch we stay with the product as new partners, currencies or requirements come along.