RED THREADS.

Money. Identity. Technology.
Follow the money. Find the decision.

← All subjectsSafety & rights

Recipient role

Onboarded TCAP hash-list recipient

Authenticated recipient role in current public API documentation; may maintain a checkpointed local cache. No actual customer, synchronization result or account restoration is identified.

What the records show

TCAP content-hash API — current public docs → Onboarded TCAP hash-list recipient

documents withdrawal metadata and incremental update handling

Hash records carry deleted and updated_on fields; checkpointing supports recipient caches and monitoring deprecated values is recommended. This interface can convey withdrawal, but recipient synchronization, erasure or reopening prior restrictions is unobserved. The documented output is withdrawal metadata for a recipient, not a command that restores an account or proof that a recipient applied it.

TCAP — current content-hash update documentation ↗

Further reading

TCAP Archive, Hash API and Trusted Flagger access ↗

Read the original sources 2
TCAP — current content-hash update documentationTCAP — onboarding prerequisite for API access

See the connections

Open this part of the network ↗

What the connections say

1 relationships
1

TCAP content-hash API — current public docs → documents withdrawal metadata and incremental update handling → Onboarded TCAP hash-list recipient

Hash records carry deleted and updated_on fields; checkpointing supports recipient caches and monitoring deprecated values is recommended. This interface can convey withdrawal, but recipient synchronization, erasure or reopening prior restrictions is unobserved. The documented output is withdrawal metadata for a recipient, not a command that restores an account or proof that a recipient applied it.

Read the original source 1
TCAP — current content-hash update documentation