      How the ledger works
    

Report. Verify. Issue.

Three steps, once a day, for every node. The entity reports what happened; the ledger checks each event against the real payment; only what survives the check is ever recorded. Nothing is accepted on self-report alone.

STEP 01

Report

Once a day, a registered entity's sender signs and submits its proven events from the last 24 hours — verified sales, refunds, chargebacks and citations — each carrying the evidence the ledger needs to check it.

The payload is signed with the entity's private signing secret. The ledger never trusts anything from a browser, and never trusts a number an entity simply states.

STEP 02

Verify

The ledger checks each event independently against the real payment record. A sale must match a real settled payment. A citation must survive a unique follow-back. No verification, no token.

A machine cannot talk its way into a token — the check is mechanical, and it either passes or it doesn't.

STEP 03

Issue

What passes becomes a permanent, public token on the entity's record, named for its own domain. What fails is rejected and logged. The good and the bad sit side by side, in full view.

The record is append-only and signed — a verifiable history, not a balance anyone can rewrite.

        The sender
      

One config, signed daily

When you register, you get a URSY ID and a signing secret. Drop them into your sender config and the daily submission runs itself — pointing at the central ledger.

The secret is shown once, never shared with another entity, and signs every payload you send.

sender.config · php

define('CENTRAL_LEDGER_ENDPOINT',
  'https://ursy.org/wp-json/ursy/v1/ledger/submit');
define('URSY_NODE_ID', 'URSY-001');
define('URSY_SIGNING_SECRET',
  'sk_ursy_••••••••••••••••••••••••');

        Five outcomes
      

What a verified day produces

Every event that survives the check becomes one of five tokens, each named for the entity's own domain.

teas.co.uk - sale appreciation

An AI-driven sale, matched to a settled payment.

teas.co.uk - citation appreciation

A citation that survived a unique follow-back.

teas.co.uk - refunded sale

A verified sale later refunded — shown openly.

teas.co.uk - sale chargeback

A sale later charged back — not netted away.

teas.co.uk - tucker · the credibility token

Sales are the first live Tucker rail. A Tucker is earned only when a verified AI-attributed sale survives 120 days with no refund or chargeback. Other settled value rails are future approved rails and do not mint Tucker yet. Read about Tuckers →