The TradePact Protocol: Principles, Participant Roles, and Neutral Receivables Engagement

Discover how the TradePact Protocol establishes a shared standard for neutral B2B receivables engagement, participant roles, and commercial trust.

The TradePact Protocol v1.0 is a shared trust framework and operating standard for transparent B2B receivables engagement, payment resolution, commercial trust, and responsible behavioral intelligence. Effective January 1, 2026, and operated by ChaseFlow Pte Ltd, the protocol governs how specialized network participants communicate, resolve invoice disputes, exchange verifiable evidence, and coordinate payment outcomes. It exists to replace fragmented bilateral chasing with an auditable, neutral operating standard that protects commercial counterparty relationships while accelerating resolution.

This guide explains how the protocol functions across its three architectural layers, the six commitments required of every network interaction, the clear legal and operational boundaries that distinguish the network from debt collectors and credit bureaus, and the published admission criteria for organizations joining the network.

Key Takeaways (TL;DR)

A Shared Operating Standard: The TradePact Protocol separates the participant brand engaging a customer from the underlying execution infrastructure and behavioral reporting.
Three-Layer Architecture: The network operates through Infrastructure (managed by ChaseFlow), customer-facing Participants (such as InvoiceMediator and PaymentMediator), and Intelligence (operated by Late Payer Index).
Six Core Commitments: Every network touchpoint is governed by strict rules on Communication, Resolution, Evidence, Intelligence, Accountability, and Interoperability.
Strictly Non-Custodial & Non-Adversarial: The protocol is neither a debt collection agency nor a payment processor. No participant holds client or debtor funds; all payments flow directly between commercial counterparties.
Admission by Standard: Independent billing platforms, accounting providers, and trade bodies can deploy branded engagement portals under the "Bring the brand. We run the rail." model, subject to four published criteria.

What Is the TradePact Protocol?

Commercial trade depends on predictable cash flow, yet payment follow-up has historically been fragmented across disconnected internal systems, ad-hoc spreadsheets, and unilateral communications. When an invoice falls overdue, traditional approaches often swing between two unhelpful extremes: hesitant administrative follow-up that permits severe delinquency, or aggressive, adversarial escalation that permanently fractures commercial goodwill.

The TradePact Protocol establishes an institutional standard for receivables engagement. Rather than leaving follow-up norms to individual discretion, the protocol introduces a structured, neutral operating framework applied from the date an invoice is issued. Every interaction conducted under the protocol is logged, transparent, and proportionate to the invoice lifecycle.

By establishing common standards across specialized service providers, the protocol transforms receivables from an emotional point of commercial friction into an objective administrative process. Every invoice registered under the protocol receives a unique 15-character TradePactID, enabling counterparties to verify record status on tradepact.network under strict privacy guarantees.

How Is the TradePact Network Organized Across Its Three Layers?

The TradePact Network separates brand engagement, technical execution, and behavioral intelligence into three distinct layers governed by one shared protocol (https://tradepact.net/protocol).

Network Layer	Operated By	Core Responsibility Under the Protocol
1. Infrastructure Layer	ChaseFlow	Operates the core communication engine, evidence registry, structured resolution workflows, and the public `tradepact.network` status record system.
2. Participant Layer	Network Participants (e.g., InvoiceMediator, PaymentMediator)	Provides the distinct, party-facing engagement brand and resolution portal (`pay.<domain>`) that interacts with suppliers and paying parties under protocol rules.
3. Intelligence Layer	Late Payer Index (LPI)	Processes protocol-governed behavioral payment telemetry in accordance with the protocol's intelligence and accountability commitments.

This separation of concerns solves a critical structural problem in commercial finance: suppliers and billing platforms want professional, third-party administrative authority without handing their customer relationships to unregulated collection agencies or building complex telephony and audit infrastructure from scratch.

What Are the Six Core Commitments of the TradePact Protocol?

Every network participant and infrastructure touchpoint must adhere to six binding commitments defined in TradePact Protocol v1.0:

Communication: All outreach is professional, factual, and proportionate. Communications identify the managing participant clearly, reference the invoice's TradePactID, and state the exact administrative action required without harassment or coercion.
Resolution: The protocol prioritizes early identification of administrative blockers. Paying parties are given a structured channel (pay.<domain>) to confirm payment dates, request restructuring, or flag genuine commercial disputes (such as missing purchase orders or delivery discrepancies) before an account escalates.
Evidence: Every outreach attempt, delivery receipt, portal interaction, and party response is recorded in a tamper-evident, chronological audit trail. Both parties benefit from an objective record of what was communicated and when.
Intelligence: Behavioral payment data is handled responsibly and objectively, distinguishing between verified commercial disputes and uncommunicative delinquency.
Accountability: Participants operate under transparent governance. Every party-facing touchpoint displays the TradePact Network mark and links to the governing protocol standards.
Interoperability: Because all participants run on shared protocol definitions and status states (Paid, Unpaid, Unknown), records and interaction histories follow a uniform structure across the network.

How Does the Protocol Differ From Debt Collection and Software Tools?

The TradePact Protocol defines strict operational boundaries that separate it from legacy receivables categories:

Non-Custodial Direct Settlement: Neither TradePact Network nor any network participant acts as a payment processor, escrow agent, or custodian of funds. Paying parties remit funds directly to the creditor's designated bank account or payment facility.
Prohibition on Debt Collection and Debt Purchase: Network participants are barred from purchasing distressed receivables, charging contingent recovery percentages, or conducting legal enforcement. Engagement is administrative and neutral.
Not a Public Credit Bureau: While every managed invoice carries a TradePactID for counterparty verification at tradepact.network, the public record discloses only five fields (identifier, status, masked invoice number, invoice date, and managing participant) and never publishes party names, contact details, or monetary amounts.
Managed Rail vs. Self-Hosted Software: Participants do not deploy standalone software instances. All protocol workflows run on centralized network infrastructure operated by ChaseFlow to guarantee compliance with the six protocol commitments.

How Do Organizations Join as Network Participants? ("Bring the Brand. We Run the Rail.")

While network participants today are operated by ChaseFlow, the TradePact Network is designed to admit eligible external organizations—such as billing and accounting platforms, business service firms, and industry trade bodies—that sit close to commercial invoicing.

Under the "Bring the brand. We run the rail." model, an admitted participant supplies a dedicated engagement brand (domain name, visual identity, and pay.<domain> subdomain), while ChaseFlow operates the underlying communication, evidence, resolution, and record-keeping infrastructure.

To protect the integrity of the trust framework, TradePact Protocol v1.0 requires every applicant to satisfy four admission criteria:

Distinct Engagement Brand: The participant must operate under a dedicated engagement brand and domain separate from its primary commercial product brand.
Protocol Attribution: The participant must display the TradePact Network mark on every party-facing communication and portal page.
Exclusive Network Routing: All receivables communications, resolution workflows, and status projections must route through the network infrastructure.
Neutrality & No Conflicting Financial Interest: The participant must hold no conflicting financial interest in the outcome of managed invoices and must not operate a debt purchase, debt collection, or enforcement business.

Organizations interested in operating a participant brand can review the specification at tradepact.net/protocol and apply via participants@tradepact.net.

Frequently Asked Questions

Who operates the TradePact Network and Protocol?

The TradePact Network and TradePact Protocol v1.0 (effective January 1, 2026) are operated by ChaseFlow Pte Ltd (UEN 202542183C), registered in Singapore. ChaseFlow operates the core technical infrastructure and record registry, while individual engagements are conducted through protocol-admitted participant brands such as InvoiceMediator and PaymentMediator.

Does a TradePact Network participant take custody of invoice payments?

No. Under the TradePact Protocol, no participant ever holds, processes, or takes custody of funds belonging to a creditor or a paying party. All invoice settlements are paid directly between the commercial counterparties using the supplier's established banking or payment instructions.

How does neutral receivables engagement preserve commercial relationships?

When a supplier chases its own overdue invoices, conversations quickly become personal—forcing account managers to choose between pressing for cash and preserving client goodwill. By routing follow-up through a neutral participant brand governed by published protocol rules, payment verification and dispute logging are handled as routine, objective administration.

What happens when a paying party raises a dispute under the TradePact Protocol?

Under the protocol's Resolution and Evidence commitments, a paying party can log a dispute or billing discrepancy directly through the participant's resolution portal (pay.<domain>). This immediately records the issue and supporting documentation in the shared audit trail so the creditor can resolve the discrepancy rather than continuing routine payment reminders.

Can an accounting platform or trade association launch its own participant brand?

Yes. Eligible billing providers, business service firms, and trade bodies can apply to join the network under the "Bring the brand. We run the rail." model. Admitted organizations provide a distinct engagement brand and domain while ChaseFlow operates the underlying communication, resolution, and status-record infrastructure.

Explore the Protocol or Verify a Record

Review the full text of the TradePact Protocol v1.0 specification, verify an existing invoice record using its 15-character identifier on tradepact.network, or see how managed protocol workflows operate in practice: Watch the customer journey, the interactive demo and get started for free.