Transfer by Paper Oracle Private build

Workflow layer for conditional transactions

Coordinate payments with clear conditions and outcomes.

Transfer is a focused workflow system that coordinates how transactions progress when conditions, timing, or partial completion matter. It provides a shared, structured view of states and outcomes while relying on external payment services to execute movement of funds.

Explicit states instead of guesswork
Designed for changes, delays, and disagreement

Who it’s for

People and platforms that need predictable outcomes.

Transfer is intentionally narrow. It’s built for situations where a simple payment isn’t enough, but building a fully custom system would be unnecessary.

Individuals

High-value exchanges or collaborations where both sides want to agree on conditions and next steps before money changes hands.

Freelancers & teams

Project-based work with milestones, partial delivery, or evolving scope that benefits from shared expectations.

Platforms & marketplaces

Transaction flows that require structure and visibility without replacing existing payment infrastructure.

Operators & finance leads

People responsible for understanding what happened, why it happened, and what comes next when transactions don’t follow the happy path.

How Transfer works

Define the rules before outcomes occur.

Transfer structures the workflow around a transaction so that expectations, conditions, and possible outcomes are clear before execution.

01

Create

Define participants, roles, amounts, and conditions in a single workflow.

  • Specify what completion looks like for each side.
  • Define who can signal progress or request changes.
  • Set expectations for how disagreements are handled.
02

Confirm

Participants review and agree on the workflow before execution begins.

  • Everyone sees the same conditions and timelines.
  • Updates and revisions are recorded transparently.
  • External payment services are prepared based on the agreed structure.
03

Progress

As events occur, the workflow advances according to predefined rules.

  • Outcomes follow agreed paths rather than ad-hoc decisions.
  • Context and evidence remain attached to each state.
  • Edge cases follow the same logic as standard flows.

Under the hood

A workflow system that complements payment rails.

Transfer does not act as a bank, payment processor, or custodian. Payments are executed by third-party services, while Transfer focuses on coordinating states, rules, and outcomes around those transactions.

  • External providers manage accounts, compliance, and fund movement.
  • Transfer manages workflow states and transition logic.
  • Each state change is recorded with context, timing, and the triggering input so outcomes can be understood after the fact.