🤖 Agentic commerce · built on the open UCP standard

Your agent shops.
It recommends the card that earns the most, on every cart.

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 Universal Commerce Protocol — the open standard backed by the payments industry.

Built on UCP · public discovery pending Any wallet · bank, platform, or program Deterministic money math · never left to the model Scoped mandates · checked before an external wallet moves value
Product

An agent that does not just chat about shopping. It closes.

Most shopping assistants stop at recommendations. Paygent holds the wallet — so discovery, loyalty, and checkout happen in one conversation.

💳

Best-card intelligence

Computes real per-card earning on the actual cart — multipliers, bonuses, thresholds — and recommends the card that wins. Server-computed, never hallucinated.

🪙

Points at checkout

Points are reserved at checkout, then captured or released. Escrowed, atomic, auditable.

🔐

Know Your Agent

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.

🧩

Bring your own wallet

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.

🧾

Earning, not only spending

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.

🎯

The price you were shown

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.

How it works

From intent to receipt in four steps.

1

Say what you want

Natural language — a product, a budget, or how you want to use your points.

2

The agent works the market

Finds it across connected catalogs and compares.

3

The wallet does the math

Highest-earning card on this cart; points applied at checkout. All computed deterministically.

4

Checkout, on your terms

The order completes on the cart you approved, at the price you saw, with your points applied.

The trust principle

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.

How a money figure reaches the user without passing through the model Two lanes. The model routes the intent and narrates the outcome. Deterministic services compute every total, discount, and point figure and hand it to the reply as a sealed block. Nothing numeric crosses from the service lane into the model lane. JUDGMENT · THE MODEL Route the intent Pick the operation Narrate the outcome MATH · SERVICE CODE Checkout totals Loyalty earning · escrow Pricing discounts Redemption points applied User turn what to do no amount ever crosses this line upward THE REPLY narration sealed figures composed server-side, rendered as-is
  • The model routes the intent, picks the operation, and narrates the outcome — words only.
  • Service code computes every total, discount, and point figure.
  • Those figures reach the reply as a sealed block the client renders as-is.
  • No amount crosses back into the model's lane, so no amount can be rewritten.
The number takes the bottom path. That is the whole architecture.
Rewards demo

Your loyalty program, on our rails.

Our rewards proof of concept runs on Stellar testnet, with points issued on chain as CRWD, a branded test asset. Seven short recordings show it working, from your program's rules to connecting it.

Watch the demo →

  1. This is your program
  2. A card charge becomes points
  3. Sign up with an existing partner account
  4. Points stay inside the program
  5. Every charge is verified before it earns points
  6. Redeemed points are removed from circulation forever
  7. Connecting your program
For banks & platforms

One engine. Your brand. Your wallet.

Paygent is built to be embedded — the same engine ships four ways.

🏦

Embedded in your app

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.

🏷️

White-label platform

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.

🤝

Embeddable agent

Already running an assistant? Paygent plugs in as the commerce capability over standard surfaces — agent card, MCP, UCP — and your host keeps the conversation.

☁️

Paygent Cloud, operated

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.

Early access

Commerce is getting an agent.
Make sure it earns for you.

We are looking for a first design partner among banks, platforms and loyalty programs ahead of general availability.

Request early access Request a walkthrough Watch the demo