Vocabulary for Fintech Developers

Financial technology sits at the intersection of software engineering and financial systems. If you are building payment platforms, trading systems, banking APIs, or accounting software, you will encounter a specialised vocabulary that blends finance and engineering. This guide covers the core terms every fintech developer needs to communicate clearly.

Reconciliation

Reconciliation is the process of verifying that two sets of financial records match — for example, confirming that the transactions recorded in your internal system match those reported by a bank or payment processor.

“Every night, the reconciliation job compares our internal ledger against the Stripe payout report. Any discrepancy triggers an alert for the finance team.” “Reconciliation failures are usually caused by timing differences, duplicate records, or rounding errors in currency conversion.”

Settlement

Settlement is the process of transferring funds between parties to complete a financial transaction. Settlement can be immediate (real-time gross settlement, or RTGS) or deferred (typically the following business day, or T+1/T+2).

“Card payments settle on a T+1 basis — the money appears in the merchant’s account the business day after the transaction.” “We use a settlement account to batch daily transactions and settle once per day rather than processing hundreds of individual transfers.”

Ledger

A ledger is a record of financial transactions. In software, a ledger is often a database table or service that records every debit and credit, maintaining an accurate running balance.

“Our double-entry ledger records every transaction as a debit on one account and a corresponding credit on another. The sum of all entries always equals zero.” “We built an immutable ledger — entries are never deleted or updated, only appended. This gives us a complete audit trail.”

Idempotency

Idempotency means that making the same request multiple times produces the same result as making it once. In payment systems, idempotency is critical to prevent double charges when requests are retried due to network errors.

“Every payment API request must include an idempotency key. If you retry with the same key, the server returns the original response without processing the payment again.” “Without idempotency keys, a timeout followed by a retry could result in a customer being charged twice.”

ISO 20022

ISO 20022 is an international standard for financial messaging — a common language for exchanging data between financial institutions. It is gradually replacing older standards like SWIFT MT messages and is being adopted by CHAPS, SEPA, and other major payment systems.

“We’re migrating our payment messages to ISO 20022 ahead of the SWIFT deadline. The new format carries much richer data, including full remittance information.” “ISO 20022 messages are XML-based and structured — they are more verbose than MT messages but far easier to parse and validate programmatically.”

FIX Protocol

The FIX (Financial Information eXchange) Protocol is a messaging standard used in electronic trading for the real-time exchange of securities transaction information. It is the dominant protocol for order routing between brokers, exchanges, and buy-side firms.

“The order management system sends buy and sell orders to the exchange via FIX 4.4. Each message contains the instrument identifier, quantity, price, and order type.” “FIX is a binary-friendly, low-latency protocol. In high-frequency trading, even microseconds of latency matter, and FIX was designed with that in mind.”

Clearing

Clearing is the process of reconciling orders between transacting parties before settlement — confirming the details of a transaction and ensuring both parties have the necessary funds or securities to complete it.

“After a trade is executed, it goes through clearing. The clearing house acts as the counterparty to both buyer and seller, guaranteeing settlement even if one party defaults.” “Clearing adds a layer of risk management between trade execution and settlement. It is mandatory for most exchange-traded instruments.”

Escrow

Escrow is an arrangement in which a trusted third party holds funds or assets on behalf of two parties until specified conditions are met. In software, escrow mechanisms are common in marketplace and P2P payment platforms.

“When a buyer places an order on the marketplace, the payment is held in escrow. Funds are released to the seller only after the buyer confirms delivery.” “We implemented an escrow service using a virtual account per transaction. Funds sit in the escrow account until the dispute window closes.”

Chargeback

A chargeback occurs when a customer disputes a transaction with their bank, and the bank reverses the payment, reclaiming the funds from the merchant. Chargebacks are costly and can result in penalties for merchants with high rates.

“Our fraud detection model flags transactions likely to result in chargebacks. By declining high-risk transactions, we keep our chargeback rate below the 1% threshold set by Visa.”

Practical Phrases for Fintech Developers

• “The nightly reconciliation job found a £240 discrepancy — it turned out to be a refund that processed after the settlement batch ran.”
• “Always pass an idempotency key when calling the payments API. If you don’t, retries will create duplicate charges.”
• “The ledger is append-only. We never update or delete rows — we issue a correcting entry instead.”
• “We’re moving to ISO 20022 to support richer payment data and comply with the SWIFT migration timeline.”
• “The clearing house introduces counterparty risk management between trade and settlement.”

Fintech vocabulary bridges two worlds — finance and software engineering. Mastering these terms will help you read API documentation, discuss system design with payment partners, communicate with compliance and finance teams, and build robust financial systems that handle money reliably and safely.