Selected Work Case Study 01
IranPay — Designing Financial Operations Infrastructure
An RFQ-based operations design that separates a price, a reservation and a confirmed obligation on the path to settlement.
When the desk, the payment team and operations hold different views of the same request, a price can be mistaken for a commitment. The design question is how to keep commercial intent and delivery obligations distinct as a request moves between people and systems.
Project context
The publicly documented IranPay design brings pricing, reservations, payments, settlement and operational oversight into one workflow. It addresses handoffs among a requester, a quoting desk and the people responsible for delivery and review. This case study explains the public design scope; it does not document a product launch or certify a deployed control.
Conceptual workflow
From a request to a reconciled obligation
Define the request
Capture the instrument or currency, direction, size and proposed settlement terms.
Quote and reserve
Attach a price and validity to those terms. Treat any reservation as a separate, time-bounded commitment of capacity.
Establish acceptance
Tie acceptance to the exact quote version. Verify the authoritative trade status before treating delivery as due.
Settle and reconcile
Track each delivery leg through confirmation and reconcile the remaining obligations.
Design decisions
Separate economic terms from operational state
A price belongs to a versioned quote. Reservation, acceptance, execution and settlement describe different facts. Combining them into one status makes it hard to tell whether capacity is reserved, a trade was agreed, or a delivery is still outstanding.
Make pending states usable
An expired quote can call for a new price; an unconfirmed acceptance calls for checking what happened. Keeping those states distinct lets an operator take the next safe step without repeating an economic instruction.
Track obligations on both sides
A confirmed trade can still have outstanding payments or deliveries. Reconcile the obligations and evidence for each leg separately, and keep exceptions visible until resolved.
Operational risk and reliability
A useful failure scenario is a dropped connection after acceptance. The absence of a reply leaves the outcome unknown. Before retrying, reconcile the original request against the authoritative state. Where a protocol supports duplicate prevention, preserve the request identity under its rules. In a cash or remittance workflow, a handoff or receipt may require separate evidence; the interface should not infer final settlement from a handoff alone.
Contribution
Seyed Iman Hosseini’s documented project focus covers financial workflow design, the operating model, RFQ logic and execution-oriented infrastructure. This is a statement of the areas he contributed to, not an assignment of sole ownership or credit for individual components.
What the design teaches
The main design lesson is that an operational status should tell the next person what is known, what remains owed and who can act. There are no public rollout, transaction-volume or performance results in this case study.
Related insights
- OTC Execution in Practice
Follow the distinction between quote acceptance, confirmation and settlement.
- Order Book Execution Simulator
Test how size changes a hypothetical execution benchmark before comparing an OTC quote.
Discuss the work
For professional conversations on execution, financial operations and market infrastructure.