Anchor

Discover payment details from simple identifiers: phone numbers, emails, QR codes, and more.

An anchor associates a user-friendly identifier like a phone number, email, or account number with payment information. At its simplest, an anchor maps a phone number to an account number. Anchors can also carry richer data including source and target details, amounts, and custom fields, providing everything a client needs to construct a payment intent from a single lookup.

Anchors are pure data — they don't hold balances or move money. Other systems query anchors to resolve identifiers and assemble payments. Common use cases include alias directories that map phone numbers or emails to payment credentials, and QR code generation where scanning a code retrieves all the details needed to pay.

Anchor forwarding enables federation: if a lookup finds no match locally, it can fall back to a remote service, and new anchors can be replicated across directories.

Endpoints

MethodPathDescription
POST/anchorsLink a user-friendly identifier like a phone number or email to payment details.
GET/anchorsQuery anchors with filtering, sorting, and pagination.
GET/anchors/{id}Retrieve an anchor by its handle or LUID.
PUT/anchors/{id}Submit a new version of an anchor.
DELETE/anchors/{id}Permanently remove an anchor from the ledger.
POST/anchors/{id}/proofsSubmit a signed proof to an anchor record.

Access & History

MethodPathDescription
POST/anchors/{id}/access/!checkEvaluate what actions a signer can perform on this anchor.
GET/anchors/{id}/changesRetrieve the change history of an anchor by its handle or LUID.
GET/anchors/{id}/changes/{change}Retrieve a change record for an anchor by handle or LUID and change number.

On this page