Revolut Clone: Multi-product Finance App — Custom-Built for Your Market

A frozen card can still have a payment waiting to settle

A fictional customer, Maya, sees a hotel payment pending against her euro balance and freezes her card before a flight. She also has a sterling balance and an exchange quote open on another screen. A buyer evaluating a Revolut-style app should inspect what the app says next: which funds remain available, whether the card provider acknowledged the freeze and whether an expired quote can still be submitted. One reassuring home total cannot answer those questions.

App Clone Labs scopes independently branded personal finance software around multi-currency account views, card controls, reviewed exchange instructions and accountable servicing. This reference does not imply Revolut affiliation, a financial license, provider approval or insurance coverage. Establish the actual institutions, permissions and customer protections separately. Synthetic account activity demonstrates software behavior; it cannot establish authorization to hold funds, issue cards or offer an additional financial product.

Our current reference build is a Next.js and React application on PostgreSQL with an Android client. It shows personal, business and family account views, virtual cards, savings vaults with round-ups, cashback, plan tiers and an investing view, with admin, support and analytics panels. All data is fictional: the reference holds no funds and carries no licence. Investment views are illustrative; real trading needs an authorised broker, capital is at risk and nothing here is investment advice.

Every product needs a responsible provider and permission boundary

Identify the entity supplying the account, the card arrangement and the currency exchange service before combining them in one interface. Define eligible customers, operating markets and supported product states through those actual arrangements. An account accepted by one provider does not establish eligibility for another product. Keep required checks and customer disclosures attached to the product that needs them, including any restrictions while review remains incomplete.

Give operations a written responsibility map for onboarding, financial records, complaints and incidents. Explain applicable protection using approved facts about the actual service; do not label every balance a bank deposit or imply a uniform protection regime. Rehearse a customer eligible for a currency account but not a card, and a provider changing a product restriction. Navigation should communicate the decision without offering an action the server cannot authorize.

Currency balances should separate available money from holds

Show each currency balance with its own unit, source and availability evidence. Separate posted funds, pending authorizations and restrictions under the selected ledger arrangement. A converted home total can help orientation, but it needs a stated valuation basis and must not appear to be a single spendable account. Stale provider data should have a visible state, especially when the customer is preparing a card purchase or an exchange.

Rehearse Maya holding both euros and sterling while a euro authorization remains pending. The available amount, transaction detail and statement should tell a consistent story. Define exact monetary units and rounding at accounting boundaries. Never release a hold because a screen refresh omitted it or merge provider records using a matching display name. An unexplained difference needs investigation ownership rather than a manual balance edit that makes the app look tidy.

Pending authorization is a distinct card payment state

Revolut’s UK personal help on pending card payments distinguishes authorization from full processing and explains that a pending payment cannot simply be cancelled by the service before the indicated date. This is a reference example, not a timetable or capability promise for an independent card program.

Agree how authorization, clearing, reversal and expiry arrive from the actual processor. Keep the amount held distinct from final settlement, including changed merchant amounts or supported currency differences. Show relevant references and the expected next action without promising every pending payment resolves in the same period. Rehearse a merchant cancellation arriving after a customer contacts support, then a duplicate reversal event. Reconcile the financial result once and retain the original authorization trail so the customer and operations can explain the released amount.

Card freeze needs acknowledgement and a precise explanation

Treat card freeze as a consequential instruction to a selected provider, not merely a local visual toggle. Authenticate the customer, submit the intended card reference and track acknowledgement. Distinguish requested, pending, effective and failed states where the provider supports them. Explain the scope of the restriction using the agreed card rules. A freeze screen should not imply that already authorized payments are refunded or that every possible transaction path is blocked.

Rehearse an authorization racing the freeze request, a processor timeout and a customer opening the app on a second device. The interface should show the best established state and a supported escalation route. Unfreeze must respect independent account or fraud restrictions; reversing a customer preference cannot override a provider decision. Keep an attributable record of who requested the change and what the provider confirmed. Lost-card replacement needs a separate supported lifecycle rather than an overloaded freeze button.

The spending currency policy must be understandable before travel

Define which supported balance funds a card payment and whether the selected arrangement permits automatic conversion. Explain insufficient funds, unavailable currencies and any fallback order. Do not infer that every currency visible in the app is usable by the card. Account balances, merchant transaction currency and settlement currency can serve different roles, so retain those identifiers in transaction details when the provider supplies them.

Rehearse a euro purchase when Maya has a partial euro balance and sufficient sterling, then repeat while exchange is unavailable. Show the actual supported outcome rather than inventing a universal split-payment rule. Clarify how a later reversal or refund is recorded, including the provider treatment of currency conversion and fees. A spending preference should be a customer control with documented limits, not an assurance that every merchant or network will apply the customer’s preferred rate.

An exchange quote is more specific than a displayed rate

Revolut’s UK personal explanation of exchange rates and costs describes variable rates and reviewing rate and fee information before an in-app exchange. It also distinguishes the timing of cost information for card transactions requiring conversion. Verify the selected provider’s actual quote and disclosure behavior independently.

Bind a supported exchange quote to source currency, destination currency, debit amount, received amount, fees and validity. Explain whether a displayed rate is indicative or executable. Rehearse FX quote expiry while the customer reads the confirmation screen, and require a renewed review when the provider supplies changed terms. Do not execute a materially different conversion under an earlier confirmation. Preserve the accepted quote and provider reference so support can compare the reviewed instruction with the resulting account entries.

An uncertain exchange should not invite an accidental second debit

Separate quote acceptance, instruction submission, provider confirmation and ledger reconciliation. If the connection fails after submission, retain the instruction reference and query its result through the supported interface. A timeout is not proof that no exchange occurred. Explain the pending state and prevent an impatient refresh from silently creating another conversion. Any retry policy needs to preserve the identity of the intended financial instruction.

Rehearse a confirmed provider exchange whose account update is delayed, followed by repeated callbacks. Reconcile one source debit and its corresponding destination credit, with fees recorded as agreed. Distinguish missing evidence from confirmed failure and route unmatched entries to the responsible operations team. Staff should not fabricate a receipt or release spending capacity based on a hopeful assumption. Define what the customer can do while review continues and how an unresolved case reaches the actual provider.

Budgets and notifications need correction paths

Present budgeting as an explanation of recorded activity, with clear treatment of pending payments, refunds and internal exchanges. A transfer between currency balances should not automatically become new spending in every category. Let customers correct supported merchant categorization without changing the underlying financial transaction. Explain whether a budget uses transaction currency or a selected reporting currency and how valuation affects historical comparisons.

Rehearse the hotel authorization becoming a different settled amount, then a refund arriving in a later reporting period. Notifications should follow meaningful state changes without duplicating the same event after reconnection. Give customers accessible controls over supported alerts, while preserving required service communication under the actual policy. Avoid exposing sensitive balances in notification previews by default. A missed notification does not alter payment status, and an attractive budget chart cannot substitute for reconciled account records.

Disputes need evidence and a team that owns the next step

Offer a transaction-specific help route that distinguishes an unfamiliar payment, a merchant disagreement and a pending authorization question. Collect appropriate evidence without requesting unnecessary sensitive documents. Explain the responsible provider, case reference and supported communication path. Filing a dispute is not the same as receiving a refund; do not promise a successful chargeback, immediate funds release or a single universal resolution deadline.

Rehearse Maya reporting the hotel payment while it remains pending, then returning after settlement with additional merchant evidence. Keep the financial state and support case connected without conflating them. Record evidence requests, submissions and attributable decisions, and preserve a route for complaints appropriate to the actual service. Restrict financial adjustment authority and document any supported provisional treatment. A support agent acknowledging a message must not make the interface imply that the provider has accepted liability or completed the investigation.

Choose personal finance coordination before adding unrelated products

Compare the digital banking front-end platform when the main decision is a selected institution-backed account experience. This brief adds explicit coordination across personal currency balances, card spending controls and exchange quotes. Start with a small set of actual providers whose responsibilities can be explained and tested.

Review the Wise-style cross-border money movement scope when recipient setup, funding and corridor payout are the central workflow. Those transfer stages differ from managing daily card authorizations and internal currency conversion. Investments and insurance require separate eligibility, disclosures, consent and servicing arrangements; their icons should not appear as actionable products merely because the home screen has room.

Follow one customer through freeze, expiry and dispute review

Use a synthetic sandbox with Maya, fictional currency balances and controlled provider events. Buyer acceptance should distinguish available funds from a pending authorization, freeze a card through acknowledgement and show an independent restriction blocking unfreeze. Expire an FX quote, review changed terms and interrupt a submitted exchange. Recover its result once, reconcile both currency entries and follow the hotel payment into an attributable dispute case.

Set expected outcomes before the walkthrough and retain the observed provider events alongside the customer view. A freeze request should not appear effective before acknowledgement; an expired quote should stop before a debit; repeated settlement evidence should produce one financial result. Verify that support can identify the responsible provider and next action without gaining unauthorized adjustment powers. Record unresolved exceptions as acceptance gaps with an owner.

Bring one provider arrangement and one unresolved payment to a personal finance scope discussion to define account boundaries, card behavior, exchange confirmation and staffed support.

Use the delivery process to agree source-code terms, permissions and acceptance evidence. Demonstrations do not establish licensing, live funds access, issuing approval or protection for real customers.