What a TradePactID Tells You: Invoice Status Verification and Privacy Guarantees
Learn how a TradePactID verifies B2B invoice status on tradepact.network, the 5-field public record contract, and zero-exposure privacy guarantees.

A TradePactID is a unique, 15-character alphanumeric identifier assigned to every commercial invoice managed under the TradePact Protocol. Printed on invoice correspondence sent by network participants, it allows any commercial counterparty holding the identifier to independently verify an invoice's current network status (Paid, Unpaid, or Unknown), masked invoice number, invoice date, and managing participant at tradepact.network—without exposing company names, contact details, or invoice amounts.
This guide is for finance directors, accounts payable teams, and commercial counterparties who have received correspondence referencing a TradePactID and want to understand how public status verification operates, what information is and is not disclosed, and how the TradePact Protocol enforces strict privacy boundaries.
Key Takeaways (TL;DR)
- Single-Record Verification: A
TradePactID(format: 14 digits followed by 1 uppercase check letter, such as20260813000001A) verifies the real-time status of a registered invoice at tradepact.network. - Strict 5-Field Public Contract: A public lookup returns only five fields: the
TradePactID, record status (Paid,Unpaid, orUnknown), a masked invoice number, the invoice date, and the managing network participant. - Zero Exposure of Parties or Amounts: The public status site never publishes creditor names, paying-party names, email addresses, phone numbers, line items, or invoice amounts.
- Anti-Enumeration & Search-Engine Isolation: Individual record URLs carry
noindexandno-storeheaders, are excluded fromsitemap.xml, and return byte-identical404responses for unknown or malformed identifiers so records cannot be scraped or enumerated. - Neutral, Non-Custodial Framework: TradePact Network is a shared receivables protocol and record framework operated by ChaseFlow Pte Ltd in Singapore—never a debt collector, credit bureau, or custodian of funds.
What Is a TradePactID?
A TradePactID is the canonical record reference for an invoice registered on the TradePact Network. Whenever an invoice enters structured engagement under the TradePact Protocol (effective January 1, 2026), the network infrastructure assigns it a unique identifier consisting of 14 numeric digits followed by a single uppercase ASCII letter (for example, 20260813000001A).
This identifier appears on correspondence—such as payment reminders, discrepancy notices, or resolution updates—sent by a network participant brand (such as InvoiceMediator or PaymentMediator). Its purpose is to give both parties a shared, verifiable reference point. Instead of relying solely on unverified emails or informal status claims, anyone holding the TradePactID can confirm that the correspondence originates from an authorized TradePact Network participant and check the current standing of the invoice record.
What Does a Public TradePactID Lookup Show?
A public TradePactID lookup on tradepact.network displays a strictly bounded, five-field status projection designed to verify record authenticity without disclosing confidential commercial terms.
At the code and protocol level, the public lookup endpoint enforces a closed five-field contract. The table below outlines exactly what is displayed on a valid TradePactID lookup and what is permanently excluded from the public surface:
| Data Element | Publicly Shown on tradepact.network? | How It Appears / Privacy Rule |
|---|---|---|
| TradePactID | Yes | Exact 15-character identifier (14 digits + 1 uppercase letter, e.g., 20260813000001A) |
| Record Status | Yes | Paid, Unpaid, or Unknown (reflecting the current network state) |
| Invoice Number | Yes (Masked) | Masked invoice reference (e.g., INV-***42) so only the genuine invoice holder recognizes it |
| Invoice Date | Yes | Issue date of the invoice (YYYY-MM-DD) |
| Managing Participant | Yes | Name, domain, and verified mark of the network participant managing the engagement |
| Creditor / Supplier Name | Never | Excluded from the public projection and public API response |
| Paying Party / Debtor Name | Never | Excluded from the public projection and public API response |
| Contact Details (Email / Phone) | Never | Excluded from the public projection and public API response |
| Invoice Amount & Currency | Never | Excluded from the public projection and public API response |
| Dispute Notes & Correspondence | Never | Restricted to authenticated parties within the engagement workflow |
Understanding the Three Status States
Unpaid: The invoice is currently registered under active protocol engagement and has not yet been confirmed as settled or closed.Paid: The creditor or network infrastructure has recorded settlement of the invoice, closing the active follow-up lifecycle.Unknown: The invoice record has been withdrawn, closed without a confirmed payment outcome, or its terminal settlement state is not attested on the public projection.
How Does TradePact Network Protect Counterparty Privacy?
TradePact Network protects commercial privacy by combining data minimization at the database projection layer with strict HTTP response controls that prevent search indexing, caching, and automated enumeration.
When a finance team sees an external lookup URL on an invoice notice, their first question is whether a public webpage is broadcasting their company's payable status to search engines or competitors. The architecture of tradepact.network prevents public exposure through four technical safeguards:
- Projection-Level Data Stripping: The public status service reads only from a restricted record projection. Party names, contact details, and financial amounts are not merely hidden in the browser interface—they are absent from the public data payload entirely.
- Search Engine Exclusion (
noindex): Every individual record lookup response (/:tradePactId) is served withX-Robots-Tag: noindexheaders and excluded fromsitemap.xml. Only the public homepage and educational/learnguides are indexable by search engines. - Zero Browser or Proxy Caching (
no-store): Record lookups returnCache-Control: no-store, ensuring that status checks performed on shared corporate networks are not retained in intermediate caches. - Byte-Identical 404 Anti-Enumeration: If an automated script attempts to guess or brute-force
TradePactIDstrings, every malformed identifier (404) and every valid-format but non-existent identifier (404) returns a byte-identical response body and status code. External observers cannot distinguish between a format error and an unregistered ID, preventing directory harvesting.
How Does the TradePact Network Operate Behind a TradePactID?
Every TradePactID is governed by the TradePact Protocol v1.0 (effective January 1, 2026), which organizes receivables engagement into three distinct layers operated by ChaseFlow Pte Ltd (UEN 202542183C) in Singapore:
- Infrastructure Layer (Operated by ChaseFlow): Provides the underlying communication rail, evidence logging, dispute resolution workflows, and the
tradepact.networkstatus record registry. - Participant Layer (e.g., InvoiceMediator, PaymentMediator): Distinct, protocol-admitted engagement brands that communicate with commercial parties and host dedicated resolution portals (
pay.<domain>). Every participant must display the TradePact Network mark, route exclusively through network infrastructure, and hold no conflicting financial interest in the outcome of an invoice. - Intelligence Layer (Operated by Late Payer Index): Aggregates anonymized or protocol-governed behavioral telemetry under the protocol's intelligence rules.
What TradePact Network Is Not
To avoid confusion with traditional receivables actors, the TradePact Protocol establishes strict operational boundaries:
- Not a Custodian or Payment Processor: No network participant holds funds belonging to a creditor or a paying party. All invoice payments are made directly between the commercial counterparties using the supplier's established payment rails.
- Not a Debt Collector or Enforcement Agency: Participants are prohibited by protocol admission rules from purchasing distressed debt, charging contingent collection commissions, or operating legal enforcement businesses. Engagement is neutral, administrative, and begins early in the invoice lifecycle.
- Not a Credit Bureau:
tradepact.networkdoes not sell public credit scores or publish company default directories.
What Should You Do If You Receive a Notice With a TradePactID?
If your accounts payable or finance team receives an email or notice carrying a TradePactID, follow three straightforward steps:
- Verify the Record Status: Visit tradepact.network and enter the 15-character
TradePactIDexactly as printed. Confirm that the masked invoice number, invoice date, and managing participant match the invoice in your accounting system. - Use the Participant Resolution Portal for Action: If the invoice is already paid, requires a billing adjustment, or has a commercial discrepancy, use the dedicated participant portal link (
pay.<domain>) provided in the correspondence to upload remittance proof or log the dispute reason directly into the shared audit trail. - Pay the Supplier Directly: When settling an undisputed invoice, remit payment directly to your supplier's verified bank account or payment link as stated on the original invoice.
Frequently Asked Questions
Does looking up a TradePactID reveal our company name or invoice amount to the public?
No. A lookup on tradepact.network enforces a strict five-field contract that displays only the TradePactID, the record status (Paid, Unpaid, or Unknown), a masked invoice number, the invoice date, and the managing network participant. Company names, individual contact details, line-item descriptions, and monetary amounts are never published on the website or returned in the public data payload.
Can search engines like Google index our invoice status page?
No. Every individual TradePactID lookup route on tradepact.network is served with strict noindex and no-store HTTP headers and is permanently excluded from the site's sitemap.xml. Search engines and web crawlers can index only the public landing page and general educational articles under /learn, keeping individual invoice status lookups completely out of search results.
Why does my TradePactID lookup return a 404 page?
A 404 response occurs when the 15-character TradePactID is mistyped, does not follow the required format of 14 digits followed by one uppercase letter, or does not correspond to a registered public record. For security and anti-enumeration reasons, tradepact.network returns an identical 404 response for both malformed entries and unknown identifiers.
Do we pay TradePact Network or the participant brand to settle an invoice?
Neither. TradePact Network and its participants are strictly non-custodial and never hold, process, or take custody of funds belonging to a creditor or paying party. You always remit payment directly to your supplier using the banking or payment instructions verified on your commercial invoice, after which the network record updates to Paid.
Is a TradePact Network participant a debt collection agency?
No. Under TradePact Protocol v1.0 admission rules, network participants are prohibited from operating a debt purchase, debt collection, or legal enforcement business and may hold no conflicting financial interest in an invoice's outcome. Participants act as neutral administrative intermediaries that help commercial counterparties verify billing status, log disputes, and coordinate timely resolution.
What happens to the TradePactID status once an invoice is paid?
Once payment is confirmed by the issuing business or recorded through the network infrastructure, the status associated with the TradePactID on tradepact.network updates from Unpaid to Paid. Either party can subsequently enter the TradePactID to verify that the obligation is recorded as settled under the protocol.
Verify a Record or Explore the Protocol
If you hold a TradePactID from recent invoice correspondence, you can verify its live status immediately on the TradePact Network status lookup or review the full operating rules in the TradePact Protocol v1.0 specification. To see how structured receivables engagement works in practice, Watch the customer journey, the interactive demo and get started for free.