Manual decision for missing TRM
Accept or reject destinations waiting for a Travel Rule message (missing TRM), without waiting for a TRP webhook or the missing-TRM policy timeout. You can submit before a destination enters the missing-TRM wait; if it can’t be updated immediately, the decision is applied on the next processing attempt instead (status ACCEPTED). Check status in the response to see whether the decision has been applied.
Headers
A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.
Path Parameters
Customer integration unique identifier
Fireblocks transaction unique identifier
Body
Request to manually accept or reject destinations waiting for a Travel Rule message (missing TRM)
Decision action for destinations waiting for a Travel Rule message (missing TRM)
ACCEPT, REJECT "ACCEPT"
Optional reason for the manual decision (e.g. 'Internal KYC approved'). Do not include PII.
500"Internal KYC approved"
Response
Decision applied (status APPLIED), accepted for the next processing attempt (status ACCEPTED), or accepted early (status PRE_ACCEPTED).
Response containing the result of a manual missing-TRM decision (POST write or GET read).
APPLIED - Decision applied to at least one destination immediately. ACCEPTED - Intent stored for deferred apply on the next processing attempt. PRE_ACCEPTED - Intent stored on the transaction before destinations entered the missing-TRM wait.
APPLIED, ACCEPTED, PRE_ACCEPTED "APPLIED"
Decision action for destinations waiting for a Travel Rule message (missing TRM)
ACCEPT, REJECT "ACCEPT"
Source of the manual decision. Values are lowercase.
manual, policy "manual"
Transaction ID
"b70701f4-d7b1-4795-a8ee-b09cdb5b850e"
Number of destinations where the decision was applied
2
Number of destinations that were skipped
0
Per-destination details
100