TL
TideLinxProof of concept
Home

Proof of Concept

Real-Bank Payment Verification — Proof of Concept

TideLinx is building an external-payment verification and commerce-authorization workflow that uses institution-originated transaction data. A controlled real-money banking transaction will be recorded here when the evidence package exists.

Proof Status: PENDING Review

What Was Tested

The intended test sends a real payment to a designated Mercury account, lets it appear in that institution's transaction records, exports the transaction data, and securely imports the file into TideLinx.

TideLinx then normalizes the institution-specific record, reconciles the incoming payment against an existing receivable, evaluates the transaction against verification rules, generates a commerce authorization, and transmits that authorization to a connected application.

This page does not claim that the live $10.17-class settled payment for TLX-POC-MERCURY-001 has been Review-signed. Status is read from the frozen database record. If that fetch fails, the page stays PENDING. A synthetic fixture path exists so Review can walk the software. Public proof stays pending until Review signs.

Test Architecture

Real Bank Payment → Mercury → Institution-Originated CSV → TideLinx Institution Adapter → Normalization → Reconciliation → Verification → Commerce Authorization → Connected Application

┌──────────────────────┐
│ Commerce Application │
└──────────┬───────────┘
           │ Receivable
           ▼
┌──────────────────────┐
│      TideLinx        │
│ Reference Generation │
└──────────┬───────────┘
           │ Real Payment
           ▼
┌──────────────────────┐
│ Financial Institution│
│       Mercury        │
└──────────┬───────────┘
           │ Transaction Export
           ▼
┌──────────────────────┐
│  Institution Adapter │
│       Mercury        │
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│ Normalized Transaction│
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│ Reconciliation Engine│
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│ Payment Verification │
└──────────┬───────────┘
           ▼
┌──────────────────────┐
│Commerce Authorization│
└──────────┬───────────┘
           │ Webhook/API
           ▼
┌──────────────────────┐
│ Commerce Application │
│   Order Released     │
└──────────────────────┘

Test Procedure

  1. Create a receivable with payment reference TLX-POC-MERCURY-001 and amount 10.17 USD.
  2. Confirm the connected application order is LOCKED.
  3. Receive a settled credit on the designated Mercury account (live evidence later).
  4. Export institution-originated CSV. Do not collect bank login credentials.
  5. Upload the CSV in Financial Data → Import Transactions.
  6. Confirm the Mercury adapter detects the format by header names.
  7. Confirm exact reference + amount + currency auto-authorizes only when those rules pass.
  8. Confirm the signed commerce.authorization.created webhook releases the order.

Results

Proof IDTLX-POC-MERCURY-001
InstitutionMercury
InputInstitution-originated transaction export
PaymentMatch recorded — awaiting Review sign for public proof
VerificationTideLinx reconciliation engine
Authorizationauth_23a70b15caae3911
External Applicationevt_f035303f-0c60-4701-96f7-939e35984112
Duplicate ProtectionImplemented — not yet Review-signed
Exception TestingAutomated suite present — Review pending
ResultPENDING Review
Source file SHA-2563dd4240e4dcd83701ad0c0072a3ee7186ab74d70fe59a01838640ce5ec1ef277
Correlation IDpoc_corr_20260831_B061F8
Receivable IDa96c7d15-2f3b-4d40-9588-5399019c92af
Connected order IDcb1ecfef-e3f8-44f5-b3eb-b430bb6b57c1

Result cards are filled from poc_evidence_records. Blank fields mean evidence has not been written yet. A CSV walk may fill SHA-256, authorization ID, and webhook event without flipping Result to PASS. Only a Review-sign API call sets review_signed_at.

Failure Tests

Evidence

Scaffolding lives in docs/proof-of-concept/mercury-001/. Screenshots, the source-file SHA-256, and the redacted evidence manifest are filled from the frozen record when those fields exist. Unredacted bank statements, account numbers, webhook secrets, and private keys are not published.

Review can inspect the frozen row without signing: GET /api/public/proof-of-concept/TLX-POC-MERCURY-001.

What This Proves

When the evidence package is complete, the test is intended to demonstrate:

What This Does NOT Prove

This architecture is designed so a later test can be described as validated using Mercury-originated transaction data. It does not represent or imply a partnership, endorsement, certification, integration agreement, or commercial relationship between TideLinx and Mercury.

Technical Architecture

Adapters convert institution-specific files into a canonical transaction. Reconciliation has no Mercury-specific logic. Auto-authorization requires an exact payment reference, exact amount, exact currency, a non-duplicate row, an acceptable source status, and a receivable that is still awaiting payment.

AdapterStatus
MercurySUPPORTED
Republic Bank TTNOT_VALIDATED
First Citizens TTNOT_VALIDATED
Scotiabank TTNOT_VALIDATED
RBC / RBTTNOT_VALIDATED
WamNOT_VALIDATED

SUPPORTED means the adapter is implemented and covered by technical tests. VALIDATED is reserved for genuine institution-originated evidence. Planned Trinidad & Tobago banks and Wam are listed as NOT_VALIDATED only.

Security & Privacy

Version History

2026-08-24 — Ingestion layer and public page published with result PENDING Review.

2026-08-24 — Frozen poc_evidence_records row; public status read from the database.