An account you can understand
Currency accounts connect available funds, transaction history and individual payment details. A customer can move from the overview to the record behind a balance without losing their place.
Website & product design
Nevka Money
An everyday banking workspace connecting currency accounts, transfers and card controls. Clear payment reviews carry through to receipts and account activity, while the same warm visual identity moves from the product website into daily use.
About the project
- Industry
- Fintech
- Scope
- Website
Customer app
Card controls - Focus
- Customer experience
The product starts with a simple question: can a customer understand what they have, what has moved and what will happen next? The overview connects separate currency accounts to their recent activity, with payment details a step away.
A complete sample payment journey carries the customer from recipient selection through amount and fee review to a receipt. Card controls sit in a dedicated workspace, while the same warm visual identity carries through the product website.
The experience, in motion
An account.
A complete experience.
Follow a transfer from recipient to receipt, then manage the card connected to the account.
Product walkthrough · Illustrative data
Inside the product
Considered beyond
the first screen.
A payment, from intent to receipt
Choose a recipient, enter an amount and review the conversion and fee before confirming. The local sample records the transfer and updates the available funds and activity together.
A card with useful controls
Card management brings spending limits, payment settings and the active or frozen state into one place. The customer sees what a change affects and can return to the account to check its activity.
Engineering approach / Proposed architecture
A ledger behind every balance.
The account and card controls would connect to a service that records money movements, coordinates providers and gives operators the same transaction history customers see. The central design decision is to make every displayed balance explainable.
- 01→
Identify the account
Check the signed-in customer, account permissions and currency before returning a balance or accepting an instruction.
- 02→
Record the instruction
Create a payment record with a stable request key. Validate available funds and record any reservation before contacting a provider.
- 03→
Track the provider
Send through the selected payment or card integration. Keep requested, accepted, completed and failed states distinct as responses arrive.
- 04✓
Close the record
Post balanced ledger entries, release or settle reservations, and match provider settlement records to the internal journal.
Under the surface
The decisions
behind the experience.
Explore the system behaviour, integration choices and operational detail.
Money belongs in a journal
Use an append-only double-entry journal with balanced postings committed in one database transaction. Store amounts with explicit currency and precision. Corrections add reversing entries, preserving the original record and its explanation.
A card toggle needs confirmation
Treat freezing a card as a request to its issuing provider. Show a pending state until the provider confirms the change, and retain the previous state if it fails. Record who requested the change and the provider response.
Make exceptions visible
Give each payment a shared reference across the customer view, provider calls and operations workspace. Repeated requests reuse the original instruction; unresolved provider responses enter a review queue instead of silently becoming new payments.
A possible production stack
- Customer experienceNext.js + TypeScript
- A shared set of account, activity and card components, with server-checked access to customer data.
- Accounts & integrationsGo service + provider adapters
- Keep account rules separate from individual payment and card APIs, with explicit request and response contracts.
- Financial recordPostgreSQL
- Atomic postings, exact amounts and linked journal records would underpin the balance and reconciliation views.
- Long-running operationsTemporal
- Coordinate provider waits and retries, with idempotent activities and clear paths for failures that need an operator.
Design approach
01
A clear first impression
Warm neutrals, editorial typography and a tactile card image give the product a distinct identity. A quiet layout lets that identity lead, with a clear path into the experience.
02
Control at a glance
Balances, payment history and card settings belong to one consistent account state. A confirmed sample transfer updates the available funds and adds its record to activity; a frozen card stays visibly frozen when the customer returns.
