Use a computer

For full performance and fluidity, please open Pay Engineers on a desktop or laptop. On mobile, the experience is limited — especially authenticated sections and advanced tools after login.

Pay Engineers Pay Engineers
Connexion
Langue
Accueil
Processeur sur mesure Infrastructure de paiement sur mesure Configurateur Concevez votre processeur Espace Stripe Opérations Stripe connectées Conformité Autorisations et licences
Tous les services Offres d'ingénierie et de conseil Commander un processeur Démarrer un projet sur mesure Déposer une réclamation Service réclamations
Guides processeur Architecture et bonnes pratiques Documentation API (opens in a new tab) Documentation développeur Blog Product & engineering notes
À propos Who we are Contact Talk to our team
Create an account

Payment Infrastructure

Escrow Engine

Conditional release of funds

Presentation

Overview

Escrow exists to solve a simple but persistent problem in commerce: a buyer does not want to pay before receiving what they were promised, and a seller does not want to deliver before being paid. Pay Engineers builds escrow engines that hold funds neutrally between two or more parties and release them only when contractually defined conditions are satisfied, giving both sides confidence to transact.

This is not a generic hold-and-release feature bolted onto a checkout. It is a dedicated engine modelling milestones, conditions, disputes and evidence, because in practice escrow only earns trust when the rules around release and dispute are transparent, consistently enforced and fully auditable after the fact.

We design the engine so that dispute handling is a core feature rather than an exception path, since disputes are precisely the moments when the value of a well-built escrow system becomes most visible to the parties relying on it.

Who This Is For

  • B2B marketplaces where transaction values are high enough that trust needs an explicit mechanism
  • Freelance and services platforms managing milestone-based project payments
  • Platforms trading in high-value goods, such as property deposits, vehicles or luxury items
  • Any business that currently manages conditional fund holding manually through bank transfers and email confirmations

What You Get

  • Milestone-based release logic so funds move automatically when predefined delivery or approval conditions are met
  • Dispute handling workflows that pause release, collect evidence from both parties and support a documented resolution
  • An immutable audit trail recording every hold, milestone update, release and dispute event with full timestamps and actor identity
  • Webhook notifications so your platform and both counterparties stay informed of status changes in real time

Technical Approach

The engine is built on Laravel with PostgreSQL as the durable store for escrow state, and we apply event-sourcing patterns to the escrow lifecycle specifically: every state transition, from initial fund hold through milestone completion to final release or refund, is recorded as an immutable event rather than an in-place update. This gives you a system where the current state is always derivable from history, and history can never be silently altered.

Milestones are modelled as a configurable sequence rather than a single hold-and-release step, so you can support anything from a simple two-party transaction to multi-stage project payments with partial releases at each stage. Dispute workflows branch the milestone sequence into a formal resolution path, capturing evidence, timelines and the eventual outcome as part of the same permanent event log used for the happy path.

Delivery Process

  • Discovery of your transaction types, typical milestone structures and dispute scenarios
  • Escrow and milestone data model design, reviewed against real-world edge cases such as partial delivery or late disputes
  • Sprint-based build of core hold and release logic, followed by dispute workflows and notifications
  • Scenario testing across happy-path releases, partial releases, disputes and refund cases
  • Rollout starting with a controlled transaction category before extending to your full catalogue

Outcomes and Benefits

  • Higher buyer and seller confidence in high-value or first-time transactions on your platform
  • A defensible, timestamped record of every escrow decision, valuable in the event of a legal or regulatory challenge
  • Reduced manual intervention in dispute handling through structured evidence collection
  • A flexible milestone model that can support new transaction types as your platform grows

Technologies

Laravel PostgreSQL Event sourcing patterns

FAQ

Milestones and release conditions are modelled as structured, configurable rules rather than free-text agreements, so the engine can evaluate automatically when a condition is met, for example delivery confirmation, inspection period expiry, or explicit buyer approval. Complex transactions can have multiple sequential or parallel milestones, each releasing a portion of the held funds, which suits high-value goods or milestone-based service agreements. Every rule change and its effective date is versioned, so historical transactions are always evaluated against the rules that applied when they were created. This structured approach is what makes the engine auditable rather than reliant on manual judgement calls.
The engine includes a dedicated dispute workflow that freezes the relevant held funds, collects evidence from both parties, and routes the case to a resolution process, whether that is your own operations team, a configured arbitration rule, or a third-party resolution service. Every piece of evidence, communication and decision is timestamped and retained, producing an audit trail that stands up if a dispute later escalates to a formal complaint or legal action. Partial releases are supported where a dispute only concerns part of a milestone, so the whole transaction does not need to stay frozen over a partial disagreement. This is engineered as a first-class feature rather than an exception path, since dispute handling is where escrow systems earn or lose trust.
Escrowed funds are tracked in a dedicated ledger structure separate from operating or fee revenue, reflecting the fact that held funds belong to the transacting parties, not to your business, until release conditions are met. Depending on your regulatory position and jurisdiction, this is paired with appropriately segregated bank accounts or safeguarding arrangements, which we discuss with your legal and compliance advisors during scoping since holding client funds often has specific regulatory implications. The ledger design makes it straightforward to demonstrate, at any point, exactly which funds are held for which transaction and why. This segregation is typically one of the first things auditors and regulators check in an escrow business.
Yes, the engine is designed to plug into an existing marketplace, freelance platform or checkout system through an API, so you do not need to rebuild your buyer or seller-facing experience to add escrow protection. We map your existing transaction and order data into the milestone model during integration, and expose webhooks so your platform can reflect hold, release and dispute status in real time. Where you already have a payment processor or gateway in place, escrow sits as a logical layer on top rather than replacing that relationship. This keeps the integration scope focused and predictable.
A first release covering fund holding, basic milestone release and manual dispute handling typically takes 10 to 14 weeks, with automated multi-milestone rules and more sophisticated dispute workflows following in later phases. Timeline depends on how many distinct transaction types and release rule variations you need to support at launch. We recommend starting with your highest-value or highest-risk transaction type, since that is usually where escrow delivers the clearest business value first. Integration with your existing platform's order and user data is typically the largest variable in the schedule.

Similar services

Custom Payment Processor

We design and build independent payment processors that give fintechs, banks and platforms full ownership of authorisation, routing, settlement and risk logic. The engagement spans scheme connectivity, merchant lifecycle management, fee configuration and compliance hooks, engineered around your corridors and volumes. You end up with a processor you can extend, audit and scale on your own roadmap, not a black box you rent from someone else.

Payment Gateway

A production-grade payment gateway connecting your checkout to acquirers, card schemes and local payment methods, engineered around strong customer authentication and tokenised credentials. We handle 3-D Secure and SCA orchestration, smart transaction routing and webhook-driven integration so your checkout converts more customers while staying compliant with PSD2 and scheme mandates.

Merchant Portal

A branded merchant portal giving your merchants self-service visibility into onboarding status, transactions, statements, disputes and payout schedules. Role-based access control and full audit logging let you extend access safely across finance, support and management users within each merchant account. The portal reduces support ticket volume while giving merchants the transparency modern payment businesses expect.