How to Verify Third-Party Invoice Correspondence and Participant Notices on the TradePact Network
Learn how to verify third-party invoice correspondence, participant notices, and pay.<domain> portals on TradePact Network using 3-step verification.
Finance and accounts payable teams receiving invoice payment correspondence, reminders, or portal links from an unfamiliar third party face a critical operational challenge: distinguishing legitimate, authorized receivables engagement from fraudulent payment redirection schemes. When commercial correspondence references a TradePactID or originates from a TradePact Network participant—such as InvoiceMediator or PaymentMediator—the authenticity of the communication can be verified independently through a structured, three-step inspection protocol.
Under TradePact Protocol v1.0 (effective January 1, 2026, operated by ChaseFlow Pte Ltd, Singapore UEN 202542183C), commercial communications are decoupled from predatory collection practices. Instead, the network provides a transparent, rule-governed trust framework where commercial counterparties can verify record integrity, validate participant credentials, and confirm payment instructions without exposing confidential billing details to the public.
Here is the complete operational guide for corporate treasurers, controllers, and accounts payable specialists to verify third-party invoice notices, validate participant brand domains, and protect company cash flows.
What Is a TradePact Network Participant Notice?
A TradePact Network participant notice is an official receivables communication issued by an authorized engagement brand operating under the TradePact Protocol. Rather than employing aggressive or unverified third-party debt collection agencies, suppliers operating on network infrastructure engage commercial counterparties through designated participant brands such as InvoiceMediator or PaymentMediator.
Unlike traditional collection letters, every legitimate participant notice contains three distinct elements:
- A Canonical TradePactID: A unique 15-character alphanumeric identifier (for example,
20260813000001A) permanently assigned to the underlying invoice record. - Participant Identity Disclosures: Clear identification of the managing participant brand operating the engagement, referencing TradePact Protocol standards.
- A Dedicated Portal Reference: An authorized payment or dispute resolution link formatted strictly as
pay.<participant-domain>, allowing the recipient to review transaction details, submit documentation, or confirm settlement terms.
Understanding this architecture ensures that internal accounts payable personnel do not mistake legitimate, structured dispute resolution and reminder workflows for unauthorized external solicitations.
The Three-Step Verification Checklist for Accounts Payable Teams
When invoice correspondence bearing a TradePactID or participant brand mark arrives, accounts payable teams should execute this systematic three-step verification checklist before updating internal records or releasing funds.
Step 1: Validate the TradePactID Format and Query the Public Registry
Every legitimate TradePact record is indexed by a canonical 15-character TradePactID. To verify that the correspondence corresponds to an active, registered invoice:
- Locate the TradePactID printed on the notice, header, or portal link.
- Navigate directly to the official public status registry at
https://tradepact.network(avoid clicking unverified email hyperlinks if email headers appear suspicious). - Enter the 15-character identifier into the public lookup interface.
The public registry validates the query through strict format validation and checksum verification. If the identifier does not conform to the canonical format or does not exist, the network responds with a neutral, byte-identical 404 status to prevent automated database scraping and enumeration.
Step 2: Match the 5-Field Public Record Contract Against Internal Records
When a valid TradePactID is queried on https://tradepact.network, the network returns an immutable, five-field closed public record:
| Field | Expected Format / Value | Operational AP Verification Check |
|---|---|---|
| TradePactID | 15-character alphanumeric string (e.g., 20260813000001A) | Must match the identifier on the received notice character-for-character. |
| Status | Strictly Paid, Unpaid, or Unknown | Confirms whether the network currently tracks the obligation as outstanding or settled. |
| Masked Invoice Number | Prefix and suffix preserved (e.g., INV-***-0492) | Match the unmasked characters against your internal ERP purchase order and vendor invoice numbers. |
| Invoice Date | Standard ISO format (YYYY-MM-DD) | Confirm that the invoice issuance date corresponds with internal delivery or service logs. |
| Managing Participant | Authorized brand name (e.g., InvoiceMediator) | Must match the sender identity and signature on the payment notice. |
Because TradePact Network enforces strict data minimization, the public registry never discloses creditor names, debtor names, contact details, line-item descriptions, or invoice monetary values. Accounts payable controllers perform three-way matching internally by corroborating the masked invoice number, invoice date, and supplier billing records.
Step 3: Verify Payment Routing and Non-Custodial Settlement Integrity
The most vital verification step concerns the routing of funds. Under TradePact Protocol v1.0, the network operates on a strictly non-custodial framework:
- No Participant Holds Funds: Neither TradePact Network, ChaseFlow Pte Ltd, nor any participant brand (including InvoiceMediator and PaymentMediator) ever collects, holds, escrow, or processes invoice settlement monies.
- Direct Remittance Only: All payments must be remitted directly to the original supplier's verified corporate bank account, or through the direct payment gateway established on the supplier's authenticated merchant account.
- Warning on Bank Detail Changes: If any correspondence claiming to represent a TradePact participant demands payment to an unfamiliar intermediary bank account, escrow agent, or third-party payee, treat the communication as potentially compromised. Always verify bank account updates via an out-of-band telephone call to the supplier's verified finance director.
How to Verify B2B Payment Portal Subdomains (pay.<domain>)
Legitimate participant notices frequently direct recipients to an online portal to review statement histories, upload delivery receipts, raise billing queries, or initiate settlement. To verify that a portal subdomain is authentic and secure, evaluate the following technical and architectural safeguards:
1. Canonical Domain Structure
Authorized network participant portals operate strictly on dedicated subdomains formatted as pay.<participant-domain> (such as pay.invoicemediator.com or pay.paymentmediator.com). These portals communicate with the underlying network infrastructure over a secure, authenticated interface (/_portal/v1). Any correspondence directing payments to generic URL shorteners, raw IP addresses, or misnamed domain variants should be flagged immediately.
2. Token-Scoped Session Security
When accessing an authorized pay.<domain> portal, access is strictly scoped via cryptographic debtor tokens. The portal does not require the recipient to create arbitrary user logins or expose corporate network credentials. If an external portal demands corporate single sign-on (SSO) credentials, administrative passwords, or email logins, immediately disconnect: authentic TradePact portals never request third-party authentication credentials.
3. The 'I Don't Recognize This Company' Failsafe
To protect recipients from erroneous billings or misdirected notices, authentic debtor payment pages feature a standardized reporting link: "I don't recognize this company" (invoice.unrecognizedCompany). Clicking this link allows an accounts payable officer to submit a formal clarification request directly through the portal seam. This action prompts the declaring business to confirm invoice validity and re-establish direct communication, ensuring transparent commercial accountability.
Network Safeguards: TradePact Network vs. Collection Agencies vs. Private Portals
To understand the legal and operational protections governing TradePact correspondence, accounts payable managers can contrast the network model against traditional third-party intermediaries:
| Feature / Safeguard | TradePact Network Protocol | Traditional Debt Collection Agencies | Proprietary Vendor Billing Portals |
|---|---|---|---|
| Settlement Custody | Strictly non-custodial; direct creditor payment | Often custodial; funds held in agency trust accounts | Direct processor routing or proprietary balance holding |
| Public Privacy Protections | 5-field data minimization; zero names or amounts | Public court filings, gazette listings, or credit bureau alerts | Private silos requiring multi-factor authentication per vendor |
| Search Engine Indexing | Hard X-Robots-Tag: noindex and Cache-Control: no-store | Public records frequently indexed by search engines | Generally authenticated and inaccessible to public search |
| Intermediary Fee Model | Fixed infrastructure rails; zero percentage commissions | Contingency fees (10% to 50% deducted from debt) | Subscription or per-transaction vendor processing fees |
| Anti-Scraping Defenses | Byte-identical 404s, IP rate limits, 6-hour staleness cutoffs | Unprotected portals or public gazette registries | Variable proprietary bot-mitigation controls |
Frequently Asked Questions
How can I verify that an invoice notice from InvoiceMediator is authentic?
To verify an invoice notice from InvoiceMediator, locate the 15-character TradePactID on the document and enter it at https://tradepact.network. Verify that the public status record displays InvoiceMediator as the Managing Participant, matches the masked invoice number prefix/suffix against your purchase orders, and confirms that payment instructions route directly to your contracted vendor rather than a third-party intermediary.
What should I do if a PaymentMediator reminder lists an invoice my company already paid?
Query the TradePactID on https://tradepact.network to check the recorded status. If the status reflects Unpaid despite completed remittance, follow the secure link to the participant's pay.<domain> portal and submit payment proof, or utilize the "I don't recognize this company" link to notify the creditor. Because the network synchronizes ledger events every five minutes, bank reconciliation updates propagate rapidly across the projection.
Does verifying an invoice on TradePact Network expose our commercial data to competitors?
No. TradePact Network enforces strict data minimization under the TradePact Protocol. The public lookup registry renders only five closed fields: TradePactID, status (Paid, Unpaid, or Unknown), masked invoice number (e.g., INV-***-0492), invoice date, and managing participant. Creditor names, debtor names, line items, banking numbers, and invoice monetary amounts are never stored or displayed on the public lookup surface.
Can third-party collection agencies register records on TradePact Network?
No. TradePact Protocol v1.0 strictly prohibits debt purchasers, contingent collection agencies, and legal enforcement businesses from participating in the network. Admission requires operating under neutral dispute resolution standards, maintaining non-custodial settlement flows, and adhering to transparent communication guidelines.
Why does the TradePactID lookup return a 404 error for my invoice reference?
A 404 response indicates that the queried identifier is either formatted incorrectly or does not exist within the active network registry. TradePact Network returns byte-identical 404 Not Found responses for all missing or malformed inputs to prevent malicious actors from harvesting valid invoice references. Confirm that the 15-character alphanumeric ID was entered accurately without spaces or hyphens.
Is TradePact Network a payment gateway or payment processor?
No. TradePact Network is a neutral protocol and record verification framework operated by ChaseFlow Pte Ltd. It is neither a payment processor, money transmitter, custodian of funds, nor credit bureau. All commercial transactions settle bilaterally between the commercial buyer and the original supplier.
Strengthen Your Receivables Governance and Payment Resolution
Establishing transparent, verified communication between commercial trading partners eliminates billing friction, prevents invoice fraud, and accelerates dispute resolution.
Watch the customer journey, the interactive demo and get started for free