For the complete documentation index, see llms.txt. This page is also available as Markdown.

Changelog

All notable changes to the Phalcon Compliance API are documented here. Listed in reverse chronological order.

2026-07-16

Introduced the riskProfile field as the single source of truth for risk data, replacing multiple legacy fields.

Added

Field / Schema
Applies To
Description

riskProfile

AddressScreenResult, TransactionScreenResult

Structured risk summary containing entityRisks, interactionRisks, and behaviorRisks. Always returned.

taskId

Synchronous screening responses

Synchronous address and transaction responses now return taskId.

note

AddressScreenResult, TransactionScreenResult

User-defined note for an address or transaction.

RiskProfile, EntityRisk, InteractionRisk, ExposurePart, ExposureTotal, BehaviorRisk, BehaviorRiskFields

New schemas

Supporting schemas for the riskProfile structure.

Deprecated

Field
Applies To
Migration

includeDetails

Request parameter

No longer required — riskProfile is always returned.

alerts[].riskDetail

Response

Use riskProfile instead.

isBlacklisted, blacklistedInfo, isWhitelisted, whitelistedInfo

AddressScreenResult

Use riskProfile.entityRisks with type blacklist / whitelist instead.

fromIsBlacklisted, toIsBlacklisted, fromIsWhitelisted, toIsWhitelisted

TransactionScreenResult

Use riskProfile.entityRisks instead.

Removed

Field
Description

enableReScreening

The request parameter has been completely removed from the documentation.


2026-04-29

Deprecated the address rescreening parameter and removed the related status field.

Deprecated

Field
Applies To
Description

enableReScreening

AddressScreen request parameter

Retained for backward compatibility but has no effect.

Removed

Field
Description

reScreeningStatus

Removed from the AddressScreenResult response.


2026-03-30

Added support for multi-input BTC transactions.

Added

Field
Applies To
Description

fromAddresses

TransactionTransfer

List of source addresses for BTC transactions, where a transfer may be funded by multiple inputs.

Changed

Field
Description

TransactionScreen.transferIndex

Can be used independently or together with toAddress. For BTC transactions, it represents toAddressIndex.

Last updated