PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu

Cred Clone - Features

Cred Clone Features: One Vault, Every Issuer

The design focus of this proposal is not the dashboard. It is a reward balance that has to reconcile, a bill reminder that has to fire on the right day for the right member, and a score screen that has to explain itself rather than print a number. Fourteen product engines on one codebase, as recorded in the supplied specification; this preview does not implement or verify any of it. Here is what the specification covers, grouped by who touches it.

14 engines, one codebase3 surfaces, one APIPoints balance: designed to reconcile
14Product engines in the supplied specification
295Mobile screens recorded
35Prisma models on PostgreSQL
24Admin console sections
01 / By role

Feature Set by Role

Three surfaces run from one platform and one API, as recorded in the supplied specification: web and mobile execute the same flows, so a payment made on the phone appears in the browser without a second integration.

01 - The Card Holder

Every card the member holds sits in one vault with its limit, available credit, statement date, due date, issuer and network. Utilization is calculated per card with good, warning and critical states, and the due date and minimum payment appear in the same card so the nudge carries context. This is the intended multi-issuer aggregation view: every card in one place, with utilization computed per card.

02 - The Bill Payer

A biller catalog with categories, one-shot bill fetch, upcoming and paid views, and a payment ledger carrying a reference number for audit. Autopay rules run per bill through a setup wizard, and a daily reminder job fires against the member's own due dates. The design bet: bill payment is the high-frequency habit that makes every other engine worth building - test it against your members.

03 - The Score Watcher

Score history over time, a factor breakdown separating positive from negative impact, per-card utilization with due dates, and an alert feed. The point is a screen that explains itself rather than printing a number. The bureau connection is yours to supply; the intelligence layer above it is recorded as complete in the specification.

04 - The Points Collector

XP and levels, a bronze to diamond tier ladder, streaks, achievements and leaderboards across five categories, feeding a reward catalog with real inventory accounting and an append-only redemption ledger. Gamification is specified as native rather than bolted on; if you evaluate a loyalty vendor, ask whether it can see your event stream.

05 - The Premium Member

Monthly and yearly plans with a premium flag specified as checked server-side rather than hidden in the interface, gating advanced analytics, AI insights and exclusive offers. Budgets and goals sit alongside, so the paid tier has substance behind it rather than being a badge.

06 - The Operator

Twenty-four admin sections across members, compliance, finance, catalogs and platform policy: member management with audit logging, a four-step KYC review queue, fraud monitoring with rule management, dispute resolution, offer and reward catalogs, email templates, an integration registry with connection tests, and monitoring.

Every capability here is in the proposed base scope as recorded in the supplied specification. Where something needs a third-party account or a deployment decision before it works in production, that is stated against the feature rather than implied away.

02 / Compare

CRED vs This Build vs Building From Scratch

What each route gives you on the parts this design treats as deciding whether a credit super-app holds a member. Pricing is deliberately not on this page - the cost shape lives on the development cost page.

What decides itThis build, as proposedBuilding from scratch
Time to a working appScoped in writing before work startsAsk for the phase plan and the team shape.
Card vaultEvery issuer in one view, utilization per cardAsk how issuers are aggregated and utilization computed.
Bill engineCatalog, fetch, autopay rules and a reminder jobAsk how reminder scheduling works against member-level due dates.
Points economyInventory accounting and an append-only redemption ledgerAsk whether the points balance can be rebuilt from an append-only history.
GamificationXP, tiers, streaks, achievements and leaderboards, nativeAsk whether the loyalty tooling can see your event stream.
Credit intelligenceScore history and factor breakdown above your bureau feedAsk what explains the score to the member.
Operator console24 sections, in the proposed scopeAsk what the operator console covers, and when it gets built.
Source codeFull monorepo, 35 Prisma models, in the proposed handover scopeAsk what ownership and handover scope you end up with.

Swipe sideways for the full table

CRED itself is the reference for what this category looks like at scale; it is not a product you can buy or self-host. The comparison that matters commercially is the second column against the third.

03 / End to end

How It Works, End to End

One member, traced from signup through to a reward redemption, with every ledger entry and every operator action written down - as recorded in the supplied specification. What one bill payment touches: the bill is fetched from the biller catalog, the autopay rule is checked and the reminder cleared, the payment is written with a reference number, card utilization is recalculated, points accrue and the streak advances, and the tier ladder and leaderboard update.

01

Signup issues an identity and a referral code

Email and password registration with OTP verification, JWT access tokens with refresh token rotation, two-factor authentication and a trusted device list, and biometric login on mobile with secure token storage. A referral code is issued at signup, so acquisition mechanics exist from the first member rather than being added once growth stalls.

02

KYC runs as a four-step application

Personal, address and employment records with document upload covering Aadhaar, PAN, passport and utility, then an operator review queue with approve and reject. Member status is denormalized so eligibility checks are fast, which matters when every screen has to know whether this member can transact.

03

Cards enter the vault and start being useful

Each card carries its limit, available credit, statement date, due date, issuer and network. Utilization is computed per card with good, warning and critical states. Virtual cards with freeze and top-up, card statements and a card comparison view sit alongside, so the vault is a working surface rather than a list.

04

A bill is fetched, paid and remembered

The biller catalog is searched by category, the bill is fetched in one shot, and payment writes to a ledger with a reference number for audit. An autopay rule can be attached through a setup wizard, and from then on a daily reminder job works against that member's own due dates rather than a generic schedule.

05

The score screen explains itself

Score history is kept over time, with a factor breakdown separating what is helping from what is hurting, per-card utilization and due dates in the same view, and an alert feed for changes. The bureau adapter is in the proposed scope; what you supply is the agreement and the credentials that make real scores return.

06

The action earns points, and the points need to reconcile

Paying the bill accrues points, advances a streak, moves XP and can change the tier on a bronze to diamond ladder. The reward catalog behind it carries real inventory, and every redemption writes to an append-only ledger, so a points balance is something you can reconcile against rather than a number sitting in a cache.

07

The operator sees all of it in one console

The same member opens in the operator console: the KYC application and its four steps, the transaction record, the reward redemption against inventory, and the audit trail behind every operator action. Configuration for offers, reward catalogs, referral milestones and integration credentials sits in the same place.

04 / Deliberate

Every Feature Earns Its Place

Each module below is in the proposed base scope for a reason, not because a competitor lists it.

ModuleWhy it is in the base build
Multi-issuer card vaultThe intended multi-issuer aggregation view: every card in one place. Test whether it is reason enough for members to open your app.
Per-card utilization statesA raw percentage carries no instruction; good, warning and critical next to a due date is designed to be one.
Bill reminder jobDesign rationale: a reminder that fires on the wrong day risks member trust in every subsequent one, so the job is specified to run against the member's own due dates.
Payment ledger with referenceDesigned so every payment carries a reference through to a dispute, because a dispute without one has nothing to reconcile against.
Append-only redemption ledgerRequire a reconstructable history: ask how the balance can be rebuilt, reconciled and defended in a dispute. Ask a qualified adviser how points are classified in the relevant jurisdiction.
Reward inventory accountingDesign rationale: inventory accounting is proposed as requiring a check of available and reserved stock before a reward is offered.
Native gamificationAsk whether a loyalty vendor can see your event stream and reward the actions you care about.
Server-side premium flagProposed requirement: premium authorization is checked server-side, where the data is returned, not only in the interface.
24-section operator consoleOperator tooling is the surface to ask any provider about: ask how exceptions are handled, and by whom.

Swipe sideways for the full table

Budgets, goals, offers, referrals and subscriptions sit alongside these in the same fourteen engines, as recorded in the specification.

05 / Stack

The Technology Behind the Features

What the supplied specification records, and what that means for the team who inherits it.

Web

A Next.js 14 App Router build across sixty routes in TypeScript, with Tailwind, Radix primitives, TanStack Query and a progressive web app service worker giving offline read access.

Dual API surface

148 consumer route handlers alongside an Express workspace of 114 route files and 297 services, with an OpenAPI specification, Swagger UI and SDK generators for JavaScript, Python and PHP.

Data

Thirty-five Prisma models on PostgreSQL with 183 further data-access models, the migration set and a seed workflow, including the append-only payment, redemption and bill payment ledgers.

Mobile

A 295-screen Expo application with biometric login, secure token storage and push notifications, running against the same API as the web app rather than a parallel implementation.

Background work

Eleven background jobs covering the daily bill reminder sweep, autopay execution, score refresh and the scheduled work a credit app depends on but never shows the member.

Operations

Prometheus metrics, error tracking and generated reports with Grafana dashboards in the deployment stack, plus seven React Email templates editable at runtime.

Why the ledger design is the number that matters

A card list and a score gauge are the visible half. The half that decides whether the platform holds up is everything that has to reconcile behind them: a points balance that reconciles rather than a counter, a redemption that cannot be replayed, a bill payment that carries a reference through to a dispute, and an operator console where every intervention is written to an audit log. Thirty-five models is not a boast, it is the consequence of modelling those things instead of flattening them - as recorded in the supplied specification: 35 Prisma models, 148 consumer API routes, 11 background jobs.

The stack is Next.js, Express and TypeScript on standard PostgreSQL, which matters when you hire against it and when a technical buyer runs due diligence on what you own.

06 / Honest readiness

What Is Not Included in the Base Package

Named here rather than discovered after scoping. What needs your account, and what is pre-launch work - proposed-scope boundaries from the supplied specification; none of it is implemented in this preview.

The bureau feed

Experian and Equifax adapters and the intelligence layer above them are recorded in the specification. What is needed is your own bureau agreement and credentials before real scores return; until then the score surface runs against the adapter without live data behind it.

CIBIL is a label, not a feed

It is recorded as a configurable label rather than a live feed. That distinction is stated plainly because in this market it is the one most likely to be assumed rather than asked about.

Authentication hardening

CAPTCHA on signup and login, enforced email verification, and SMS two-factor exposed in the member interface are documented as operator work and completed as pre-launch hardening rather than switched on in the base scope.

Your own gateway accounts

Bill payment and card payment flows run through accounts you hold, which is deliberate - it keeps interchange and processing arrangements between you and your provider rather than routed through us.

iOS

The Android build of the Expo application is in the proposed base scope. A native iOS release with its developer account, signing and review cycle is quoted separately.

The controls recorded in the specification: bcrypt hashing, JWT with refresh token rotation and server-side revocable sessions, two-factor authentication, biometric login, Zod validation on every API boundary, DOMPurify sanitization, helmet headers, per-route rate limiting, HMAC verification on inbound webhooks, idempotency keys on payment initiation and audit logging on operator actions.

07 / FAQ

Frequently Asked Questions

Does the app show real credit scores out of the box?

Not until you supply a bureau agreement. The Experian and Equifax adapters and the intelligence layer above them - score history, factor breakdown, alerts - are recorded in the specification. What is missing is your own bureau credentials, which no vendor can provide on your behalf. CIBIL specifically is a configurable label rather than a live feed, and we state that plainly because it is the assumption most likely to go unquestioned.

Why does the points ledger matter so much?

Because a reward balance has to reconcile. If it lives as a counter that can be incremented and decremented in place, ask how you would prove what a member earned, survive a reconciliation, or defend a dispute. In the specification, redemption writes to an append-only ledger against a reward catalog with real inventory, so the balance can be rebuilt from its own history. Ask a qualified adviser how points are classified in the relevant jurisdiction.

Can members add cards from any bank?

The vault holds cards from any issuer with limit, available credit, statement date, due date, issuer and network, and computes utilization per card. That single cross-issuer view is the intended aggregation: every card in one place, with utilization computed per card. What each card can do beyond display depends on the integrations you arrange with your providers.

Is the premium paywall enforced properly?

The premium flag is specified as checked server-side where data is returned, not by hiding buttons in the interface. Monthly and yearly plans gate advanced analytics, AI insights and exclusive offers. The design intent is that paid data requires server-side authorization; verify it in your own testing before launch.

What security is specified versus outstanding?

Recorded in the specification: bcrypt hashing, JWT with refresh token rotation and server-side revocable sessions, two-factor authentication, biometric login on mobile, Zod validation on every API boundary, DOMPurify sanitization, helmet headers, per-route rate limiting, HMAC verification on inbound webhooks, idempotency keys on payment initiation and audit logging on operator actions. Outstanding operator work: CAPTCHA on signup and login, enforced email verification, and SMS two-factor exposed in the member UI.

Is an iOS app included?

The Android build of the 295-screen Expo application is in the proposed base scope, and the web application is a progressive web app with a service worker giving offline read access. A native iOS release brings its own developer account, signing setup and review cycle, and is quoted as separate work rather than folded in.

09 / Explore

Explore the Cred Clone

You are on Features. Further pages on this product are being restored.

Overview

The product page.

Back to overview

Business Model

How the platform earns.

See the six lines

Development Cost

How pricing is scoped.

See the cost shape

Development Company

How to choose who builds it.

See what to check

10 / Next step

Trace a bill payment with us

Ask how one bill payment moves through the specification: fetched from the biller catalog, paid with a reference number, points accrued, tier updated, and the same activity visible in the operator console with its audit trail. Email is fine - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead