Mandate Cancellation Receipt Format

• Python: algovoi-cancellation-receipt (live on PyPI, v0.1.1)

​

Lifecycle position

admission       settlement       cancellation     refund (if owed)
compliance  --> settlement   --> cancellation --> refund
receipt         attestation      receipt          receipt

​

Why a four-state enumeration

• Payer revocation under PSD2 (Directive 2015/2366) Article 64 + UK Consumer Rights Act 2015 — MAY trigger refund obligations on debits already settled prior to the effective date.
• Payee termination under PSD2 Article 72 + contractual terms — does NOT trigger consumer-revocation refund-window obligations on already-settled debits.
• Operator/compliance-forced termination (sanctions, KYC, AML, court order) — anchors POCA s.330 / AML 5+6 evidence chain back to the originating compliance event.
• Time-based expiry — mandate’s own terms terminated it. Standard record-keeping only.

​

Receipt shape

{
  "canon_version": "jcs-rfc8785-v1",
  "cancellation_provider_did": "did:web:api.algovoi.co.uk",
  "cancellation_reason": "USER_REQUESTED",
  "cancellation_timestamp_ms": 1716494400000,
  "effective_from_ms": 1716537600000,
  "jurisdiction_flags": ["UK", "EU"],
  "mandate_ref": "sha256:0dd5d0b76c9b9281fdeb2509ad38ab132b16a17385ca01d976ff9e6e12563a0f"
}

​

The closed enumeration: cancellation_reason

​

Two timestamps

• cancellation_timestamp_ms — when the cancellation event was observed and recorded by the issuing provider.
• effective_from_ms — when the cancellation takes legal effect.

​

Composition

compliance receipt (ALLOW for mandate setup)
    |
    v   (settled_payment_ref or operator-layer link)
settlement attestation (recurring execution N)
    |
    v   (chain via prev_hash)
cancellation receipt (USER_REQUESTED, effective T+1 day)
    |
    v   (original_payment_ref references settlement)
refund receipt (FULL, if Article 64 refund owed)

​

Conformance vectors

1. Closed four-element cancellation_reason enumeration — four byte-distinct content_hash values.
2. jurisdiction_flags array order (RFC 8785 §3.2.3).
3. canon_version in-band pin.
4. effective_from_ms >= cancellation_timestamp_ms invariant.
5. mandate_ref content-addressing (sha256: prefix retained in canonical bytes).
6. Audit chain row linkage via prev_hash.

​

Quick start

​

TypeScript

import { buildCancellationReceipt } from "@algovoi/cancellation-receipt";
import { sha256Jcs } from "@algovoi/substrate";

const r = buildCancellationReceipt({
  cancellation_reason: "USER_REQUESTED",
  cancellation_timestamp_ms: 1716494400000,
  effective_from_ms: 1716537600000,
  cancellation_provider_did: "did:web:api.algovoi.co.uk",
  mandate_ref:
    "sha256:0dd5d0b76c9b9281fdeb2509ad38ab132b16a17385ca01d976ff9e6e12563a0f",
  jurisdiction_flags: ["UK", "EU"],
});
console.log(sha256Jcs(r));
// e50f8d4f9fcd8b0cf142bd65528a90d8814dd71127d4529ca77137b4b41ad407

​

What this is NOT

• Not a refund receipt. Cancellation records the termination of a mandate; refund records the reversal of a settled payment. When a USER_REQUESTED cancellation triggers a refund, both receipts are emitted and chained via the audit-chain.
• Not a dispute receipt. Disputes are state machines over multiple parties; cancellation is a single state transition.
• Not an attestation of mandate validity. The receipt records the termination of a previously-valid mandate; the mandate itself is specified elsewhere.

​

Companion IETF Internet-Draft

​

See also

• Canonicalisation substrate — the JCS discipline
• Settlement attestation — recurring-execution counterpart
• Refund receipt — post-cancellation refund counterpart
• Conformance vectors — full vector corpus
• Substrate authorship and provenance — citable AlgoVoi authorship record