An animation shows a single dot — one transaction — moving, spawning new points and connecting them until it becomes a global financial network.
Money,inmotion.
This is one transaction.
Chapter 02 · Transaction
Everything starts with one.
- 01Vishal. A payment starts as an intent: ₹10,000 to a merchant.
- 02Account. The balance is checked and the amount reserved, so it can never be spent twice.
- 03Payment network. The network routes the instruction between institutions using shared rules.
- 04Bank. The receiving bank verifies the destination account and accepts the funds.
- 05Merchant. The merchant is credited. One transaction, five systems, one movement.
Demo transaction · fictional data
Chapter 03 · Speed
Time is part of the transaction.
Three payments leave at the same moment. Larger amounts pass more checkpoints, so each one moves at its own pace.
Checkpoint Settled
Illustrative pacing · not real settlement times
Chapter 04 · Network
One transaction is small.The network is everything.
Customers, merchants, banks, providers and currencies — every movement touches many of them. Hover a node to see what it connects to.
- Bank
- Payment provider
- Merchant
- Business
- Customer
- Currency
Chapter 05 · Data
See what money does.
Money enters from customers, passes through the platform and branches toward where it is needed. The river is always moving — that's the point.
₹0.0 Cr
Demo daily volume · illustrative
Chapter 06 · Volume
Volume moves like water.
Each line is a slice of transaction volume. Currents shift as the simulated market changes. Move through it.
- Simulated regime
- Inflow-heavy
- Inflow / outflow
- 64 / 36
Large movements · demo simulation
Chapter 07 · World
Money has no borders.
Routes and activity are fictional demo data.
Chapter 08 · Currency
Value changes. Money moves.
Receive in
- Rate
- 1 INR = 0.01198 USD
- Fee (0.4%)
- ₹400
- Received
- $1,193.21
Illustrative rates · not live market data
Chapter 09 · Fees
The cost, in plain sight.
The circle is your transfer. Drag its edge to change the amount, and watch the fees separate. Small transfers pay proportionally more, because part of the network fee is flat.
- Amount
- ₹1,00,000
- Effective cost
- 1.10%
- Network fee
- ₹500
- Conversion spread
- ₹400
- Tax on fees
- ₹200
Illustrative fees · slices magnified ×12
Chapter 10 · Transparency
Follow every rupee.
Send an amount. Watch exactly where each deduction happens and why — before the money arrives, not after.
₹1,00,000
Start
₹1,00,000
Network fee− ₹500 (0.50%)
Paid to the payment rails that carry the transfer.
₹99,500
Conversion spread− ₹400 (0.40%)
The gap between the mid-market rate and the rate applied.
₹99,100
Tax on fees− ₹200 (0.20%)
Levied on the fee portion, never on your principal.
₹98,900
Arrives
₹98,900
Total deducted ₹1,100 (1.1%). Every rupee accounted for.
Illustrative rates · fee bars magnified ×40
Chapter 11 · Security
Trust is an engineering problem.
01Identity
Every actor is known before anything moves — people, devices, businesses.
02Authentication
Each request proves who sent it, with more than one factor when stakes rise.
03Encryption
Data is unreadable in transit and at rest. Keys live apart from the data they protect.
04Monitoring
Every movement is observed against what normal looks like for that account.
05Risk
Unusual patterns are scored and held for review before they settle.
06Response
When something is wrong, money is paused, people are told, the gap is closed.
Chapter 12 · Risk
Normal has a shape. So does everything else.
Monitoring log · demo
- TX-4018NORMAL
- TX-4019NORMAL
- TX-4020NORMAL
- TX-4021RESOLVED
Every account has a rhythm. Movements that break it are held and checked before they settle — then released or stopped.
Conceptual · no detection-accuracy claims
Whoareyou?
Chapter 13 · Identity
Identity.
- Device→Is this a device we've seen before?
- Identity→Do the credentials belong to this person?
- Behavior→Does this feel like them — timing, rhythm, place?
- Authentication→Prove it, with the factor the risk calls for.
- AccessGranted — scoped to exactly what's needed.
Access granted.
Chapter 14 · Business
Business moves differently.
Revenue arrives in one stream and leaves in many: payroll, suppliers, tax, marketing, operations. What stays is growth.
Fictional company · node size scales with the period's inflow
Chapter 15 · Analytics
Data should answer questions.
UPI overtook cards in month seven and now carries most new revenue.
Fictional business data
Chapter 16 · Time
See your money over time.
- Balance
- ₹3.82 Cr
- Revenue
- ₹13.89 Cr
- Expenses
- ₹10.03 Cr
Payments in
Payroll
Suppliers
Savings
Drag the timeline · fictional demo business
Chapter 17 · Growth
Small movements become big ones.
Illustrative shape · not a projection or advice
Chapter 18 · Investing
Capital needs direction.
Move a slider and the rest rebalance. Each ring is one asset class; together they show where capital sits.
- 15%
- 40%
- 25%
- 15%
- 5%
Product visualisation · demo values · not financial advice
Chapter 19 · People
Behind every number is a person.
Arjun, 29 · independent designer
Three clients, two currencies, one person doing the books.
- 1
Client
Project signed
- 2
Invoice
Sent with one link
- 3
Payment
Arrives, converted if needed
- 4
Tax
A share set aside automatically
- 5
Savings
What's left starts working
Fictional people and businesses
Chapter 20 · Control
The goal is not more data.The goal is more control.
Your money
₹20,52,350
Your rules
Your view
Chapter 21 · Automation
Let money handle itself.
Chapter 22 · Product
The system you were exploring is the product.
Payments
Move money in seconds.
Domestic and cross-border payments from one place.
Chapter 23 · Infrastructure
Behind the interface.
One button press in your product becomes a request that passes through every layer below it.
- POST /paymentsrequest
- ✓AUTHKey scoped to payments:write
- ✓VALIDATEAmount, currency, recipient OK
- ✓PROCESSRouted · ledger entries written
- ✓COMPLETE201 Created · pay_demo_8Kq2
Fictional request · no real keys or data
View API →Chapter 24 · Developers
Finance should be easy to build.
- ✓ AUTHENTICATED
- ✓ VERIFIED
- ✓ PROCESSED
{
"id": "pay_demo_8Kq2",
"status": "processed",
"amount": 2500000,
"currency": "INR"
}import Flux from "@flux/node";const flux = new Flux(process.env.FLUX_KEY);const payment = await flux.payments.create({ amount: 25_000_00, // paise currency: "INR", recipient: "rcp_demo_asha", idempotencyKey: "order_1042",});- Request14 ms
- Auth9 ms
- Validate5 ms
- Process31 ms
- Response8 ms
Chapter 25 · Global
Global
financial
infrastructure.
Five regions, one system. Pick a region to bring it round.
Chapter 26 · Scale
Built for the moment it gets big.
10,000Connected nodes · demo scale
An illustration of a network growing from one node to ten thousand. Demo scale, not a capacity claim.
Chapter 27 · Reliability
Quietly, always on.
- PaymentsOnline
- IdentityOnline
- AnalyticsOnline
- SecurityOnline
Demo status board · not a live status page
Chapter 28 · Trust
You should know where your money is.
- 01Visible.
- 02Secure.
- 03Connected.
- 04Controlled.
Chapter 29 · Statement
Every line opens.
A balance is a summary of decisions. Open it up and every movement, fee and conversion is there, in plain words.
AccountOperating account₹1,00,000ExpandCollapse
Transaction history+₹1,00,100
| 02 Oct | Client payment · Orbit Co | +₹1,20,000 |
| 03 Oct | Kite Supplies | −₹18,500 |
| 03 Oct | Payroll batch (2) | −₹1,400 |
Fees−₹703
| 02 Oct | Network fee · 0.48% + ₹20 | −₹596 |
| 03 Oct | Tax on fees | −₹107 |
Conversions+₹1,002
| 01 Oct | USD 12.00 → INR at 83.47 (illustrative) | +₹1,002 |
Movements−₹399
| 04 Oct | Auto-rule: 10% to Savings | −₹399 |
| 04 Oct | Interest · Savings | ₹0 |
Fictional statement · illustrative figures
Chapter 30 · Compliance
Finance needs more than speed.
- 01
Security
Layered controls from identity to response, designed in rather than added on.
- 02
Privacy
Collect what's needed, keep it only as long as needed, and say so plainly.
- 03
Compliance
Processes built to be audited: every movement has a record and a reason.
- 04
Reliability
Redundant paths, staged rollouts and monitoring that watches the money, not just servers.
How we protect data
Encryption
Data is encrypted in transit and at rest. Keys are managed separately from the data and rotated on a schedule.
Authentication
People and systems prove who they are. Sensitive actions ask for a second factor; API keys are scoped to what they need.
Access controls
Least privilege by default. Every internal access is logged and reviewed, and production access is time-limited.
Monitoring
Transactions are compared with normal behaviour for the account. Unusual movements are held for review before they settle.
Incident response
A written plan, practised regularly: contain, notify affected people promptly, fix the cause, publish what we learned.
Need the details for a security review? We'll walk your team through controls, data flows and incident process.
Book a demo →Chapter 31 · Learn
Questions worth asking.
What is a payment network?
The shared rules and rails that let banks that have never met move money between each other — the roads, not the cars.
What is a payment gateway?
The front door for a business: it takes one checkout and speaks to many methods — cards, UPI, wallets — on its behalf.
What is embedded finance?
Financial features living inside products people already use — a payout button in a marketplace, credit at a checkout.
One.
Millions.
of connections · illustrative scale