Error Status Reference

This page lists current runtime status usage for merchant POS endpoints.

POST /crypto/v1/createInvoice

Status
Error / Behavior

200

Invoice created

400

Validation or save failure

401

Missing body (legacy guard)

403

apikey or merchantid missing

405

Invalid content-type, invalid merchant, or invalid API key

408

Non-matching merchantid and API key

412

Merchant not actively enrolled in cryptoPOS-V1

420

Invoice object creation failure

501

Server error while validating merchant/API key

502

Merkle validation/generation failure

GET /crypto/v1/status/{id}

Status
Error / Behavior

200

Success

403

apikey or merchantid missing

404

Invoice not found

405

Invalid API key / merchant lookup failure

406

Missing id path parameter

408

Merchant not associated with API key

412

Merchant not enrolled in cryptoPOS-V1

501

Server error while validating merchant/API key

505

Server error while fetching invoice data

GET /crypto/v1/list-txs

Status
Error / Behavior

200

Success

400

Invalid FromDate or ToDate

403

apikey or merchantid missing

404

No transactions found

405

Invalid merchant ID or API key

408

Non-matching merchantid and API key

412

Merchant not enrolled in cryptoPOS-V1

501

Server error while validating merchant/API key

505

Server error while fetching transactions

Notes

  • Status mappings above intentionally reflect current runtime behavior and legacy code paths.

  • Some status codes are non-standard for these conditions; see Known Caveats and Legacy Behavior.

Last updated