Mint receipt
Receipts
Mint Receipt
Create a cryptographically signed, transparency-log-anchored receipt event.
POST
Mint receipt
Creates a cryptographically signed, transparency-log-anchored receipt event. Receipts are validated against the registered receipt type schema before signing.
Receipt types
| Type | Name | Required Fields |
|---|---|---|
payment_receipt | Payment Receipt | amount, currency, provider, provider_reference, subject |
security_event_receipt | Security Event Receipt | event_type, severity, subject, outcome |
delivery_receipt | Delivery Receipt | item_reference, recipient, delivery_method, delivered_at |
compliance_receipt | Compliance Receipt | check_type, subject, result, framework |
custom_receipt | Custom Receipt | subject, event |
Headers
UUID for idempotent minting. If you submit the same key twice, the original receipt is returned.
Request
UUID of the issuer signing the receipt.
Key ID of the signing key.
Signing algorithm:
Ed25519, ES256, or RS256.Receipt type name (e.g.
payment_receipt, security_event_receipt, or a custom type).Subject identifier for the receipt.
Receipt payload — validated against the receipt type’s JSON Schema.
Optional metadata attached to the receipt envelope.
Response
UUID of the created receipt.
The receipt type name.
activeUUID of the signing issuer.
Subject identifier.
Cryptographic signature:
alg, kid, value.ISO 8601 timestamp.
Webhook event
Areceipt.created webhook event is delivered to all configured endpoints after a successful mint.Authorizations
API key for machine-to-machine authentication
Headers
UUID for idempotent minting
Body
application/json
UUID of the issuer signing the receipt
Key ID of the signing key
Signing algorithm
Available options:
Ed25519, ES256, ES384, ES512, RS256, RS384, RS512, PS256, PS384, PS512 Receipt type name
Subject identifier
Receipt payload validated against schema
Optional metadata

