Skip to main content
Several AroPay endpoints return a .nota file: a serialized Notareum resource. Think of it as a portable, typed envelope for payment artifacts: instead of copy-pasting hex strings or screenshotting receipts, you exchange a file that any Aro surface understands. All .nota endpoints return the same shape:
Write the nota payload to disk under the suggested filename:

​
The three kinds

Address card

GET /wallets/{id}/nota. The file twin of a receive QR: public address plus chain context, no key material. Safe to share freely.

Key export

POST /wallets/{id}/export. A custodial wallet’s private key, re-encrypted under your passphrase before it leaves the server. Handle like a secret.

Transaction receipt

GET /transactions/{id}/nota. A notarized receipt for a transaction that reached the chain. Attach it to invoices or audit trails.

​
Address cards

Any wallet (custodial or external) can produce an address card. Recipients import it into any Aro recipient field (including external wallet registration) instead of pasting an address, eliminating transcription errors.
A malformed or wrong-type file is rejected with 400 invalid_nota.

​
Key exports

Exporting a custodial key is deliberately guarded:
  • Session-only: API keys get 403 session_required; you must be signed in to a browser session.
  • You supply a passphrase (8–200 characters); the key is encrypted server-side with PBKDF2-SHA256 (310,000 iterations) + AES-256-GCM. The plaintext key never crosses the wire.
  • Only custodial wallets can be exported; there is nothing to export for a watch-only address.
See Export & backup for the full flow and handling guidance.

​
Transaction receipts

Receipts are generated from on-chain state, so they exist only for transactions that actually reached the chain. A transaction that is still QUEUED (no hash yet) returns 409 receipt_unavailable with details.retryable: true; retry once it is PENDING or terminal. A transaction that FAILED before anything was submitted can never be represented and returns 400 receipt_unavailable with details.retryable: false. For redeems, the receipt reflects both legs once settled.
.nota content is opaque to the API consumer; treat it as a blob. Its internal structure is a Notareum implementation detail and may evolve; round-trip it through Aro surfaces rather than parsing it yourself.