Published October 3, 2026 · ScriptMasterLabs trend-hunt canonical · Receipts dated Oct 1–3, 2026

T54 launched an agentic wallet on XRPL — but a spending limit is not a gate

On October 3, 2026, at XRP Seoul 2026, T54 launched a native agentic wallet on the XRP Ledger: AI agents execute payments within user-defined limits, receive pre-approval for transactions, and pay in XRP or RLUSD. It shipped alongside a trust framework — KYA (Know Your Agent) identity verification, user-defined spending limits, on-chain dispute and chargeback mechanisms — with Ripple, Mastercard, and AWS cited as partners. This is the most complete authorization stack any agent-payment rail has shipped to date. And it still doesn't judge a single payment: a limit is a fence, not judgment. The per-payment scored gate is the layer nobody supplies.

What happened today (dated receipts)

The authorization stack, mapped: what T54 ships vs what it scores

T54's stack is the closest thing the industry has to the full decision-gated pattern — so it's worth being precise about which half it supplies.

The design thesis, in one line: the wallet is the seatbelt; the gate is the driver. A seatbelt caps the damage of a crash it can't prevent. T54 built the best seatbelt in agent payments — limits, KYA, Verifiable Intent, dispute rails. But at 675,000 agent transactions a day heading for 100 million, every one of those transactions still fires on zero per-payment judgment. The fence without the driver is how you get a hundred wrong five-cent payments — each one perfectly inside the limit, each one perfectly logged, each one a payment that shouldn't have existed.

Live gate receipts (minted today, not hypotheticals)

Scored against the live endpoint POST https://scriptmasterlabs.com/api/harness/decide — local-heuristic-v1, gate bands 0.80/0.50 live on the endpoint, October 3, 2026 ~20:20 EDT. Exact shape: {"state":{}, "questions":[{"id","type":"score","scale":[0,1],"question"}]}.

The honest finding (ninth run in a row): the uncalibrated local heuristic scores the routine listed-price payment and the flagged full-limit spend identically — it cannot discriminate the wallet's two canonical cases. Fail-closed is the protection: nothing inside the fence auto-fires on this gate either. That is the point of the table above, and it's the honest limit of a heuristic — the calibrated decider (the per-option probability JEV-27B supplies; the plugged-in TypeSafe Jev the harness's own meta note calls for) is the upgrade. calibrated=false, typesafe_wired=false — labeled, not hidden.

Do it yourself: wire the judgment layer onto the fence (5 steps)

1. Keep the fence. Deploy the wallet the way T54 does: user-defined daily limit, pre-approval categories, KYA-verified agent identity, Verifiable Intent records on every payment. The fence is the fail-closed ceiling — never remove it.
2. Score before the wallet, not instead of it. Route every payment instruction through a decision gate before it reaches the wallet's signing step: ≥0.80 confidence auto-acts inside the limit, 0.50–0.79 holds for human confirm, below 0.50 blocks, logs, escalates.
3. Score the instruction, not the account. Feed the gate the payment's own text — merchant, amount, listed price, price match, retry count, Trustline screen result. KYA tells you who; the gate scores whether.
4. Log like the FTC is watching. Attach the score, band, authority chain, and Verifiable Intent record to an append-only log per payment — the audit record the Sept 22 six-bank report and the Sept 30 FTC rogue-agent probe both demand.
5. Calibrate the decider. The heuristic gets you fail-closed; a calibrated decision model (JEV-27B's per-option probabilities; TypeSafe Jev via API) gets you discrimination — the routine payment clears, the flagged one doesn't. The wallet can't do that job. The gate can.

Exact wire shape for the gate used in today's receipts:

curl -s -X POST https://scriptmasterlabs.com/api/harness/decide \
  -H "Content-Type: application/json" \
  -d '{"state":{},"questions":[{"id":"pay-001","type":"score",
        "scale":[0,1],
        "question":"Should the agent pay 0.05 XRP to a listed data API at the listed price inside the $5/day limit?"}]}'
# → {"confidence":0.35,"gate":{"band":"escalate","action":"block + log"}}

SML products that implement the missing layer

Two of the seven ScriptMasterLabs products ship the judgment layer T54's wallet needs:

• Decision-gated payments — the canonical pattern: every machine action carries a confidence score, and the band decides — ≥0.80 auto, 0.50–0.79 human confirm, below 0.50 block, log, escalate. The live gate endpoint used for today's receipts (/api/harness/decide) runs this pattern now.
• Provider Trust — trust scoring for the endpoints themselves: does this merchant deserve your agent's payments? Authorization has two halves — should this payment fire (the gate) and does this merchant deserve it (trust). KYA answers identity; Provider Trust answers deservedness.

Sequel context: this piece is the follow-up to XRPL's 10M x402 milestone (Oct 1) — the count, then the control layer. And the companion builder piece is the x402 spending-guard two-layer model (Sept 30): guard answers "can we afford it," gate answers "should it happen at all."

Claim Receipts

Honest caveats

• Event details are from the TradingView/Coinpedia XRP Seoul 2026 live blog (keynote reporting), not from a T54 primary announcement — treat quotes as reported, not verbatim press text.
• Wallet pricing, availability date, merchant onboarding, and KYA technical details were not disclosed in the keynote coverage — not claimed here.
• On-chain dispute/chargeback mechanics were named but not described — not claimed.
• "T54 backed by Ripple and Franklin Templeton" reflects the $5M joint investment reported by The Currency Analytics; "backed by" elsewhere (Times Tabloid) is not independently verified beyond that.
• Verifiable Intent support rests on T54's July 24, 2026 X post as reported by U.Today/NBTC — press-reported, not hands-on tested.
• Gate receipts use local-heuristic-v1 (uncalibrated, TypeSafe not wired) — the discrimination upgrade is the JEV-27B/TypeSafe calibrated decider, cross-linked above.