Transform Bank Transfers into Conditional Payment Agreements
Layer Payment Instructions on top of ACH, wire, and SEPA rails to deliver conditional flows, multi-party approvals, and AI-ready banking—without replacing core systems.
Premium Services, AI Readiness, and Lower Risk
Payment Instructions unlock new revenue, prepare you for AI-driven treasury, shrink disputes, and improve risk visibility—all without touching core systems.
Premium Conditional Transfers
Layer programmable business rules on top of standard transfers. Launch branded conditional products that customers cannot get elsewhere.
AI Agent Banking Ready
Provide safe guardrails for autonomous procurement and treasury agents with programmable limits, approvals, and audit trails.
Reduced Disputes & Support Load
Shared evidence timelines eliminate “I never approved this”. Customers, vendors, and bankers work from the same source of truth.
Enhanced Risk Visibility
Understand the business context of each transfer. Hold funds, review conditions, and decline with reason codes when policies require.
The Business Case
Premium Product Above Standard Transfers
Turn conditional transfers into a line of business with differentiated pricing.
- Monetize conditional flows ($5–15 per transaction, milestone fees, approval workflows).
- Launch “Conditional Bank Transfers” as a branded product for commercial customers.
- Deepen retention—treasury teams stay once workflows depend on your Payment Instructions.
AI Agent Banking Market
Capture the inevitable surge in autonomous payment agents with safe, programmable accounts.
- Agents operate within spend limits and vendor allow-lists.
- Humans review exceptions while agents handle routine payments.
- Position your bank as the first choice for AI-enabled treasury teams.
Lower Disputes & Operations Cost
Every action is documented, reducing investigation time and support calls.
- Customers and vendors track reservation and capture status in real time.
- Evidence-backed resolution replaces manual “he said, she said” processes.
- Compliance teams export audit-ready timelines instantly.
Programmable Risk Management
Use Payment Instruction metadata to inform risk decisions before funds move.
- Hold funds immediately, capture only when verified conditions succeed.
- Set velocity limits and risk scoring by Payment Instruction type.
- Decline suspicious requests with clear reason codes logged to the timeline.
How Payment Instructions Operate on Your Rails
Customer (Payer)
Authorizes transfers with embedded business logic.
- Defines reservation and capture conditions (“pay after delivery”, “funds release when all approvers sign”).
- Monitors payment status and evidence in real time.
- Reserves cash only when rules dictate, improving working capital.
Bank (Guarantor)
Executes requests on existing rails with full control.
- Processes familiar events: `Reserve Funds Requested`, `Capture Funds Requested`, `Release Reservation`.
- Runs standard risk, AML, sanctions, and compliance screens before responding.
- Writes confirmations or decline reasons to the shared timeline.
Vendor (Payee)
Receives guarantees and visibility that reduce collections friction.
- Sees when funds are reserved and what evidence is required for release.
- Triggers capture once delivery or milestone conditions are satisfied.
- Spends less time chasing payments—knows exactly where funds stand.
Business logic—delivery confirmations, approvals, dispute windows—lives inside the Payment Instruction. You continue to receive and process standard payment requests while the protocol ensures transparency and synchronisation between parties.
Integration Strategy Options
Choose your level of control—no vendor lock-in. Banks can adopt Payment Instructions through three integration levels, balancing speed-to-market with operational control. Start at any level and migrate freely. The Payment Instruction specification is open—documents remain portable across all approaches.
Level 1 · MyOS-Powered Integration
Best for: Rapid pilot and initial deployment.
- MyOS handles all Payment Instruction document processing.
- You receive webhooks and run events through existing operations.
- Respond via simple APIs with confirmations or decline reasons.
- Reference implementation: demo bank app
Level 2 · Verification-Based Integration
Best for: Enhanced security while keeping operational efficiency.
- Continue Level 1 processing with MyOS.
- Deploy your own Blue processor to verify state changes independently.
- Receive both MyOS results and the triggering events for audit.
- Add the verification layer without disrupting ongoing operations.
Level 3 · Independent Integration
Best for: Maximum autonomy and control.
- Run your own timeline infrastructure and Blue processors.
- Remove dependencies on MyOS while maintaining protocol compliance.
- Full control over monitoring, logging, and processing pipelines.
- Requires greater technical investment and ongoing maintenance.
Key Point: Starting at Level 1 does not lock you in. The Payment Instruction specification is open—any compliant processor produces identical results. Move between levels as your business needs evolve.
Your Brand, Your Experience
Payment Instructions are a data protocol, not a UI framework. Integrate the logic into your existing online banking, mobile app, or business portal — however your customers expect to see it.
Payment to Bob's Shop
$220.00
- Payer
- Alex Morgan
- Payee
- Bob's Shop
- Guarantor
- Your bank
Agreed conditions
Reserve $220. Release the payment when the shipping provider confirms delivery. Return the funds if delivery is not confirmed within 7 days.
Shared timeline
Payment authorized
The payer approved the amount and release conditions.
Funds reserved
Your bank reserved $220 for this purchase.
Delivery confirmed
The shipping provider recorded proof of delivery.
Funds released
$220 transferred to Bob's Shop.
View evidence
The shipping provider confirmed delivery. The bank recorded the matching settlement confirmation in the shared timeline.
Use Cases Driving Adoption
Construction Progress Payments
Reserve the full project amount and release staged payments when inspectors sign off. Everyone sees milestone status.
- Revenue: $25–50 per milestone + ~0.1% project fee.
Corporate Treasury Multi-Approval
Encode CFO, controller, and compliance approvals before funds leave the account. Full audit trail without manual tracking.
- Revenue: $15–25 per multi-approval transaction.
Invoice Financing with Net Terms
Schedule Net-30 captures with automatic holds when disputes are raised. Vendors see reserved funds, buyers retain dispute rights.
- Revenue: $10–20 per conditional invoice payment.
AI Agent Procurement
Allow autonomous agents to pay under strict rules (“under $5K, approved vendors, delivery confirmed”) with human oversight for exceptions.
- Revenue: Premium AI agent account ($50–100/month + transaction fees).
Equipment Leasing Milestones
Coordinate deposit, delivery, and installation payments with automated triggers. Reduce friction for lessee and lessor.
- Revenue: $20–40 per milestone + ~0.15% equipment value.
Real Estate Escrow
Hold earnest money and release at closing when title company, buyer, and seller confirm. Faster than third-party escrow services.
- Revenue: $200–500 per escrow transaction.
Compliance & Risk Benefits
Compliance Enhancements
Payment Instructions improve documentation across AML, KYC, and audit obligations.
- Purpose of transfer explicitly stated; evidence timeline exportable for regulators.
- Every request, approval, and decline is timestamped and signed.
- Multi-party approvals and documents captured in one immutable record.
Risk & Liability Model
You remain in control—Payment Instructions make liability boundaries clearer.
- You execute only the conditions authorized by the customer.
- Decline requests when funds, compliance, or policy checks fail.
- If you process correctly, the Payment Instruction timeline evidences your compliance.
Partner with us to launch Payment Instructions
Collaborate with the team behind Payment Instructions to scope your pilot, align stakeholders, and deliver conditional banking on your existing rails.