# Ledger by Novadyne – Reverse Transaction

> Ledger by Novadyne – Reverse Transaction is a paid API for AI agents from ledger-api.novadyne.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-12).

Reverses a previously recorded double-entry ledger transaction by its ID, creating a compensating entry with an optional reason.

## Facts

- Endpoint: POST https://ledger-api.novadyne.ai/ledger/transactions/%7Btx_id%7D/reverse
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ledger-by-novadyne-reverse-transaction-202f1fba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZVlXo5S7_SH1SLu-BmpHy

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ledger-by-novadyne-reverse-transaction-202f1fba -d '<json body>'
```

Example prompt: Reverse transaction tx_a9f3c2 in the Novadyne Ledger and record the reason as 'duplicate entry posted in error'.

## When to prefer this

Use this endpoint when you need to programmatically reverse a specific double-entry ledger transaction managed by the Novadyne Ledger API, especially in workflows that use x402 micropayments and Ed25519 capability tokens for authorization. Prefer this over manual correction entries when you want an auditable, API-driven reversal tied to a specific tx_id.

## Known failure modes

- Transaction ID not found — 404 or similar error if the tx_id does not exist
- Transaction already reversed — error if a reversal has already been applied to this transaction
- Insufficient authorization — missing or invalid Ed25519 capability token results in 401/403
- Payment failure — x402 micropayment not satisfied, resulting in 402 Payment Required
- Malformed request — missing or invalid reason string format

## How this service works

Double-entry ledger API with x402 micropayments and Ed25519 capability tokens.

## Output

A confirmation that the transaction has been reversed, typically including the newly created compensating entry details or an acknowledgment of the reversal. The response schema is currently sparse, so the agent should expect a success/failure signal and possibly a new transaction record referencing the original tx_id.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "reason": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ledger-by-novadyne-reverse-transaction-202f1fba/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ledger-api.novadyne.ai](https://www.zero.xyz/host/ledger-api.novadyne.ai/llms.txt)