Paygent is a commerce agent with a real wallet: it finds the product, does the loyalty math on this exact cart, applies your points, and checks out with your approval.
Built on the wire models of the Universal Commerce Protocol, an open industry standard. Merchant-side UCP integration is on the roadmap.
Most shopping assistants stop at recommendations. Paygent holds the wallet — so discovery, loyalty, and checkout happen in one conversation.
Today it ranks your cards by the points each earns on the actual cart — multipliers, bonuses, thresholds. Server-computed, never hallucinated.
Points are reserved at checkout, then captured or released. Escrowed, atomic, auditable.
Before an external wallet agent moves value, it checks who is calling (a signed request) and whether the call is within a scoped, capped, expiring mandate. Before capture, it also checks that you approved these items at this price. Verifiable proof, not a chat log.
The wallet and loyalty program are pluggable — a bank's cards, a platform's balance, a merchant's program. Paygent is the agent; the wallet stays yours.
Card charges made anywhere can be fed in as earn events — points accrue to the member, settled on Stellar testnet, with a member provisioned on first sight. The same ledger the agent redeems against.
Checkout binds to the offer you actually saw, at the price you saw, instead of searching the catalog again. "The cheapest one" resolves by arithmetic over what was on screen — never by keyword luck.
Natural language — a product, a budget, or how you want to use your points.
Finds it across connected catalogs and compares.
Your cards ranked by the points each earns on this cart; points applied at checkout. All computed deterministically.
The order completes on the cart you approved, at the price you saw, with your points applied.
Agents get judgment. Money gets math.
Every dollar and every point in Paygent is computed by deterministic, audited services —
the AI decides what to do, never how much things cost.
Money-facing text is composed in service code and spliced into the reply as sealed blocks, so the model never sees the number. Behind it: escrowed point reservations, idempotent checkout, and crash-safe redemption.
Our rewards proof of concept runs on Stellar testnet, with points issued on chain as CRWD, a branded test asset. Short recordings show it working, from your program's rules to connecting it.
Paygent is built to be embedded — the same engine ships four ways.
Surface the agent inside your banking or commerce app under your brand, bound to your cards and your loyalty program. Your customers, your relationship — now with an agent that makes your rewards the default.
Your own isolated instance — one program, one tenant, never a shared engine — running your catalog, your branding, and your wallet provider behind the same interface.
Already running an assistant? Paygent plugs in as the commerce capability over standard surfaces — agent card, MCP checkout, and a UCP-modelled discovery document — and your host keeps the conversation.
Or let us run it. A control plane, in progress today, will handle onboarding, provisioning, and the fleet, so that what you buy will be an operated service with settlement, compliance, issuer secrets and rotation, and reconciliation — not a dashboard.
We are looking for a first design partner among banks, platforms and loyalty programs ahead of general availability.