Discovered too late
Interchange downgrades and pricing errors surface after settlement — when nothing can be changed.
Autonomous Payment Intelligence
An operating system for payments — not another dashboard.
Merchants lose money to processing they can't see or control. API Labs is the intelligence layer that makes payments predictive and closed-loop — one shared memory of what's true, applied to every decision.
● 9 modules architected — 2 substrates, 7 decision modules
● 4 more scoped or reserved
The problem
Timing
Fragmentation
Memory
Money leaks where no one is looking.
Payment intelligence is normally reconstructed after settlement, from processor files and statements. By then the context that could have changed the outcome is already gone.
Fragmented knowledge
The same merchant, fee, or agreement means something different in every processor's own records.
No memory, no learning
Each transaction, contract, and statement is judged in isolation. Nothing reconciles or improves over time.
The thesis
Payment intelligence today is reactive. We're building the layer that makes it predictive — and closed-loop.
Two ideas hold the whole platform together: a shared memory every module can trust, and a single loop every module runs.
The substrate
A shared memory
The Knowledge Graph and the Merchant Twin give every module the same view of what's true, who this merchant is, and how confident to be.
The modules
Applied to one decision
Each module applies that shared memory to a specific job — edge, qualification, pricing, contracts, statements, routing, readiness — instead of starting from scratch every time.
Why now
The rules just changed. Most software hasn't.
For years, commercial-card optimization was a post-hoc cleanup — send the data, sort out qualification later. Visa's Commercial Enhanced Data Program (CEDP), enforced October 2025, ended that: enhanced data is now validated at submission, placeholder data no longer earns the rate, and merchants carry a “verified” status Visa re-scores every month.
Then
Fix it after the batch
Enrich or re-submit Level II/III data after settlement to recover a better interchange rate. For years, simply attempting to send enhanced data was often enough to qualify.
Now
Get it right before settlement
Under CEDP, validated data at submission is the rate. Placeholder or incomplete data is caught, and the post-hoc correction window optimizers relied on is closing.
So
Timing is the moat
Being at the transaction level, before the batch settles, is no longer a nice-to-have — it's increasingly the only place the value can still be captured. The rule change moved the industry to where API Labs was already built.
Qualification Intelligence™ determines what's attainable and the minimum action to reach it — before submission. Edge Intelligence™ confirms the data survives the integration path. The Merchant Financial Twin™ tracks verified status over time. Statement and Pricing Intelligence™ catch what slips through.
Three truths, one merchant
What governs. What it should cost. What actually happened.
Most tools treat the statement as the truth. We hold three independent, evidence-backed views of the same merchant — and the differences between them are where the money is.
Governing — Contract Intelligence™ reconstructs which agreements actually apply, as of today.
Expected — Pricing Intelligence™ computes what the merchant should pay under those terms.
Observed — Statement Intelligence™ reconstructs what the merchant actually paid.
How every module works
One loop. Every module. No exceptions.
It isn't a set of products bolted together. It's one architectural pattern — the same five steps — applied to every decision. That consistency is what makes this a platform, not a portfolio.
Observe — capture the real context before settlement.
Predict — apply the shared memory to the decision at hand.
Act — advise, or take a permitted action, within its limits.
Reconcile — compare what was intended, transmitted, and applied.
Learn — feed the difference back so the next answer is better.
The platform
Two substrate layers. Seven decision modules. One loop.
Everything shares one foundation. The substrate holds canonical knowledge and per-merchant memory; the modules make decisions on top of it. Nine are architected today; four more are scoped or reserved.
Substrate · Architected
Payment Intelligence Knowledge Graph™
The evidence-backed, time-aware fabric that teaches every module what payment objects mean, how they connect, and how confident to be.
Substrate · Architected
Merchant Financial Twin™
The authoritative, continuously evolving model of one merchant's payment ecosystem — its memory, state, and history.
Edge Intelligence™
Observes transaction context at the point of sale, confirms the data survives the integration path, and feeds guidance back before settlement.
ArchitectedQualification Intelligence™
Determines the best interchange qualification actually attainable for a merchant — and the minimum action to reach it — before submission.
ArchitectedPricing Intelligence™
Classifies what a merchant truly pays — and who bears it — in one processor-independent language, before any comparison is made.
ArchitectedContract Intelligence™
Reconstructs which agreements, schedules, and amendments actually govern today — the agreement is not the PDF someone uploaded.
ArchitectedStatement Intelligence™
Reconstructs what actually happened on every statement — true cost versus markup, with the evidence behind each number.
ArchitectedRouting Intelligence™
Selects the eligible, lowest-cost payment rail for each transaction before it's sent — debit first — and verifies what actually settled.
ArchitectedReadiness Intelligence™
Asks the merchant what the system can't observe, treats the answers as evidence, and turns recommendations into merchant-approvable actions.
ArchitectedExecution Intelligence™
Turns an approved recommendation into a tracked change request with the right party — and verifies it on the wire.
ReservedPortfolio Intelligence™
Lets a bank, ISO, or gateway see across many merchants without mixing any merchant's memory with another's.
ReservedNegotiation Intelligence™
Recommends pricing and contract improvements so merchants negotiate from knowledge.
ScopedRisk Intelligence™
Monitors transaction and operational patterns to generate predictions, alerts, and controls.
Scoped
Credibility, not vaporware
Nine modules, architected for real.
Not just diagrams. Each architected module has a full invention architecture and a patent-readiness pass with counsel-ready claim boundaries; the engineering build — real schemas, phased acceptance criteria — follows the same discipline.
Knowledge Graph™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Merchant Twin™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Edge Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Qualification Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Pricing Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Contract Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Statement Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Routing Intelligence™
- ✓ Architecture
- ✓ Engineering build
- ✓ Patent review
Readiness Intelligence™
- ✓ Architecture
- ○ Engineering build — next
- ✓ Patent review
Engineering approach
Designed to be built — not just diagrammed.
Every module is written twice: once for understanding, once for building. The second one is what an engineering team — human or AI-assisted — works against.
01 · Define
Architecture documents
Describe what each system does and why — the version product and patent review start from.
02 · Specify
Engineering build documents
Turn each architecture into concrete schemas, API contracts, and phase-by-phase acceptance criteria.
03 · Sequence
Phased by dependency
Identity before context, context before simulation — so each phase is provably correct before the next depends on it.
Compliance & trust
Designed in from day one.
For a processor partner or enterprise merchant doing diligence, this is the part that matters — and it's an architecture decision, not an audit fix.
PCI DSS
Scope is contained the moment real transaction context is handled — tokenization and segmentation built in, not bolted on.
SOC 2
Readiness work runs in parallel from the start, so the evidence period can begin as early as the timeline allows.
Tenant isolation
Built into the substrate from its first schema — every merchant's data is provably separated, not just logically.
How people work with it
Autonomous where it's earned. Accountable everywhere.
The loop can recommend, and within limits it can act — but every limit is set by a person, and every action can be traced back to the authority that allowed it. That's not a policy layered on top; it's part of the substrate.
01 · Identity
Known, at a known level
Merchants, partners, staff, and AI agents are all principals with a verified level of assurance. Nothing acts under an assumed identity.
02 · Authority
Scoped, timed, evidenced
What anyone may do is defined by role, scope, capability, data class, and time — and every grant is itself a piece of evidence the system keeps.
03 · The merchant
In the loop, not downstream
When the system can't observe something, it asks. Answers become evidence; recommendations become actions the merchant approves, declines, or defers.
04 · AI agents
Less than authorized, never more
An agent operates inside a class of actions a named human defined. Novel situations escalate as recommendations; outcomes are reconciled before any envelope widens.
What's next
A platform architected the way it will need to work once it matters.
Architected, phased, patent-aware, and honest about its own risks — from the first module. If you're a payments partner, investor, or prospective merchant, we'd like to show you the rest.