Recorded demo · Stellar testnet Your loyalty program, configured, not rebuilt.

Your brand, your members — our rails.

Short recordings from our rewards proof of concept, from your program's rules to connecting it.

Rewards built for agentic commerce

Earned at payment, redeemed by an agent, verifiable on a public ledger

A short overview of the proof of concept.

  1. This is your programIt starts with your rules: earning, redemption, tiers and perks, set up as configuration in your brand.
  2. Every program update is checked before it goes liveRolling back is one step, not a rebuild.
  3. A card charge becomes pointsThe points arrive in seconds, minted as CRWD on testnet.
  4. Sign up with an existing partner accountMembers sign in with the account they already have with the partner, and a wallet is created for them.
  5. Points stay inside the programOnly accounts the program authorizes can hold them.
  6. Every charge is verified before it earns pointsAltered, forged or replayed charges are refused.
  7. An AI agent handles payment and loyalty in one checkoutA wallet agent built to our contract plugs in and pays.
  8. Points pay for part of an orderPoints are spent only when the order goes through.
  9. Redeemed points are removed from circulation foreverPoints removed on chain always match the points spent.
  10. Connecting your programIt would take one secure webhook, carrying everything we need from you per transaction.

This is your program

Your rules and brand, configured

Your program's earning and redemption logic, running unmodified on our platform and in your brand. Earning rates, category bonuses, tiers and redemption values become configuration*, so changing a rule is a configuration change.

* Live earns currently apply the base rate only.

Each earn mints CRWD, a branded test asset on Stellar testnet.

What to watch for

  • Your brand on the program, with the CRWD badge.
  • Earning, redemption (100 points = $1, 500-point minimum) and tiers shown as configuration.
  • The redemption catalog ending on an optional crypto tier, off by default.

Every program update is checked before it goes live

Rolling back is one step, not a rebuild

Here, an example program's rules and brand live in one document. Each update is checked before anything is deployed, then goes live as a new version only after it passes its own check. Rolling back is one step, not a rebuild.

Midpoint Rewards is an example program, not a customer. In this version the brand is stored in the program's document; no member screen shows it.

In the proof of concept, we apply updates and roll them back for you.

What to watch for

  • The program's rules and brand in one document, with every update shown as a diff.
  • The points label changes; the asset code underneath, MIDP, does not.
  • The check's verdict, valid, before anything is deployed.
  • A new revision that takes traffic only after it passes its check.
  • One command back to the previous revision, not a rebuild.

A card charge becomes points

An auditable record of every point earned

A card charge arrives from the card feed and becomes points in seconds, each one minted as CRWD on Stellar testnet. Members would keep a familiar points experience.

What to watch for

  • A card event arrives from the card feed.
  • The new row shows the member, the charge, the points credited and the new balance.
  • The CRWD mint is recorded on the Stellar testnet ledger.

Sign up with an existing partner account

No new password, and earlier points carry over

Members sign in with the account they already have with the partner, and a wallet is created for them. In the recording, a card charge creates the member's account and earns points before they sign up, and those points come with them when they do.

The demo partner appears as Customer throughout the recording.

Sample member on testnet. The card earn took about 30 seconds in this recording; that wait is shown sped up ×8.

What to watch for

  • A card charge creates the member's account, with no enrollment form.
  • The member signs in with their existing partner account, with no new password.
  • A consent screen shows exactly what is shared.
  • The points earned before signup are already there.

Points stay inside the program

Only accounts the program authorizes can hold them

Points move between accounts inside your program, but they do not leave it as points. The ledger's authorization rules decide which accounts can hold them, so a transfer to an account the program has not authorized is refused.

Sample transactions on the Stellar testnet.

What to watch for

  • Points sent to an account inside the program go through.
  • The same points sent to an account the program has not authorized are refused.
  • The same move in test USDC, an open token anyone can hold, goes through to that outside account.

Every charge is verified before it earns points

Altered, forged or replayed charges are refused

Every earn arrives signed by the card feed, and each one is checked before any points are credited. In the recording, one genuine charge earns points once. The other four are refused by verification checks.

Sample transactions on the Stellar testnet.

What to watch for

  • One genuine signed card charge earns points, with a single CRWD mint.
  • The same charge with its amount altered after signing is refused.
  • A charge whose signature does not match is refused, and so is one signed with a key nobody registered.
  • The genuine charge sent a second time is refused as a replay.
  • After all five requests, the balance shows only the genuine charge's points.

An AI agent handles payment and loyalty in one checkout

A wallet agent built to our contract plugs in and pays

Today your members redeem points on your loyalty vendor's website. Here, an AI agent shops for the member instead, in a checkout built on UCP's wire models. UCP, or Universal Commerce Protocol, is an open standard for agent checkout, and merchant-side UCP integration is on the roadmap. In the recording, it checks their balance, finds a skillet, redeems 500 points on the order and completes it, all in one conversation.

The points live in a separate wallet agent with its own ledger, not on chain: one we built to our wallet contract, and self-attested against it. The order total stays at $149.00: the points do not discount it, and no settlement with the merchant is shown.

What to watch for

  • The member asks in plain words to redeem 500 points, and the wallet agent sets them aside for the order.
  • Each line on the right is one call the platform made to the wallet agent.
  • Completing the order is three calls: approve it, spend the 500 points, and credit what the purchase earned.
  • The 500 points come off when the order completes, and the purchase earns 149 points back, one per dollar.
  • A staged request: this wallet's contract requires every request to be signed, and a request signed for 500 points but sent as 50,000 is refused, with nothing reaching its ledger.

Points pay for part of an order

Points are spent only when the order goes through

Here, 500 points go toward a $149 skillet. At the program's rate they are worth $5, and a card would pay the remaining $144. The points are set aside in the program's ledger until the order completes, then redeemed on chain. The member approves the order, not the split: it is the same split that UCP's split-payments extension standardizes.

Sample order on Stellar testnet. Nothing is charged.

Unlike the agent checkout, this redemption settles on chain.

What to watch for

  • The order's totals: $149.00, with 500 points applied ($5.00).
  • The remainder a card would cover, $144.00, and "no charge — demo" on the total.
  • The order completed, with the 500 points redeemed and settled on chain.

Redeemed points are removed from circulation forever

Points removed on chain always match the points spent

When a member redeems points, the matching CRWD goes back to the program's issuer and is removed on chain, not moved to another member. In the recording, a member redeems 500 points, and exactly 500 of their 600 CRWD is removed. Sending the same redemption again removes nothing more.

Sample member on the Stellar testnet.

What to watch for

  • The member's on-chain balance at 600 CRWD before redeeming.
  • A request to redeem 500 points through the program's AI assistant.
  • One transaction returning 500 CRWD to the issuer, where it is removed from circulation.
  • The balance at 100 CRWD, lower by exactly the points spent.
  • The same redemption sent again, with the balance still at 100.

Connecting your program

Everything we need per transaction

It would take one secure webhook from your transaction feed. You keep the program, the brand and the member relationship; we run the technology underneath.

In the recording, the transaction comes from a test run.

What to watch for

  • One sample transaction, the input behind every earn.
  • Seven fields: an event ID, a member reference, the amount and currency, the merchant, its category and the time.

FAQ

Why did the category multiplier (dining, 3×) not apply?

In this proof of concept, earns use the base rate. Category and tier multipliers are configured but not yet applied to live earns.

Why does the balance start at 2,000?

Demo members start from the program's default opening balance. Think of it as a signup bonus that you can configure.

Is this production?

No. It is a proof of concept on Stellar testnet, and CRWD is a branded test asset with no monetary value.

About these recordings. They show a proof of concept, not a production deployment. Every on-chain step runs on Stellar testnet; in the agent checkout, points stay in a separate wallet agent's own ledger. Program names, rules and values shown are illustrative.
Live walkthrough

Want the full walkthrough?

We will take you through the entire proof of concept live.

Request a walkthrough