🌱 Early-stage fintech · founder-funded
The infrastructure behind AI commerce

When agents do the shopping,
someone owns the wallet.

Paygent Labs builds the infrastructure that lets AI shopping agents find products, recommend the highest-earning card, and help shoppers earn rewards — wherever they shop.

Three platform layers make that work: the shopping agent, the payment rails behind it, and the rewards layer on top — each one strengthening the others.

Working technology
✓ UCP checkout over MCP, on the official SDK ✓ Multi-processor orchestration — Stripe · Square · PayPal ✓ Versioned wallet-agent contract, self-attested conformance ✓ Apple Wallet NFC passes ✓ Tap to Pay on iPhone
See everything that is built ↓
The thesis

Commerce is moving to agents — and the bank or loyalty program that does not run its own agent cedes the wallet relationship to the platform that does. We build the white-label buyer-side agent they keep as their own: it holds their wallet, optimizes their loyalty, and shops on their customer's behalf.

The Universal Commerce Protocol (Google, Shopify, 20+ partners across retail and payments) standardizes the merchant side. Platform agents such as Google AI Mode and Gemini already buy under it, and the card networks supply the agent credentials that authorize each purchase. Stripe and Square own processing. Loyalty vendors bolt points on after the fact. What a bank or loyalty program lacks is a buyer-side agent it controls, so the customer relationship stays with it. That is the gap.

Why now — three trends converging
Agents can buyAI agents are becoming capable of autonomous purchasing.
Merchants are standardizingUCP is making merchant interoperability a protocol, not an integration.
Rails are openingMerchants increasingly demand processor-agnostic payment infrastructure.
Market

Three markets, one platform.

New

Agentic commerce

An emerging category, standardized by the Universal Commerce Protocol — launched with Google, Shopify, Visa, Mastercard and Stripe behind it — with room for a white-label buyer-side agent that banks and loyalty programs control.

Growing

Payment orchestration

A growing category as platforms refuse single-processor lock-in (Spreedly, Primer, Gr4vy validate the buyer).

Mature

Loyalty & rewards

Points sit as unloved balance-sheet liability; programs are siloed, expiring, and universally disliked.

The platform

Three engines that compound.

One integrated platform with a flywheel at its core: the agent drives transactions, payments execute them, and rewards retain both sides — and each layer opens its own revenue line along the way.

PaygentAI commerce agent — finds what to buy & recommends the card
StellarBackrewards layer — issues & redeems on-chain value
Stellar network
branded points, on testnet today
Paydapterpayment orchestration — executes the transaction
Merchants' existing processors
Stripe · Square · PayPal
The demand layer

Paygent — the agentic commerce engine

A UCP-native buyer-side agent with a real wallet: it discovers products across connected catalogs, computes the highest-earning card from actual per-cart loyalty math, applies points at checkout — with all money and points math kept deterministic and out of the model's hands.

  • Built on UCP; public discovery pending
  • Pluggable wallet/loyalty provider: a bank's cards, a platform's balance, or our on-chain rewards
  • Four packagings of one core: embedded in a partner's app, white-label platform, an embeddable agent, or operated by us on our control plane
  • The wallet seam is a versioned, frozen contract, to be published with the agent SDK — a bank's own wallet agent will be able to integrate without ever seeing our source
See the product page →
The moat

StellarBack — on-chain rewards infra

Closed-loop branded points on Stellar, running on testnet today: customers earn and redeem with zero crypto friction. Live issuance and self-custody withdrawals wait on a custody legal opinion.

  • Pooled/muxed accounts, on testnet: micro-rewards at sub-cent cost, no per-user reserve
  • Designed to interoperate across programs later → coalition network effects
  • Verifiable issuance: the gateway mints only against a signed earn attestation it verifies itself, so forged and replayed earns are refused, and every mint and burn is on the ledger. Attribution of sale credit is on the roadmap
  • SaaS + issuance economics
See the product page →
When demand appears

Paydapter — payment orchestration

One API to route transactions across Stripe, Square, PayPal and more — while every merchant keeps their own processor account.

  • Bring-your-own-PSP onboarding, designed so merchants do not have to switch processors
  • Paydapter never custodies funds: payments settle in each merchant's own processor account
  • Platform fee per transaction, the pricing model orchestration vendors already use
See the product page →
Together, one commerce platform.
Paygent generates transactions. StellarBack creates retention through rewards. Paydapter monetizes transaction flow.
Each layer is designed to strengthen the others — a combined stack that takes real work to assemble.
What is already built

Years of hard engineering, technically de-risked on testnet.

The difficult primitives already exist.
We are now assembling them into the platform.

✓ built  ·  ◐ in progress

Agentic commerce
✓ Commerce engine built on the official UCP SDK: orchestration, product discovery, and checkout over MCP, with a loyalty model shaped on UCP’s loyalty extension
✓ Versioned, frozen 1.x wallet-agent contract, to be published with the agent SDK: ten MCP operations plus a sandbox tool, RFC 9421 Ed25519 signing both directions, durable idempotency, Know-Your-Agent checks on every spend-affecting call (signed caller, scoped mandate), with the user's cart approval checked before capture
✓ In-house clean-room implementation, built from the written spec alone and self-attested against the contract, with a runnable conformance harness and language-neutral wire vectors; both will be released publicly with the agent SDK
✓ Transactional loyalty escrow at checkout: points are reserved, then captured or released
✓ Highest-earning card recommendation from real per-card earning on the live cart — server-computed, never model-generated
✓ Card-event earn ingress settles on-chain. On the attesting route, the mint path rejects forged and replayed attestations. On-chain accounts are created automatically at migration or at a member's first earn
✓ Each leg confirmed on Stellar testnet: account creation, branded-points migration, earn minting, and redemption burns
◐ Control plane and admin console in build: tenant onboarding, provisioning, and fleet operations over the platform's versioned admin API, to be published — the same API an integrator will get
Payments
✓ Multi-PSP routing with native marketplace onboarding (Stripe Connect, Square & PayPal OAuth)
✓ Serverless gateway with attestation, auth, and sandbox/live separation
✓ Tap to Pay on iPhone acceptance through Stripe in the merchant app, with Apple’s entitlement granted; release pending
Rewards
✓ Pooled + muxed Stellar custody: custodial and self-custodial accounts on testnet
◐ Custodial → self-custody graduation, designed
✓ Apple Wallet NFC passes: Apple-issued NFC pass-type certificate, issuance pipeline, and NFC pass reading between iPhones in an internal P2P prototype
Proximity R&D
✓ Prior proximity R&D, now parked: Wi-Fi Aware transport on Android + iOS 26, UWB distance bounding, and a geofence + beacon engagement layer
Defensibility

Why this holds.

“Agents get judgment, money gets math.” The architecture principle behind everything we build.

🤖Standards-native

Built on UCP from day one, with a loyalty model shaped on its loyalty extension; public discovery pending. As the standard spreads, the ecosystem builds the integration surface; we do not pay for it.

⚖️Deterministic agent architecture

Deterministic escrow, idempotent checkout, verifiable spend mandates — the model never touches the money math. Built for the kind of oversight agent commerce is likely to face.

🧲A distribution wedge by design

"Keep your processor" is meant to take processor switching off the table in a sales conversation. Orchestration rides existing PSP relationships instead of fighting them.

🕸️Coalition network effects

Every merchant added makes the shared reward currency more valuable to every customer — classic two-sided compounding, on infrastructure we operate.

🏗️Architecture that is genuinely hard

Scale-economical on-chain custody (pooled/muxed) plus crypto-invisible UX with a self-custody off-ramp designed in, gated on a custody legal opinion — a combination we have not seen points vendors or wallets ship. And an integrity layer underneath: the gateway mints only against a signed earn attestation it verifies itself, forged and replayed earns are refused, and every mint and burn is on the ledger. Attribution of sale credit is on the roadmap.

Business model

Four ways the platform earns.

🤖

Agent platform

Embedded/white-label licensing plus per-checkout fees on agent-completed transactions.

💳

Orchestration fees

Platform fee per routed transaction on merchants' own PSP accounts.

🪙

Rewards SaaS + issuance

Program fees and issuance volume on the reward asset.

🌐

Network take rate

Coalition membership and cross-merchant redemption fees as the network compounds.

Sequencing

Design partner first. Moat in parallel. Consumer when earned.

Founder-funded today; a first design partner, grant, or investor funds the path to production — we do not burn capital waiting for the market.

Phase 1 · Now

Rewards demo on testnet, a first design partner, and the agent SDK in public

The agentic engine and rewards loop run on Stellar testnet. Recorded demo of the rewards loop on testnet: watch it. Next, a first design partner to take it to production, and the Paygent agent SDK released publicly with the wallet-agent contract and conformance harness.

KPI: design partner signed · agent SDK public
Phase 2 · Parallel

Platform + StellarBack to mainnet

Generalize the wallet/loyalty provider into the white-label platform and client SDKs; take the control plane from tenant registry to operated provisioning and billing; webhook-driven earn/redeem loop. This phase, including self-custody withdrawals, is gated on a custody legal opinion. Paydapter orchestration and its merchant dashboard follow when merchant demand appears.

KPI: tenants · rewards issued · partner integrations
Phase 3 · Earned

The consumer network

ShakeToPay bundle launched through a captive-network pilot (QSR chain / campus), plus P2P "AirDrop for money" white-labeled for banks — distribution solved before we spend on it.

KPI: repeat usage · coalition spend
Who is building this

Payments-native, from the card rails up.

Founded by Ming-Li Liu — 25+ years engineering payment systems, from smart-card firmware to cloud gateways: the full stack, in one set of hands.

Visa · ViVOtech · Co-founder & CTO, Zenius Solutions · Director of Software Engineering, SimplyTapp · OV Loop · Poynt (GoDaddy) · Founder, MysDeFi

Full bio: mll11.com · LinkedIn

Where we are

Founder-funded and building. Happy to compare notes.

We are not running a formal raise — we are heads-down taking the rewards platform to its first design partner and the agent SDK to a public release. But if you invest in early fintech infrastructure and this thesis resonates, we would genuinely like to meet before we are "in market." Early conversations shape the company.

Start a conversation Watch the demo