Transfer Compliance

Create and inspect owner-scoped regulated-transfer workflows, commitment-only identity and wallet readiness, VASP counterparty interoperability, signed policy decisions, reviews, and delivery evidence without exposing Travel Rule cleartext or granting settlement authority.

BUSINESS CASES

Where this module fits

Travel Rule and IVMS101 orchestration
counterparty screening and key selection
pre-settlement transfer eligibility
credential and wallet-control readiness
signed compliance evidence reconciliation

PRIMARY CONSUMERS

Who integrates it

compliance teams
VASP and payment integrations
treasury and custody controls
transfer agents
audit and reconciliation agents

PREREQUISITES

What must exist first

an authenticated owner profile
compliance:read for reads, compliance:write for subject workflow commands, or compliance:review for decisions
RFC 9421 request signing and a stable Idempotency-Key for every command
a defined jurisdictional and transfer policy
caller-owned acceptance rules for credentials, counterparties, evidence freshness, and state

RECOMMENDED WORKFLOW

Compose the module safely.

01
confirm the sixteen public transfer-compliance contracts in deployed OpenAPI and authenticate with the least-privilege compliance scope
02
inspect credential and IVMS101 readiness without requesting regulated cleartext
03
register wallet-control evidence, create a consent-bound disclosure manifest, register a VASP candidate when needed, and authorize only the digest of a client-side encrypted envelope
04
register or select a VASP counterparty, then re-fetch it to validate status, due diligence, protocol, network, jurisdiction, validity, and public keys
05
create an idempotent transfer intent, prepare required evidence, and submit only credential and proof commitments for screening
06
record reviewer decisions under compliance:review, retain exact commitments and receipts, and re-fetch state before any separately authorized consequential action

AGENT INTEGRATION

Machine-use boundaries

Generate calls from deployed OpenAPI and bind every transfer, credential, vault, wallet, manifest, envelope authorization, and counterparty identifier to the authenticated owner and original workflow.
Never place regulated identity data, raw credentials, ciphertext, private endpoints, or settlement material in prompts, metadata, logs, or caches; the API accepts and returns commitments and applies no-store responses.
Reuse an Idempotency-Key only for the exact same method, path, owner, and body; generate a new key after any intended input change.
VASP candidate registration is not credential issuance, and envelope authorization neither receives nor delivers ciphertext; formal issuer and reviewer authority remain separate.
readiness.transfer_ready is prerequisite posture, proof_state=INTACT is evidence-chain continuity, and an APPROVED decision is compliance evidence; none of them signs, broadcasts, settles, or moves value.
Re-fetch counterparty and transfer state before use, preserve decimal amount strings exactly, tolerate new enumerated policy values, and fail closed when policy does not recognize a state.
The two remaining planned operations are non-executable until their separate formal credential issuance and assignment-filtered review-queue authority gates are completed.

Register only production-listed routes as executable tools, and re-fetch the deployed OpenAPI before generating or sending a request. Source-ready routes awaiting deployment are preparation references; planned contracts are non-executable.

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.