Skip to main content

User Guides

For Merchants (Supply-side)​

Running your Accensa back-office locally takes under 15 minutes. It requires PostgreSQL, the Go Indexer, and the Next.js Dashboard.

1. Database Setup​

Accensa requires a standard PostgreSQL instance to store parsed ledger data.

docker run --name pg -e POSTGRES_PASSWORD=postgres -p 5432:5432 -d postgres

2. Start the Facilitator​

Run the x402-facilitator-stellar service to handle the standard x402 protocol flow and process payments from AI agents.

cd x402-facilitator-stellar
pnpm install
pnpm start

3. Start the Dashboard​

The Next.js dashboard connects to your local database to visualize your revenue and receipts.

cd apps/web
pnpm install
pnpm dev

Path A vs Path B​

  • Path A (Chain-Only): If you run Accensa with zero integration to your x402 server, you will see total revenue, payers, and timelines based purely on chain data.
  • Path B (Middleware Hook): By adding the Accensa SDK hook to your server, your indexer attributes every chain settlement to a specific HTTP route, unlocking route-level revenue analytics.

For Agent Operators (Demand-side)​

You do not need to run any infrastructure to verify an Accensa receipt provided by a merchant.

Verifying a Receipt​

When a merchant gives you a receipt, it includes the batch Merkle root, the specific leaf (your payment hash + metadata), and the Merkle proof.

You can mathematically verify this receipt off-chain by using the Accensa Node SDK. All three arguments are hex-encoded 32-byte hashes; the proof lists sibling hashes from leaf to root:

import { verifyReceipt } from '@accensa/sdk';

const isValid = verifyReceipt(receiptLeaf, proof, batchRoot);
if (!isValid) {
  throw new Error("Receipt does not match the anchored batch root.");
}

Alternatively, you can verify the receipt strictly on-chain by calling the verify_receipt view function on the ReceiptAnchor Soroban contract using any Stellar explorer or RPC.