Regulatory & protocol compliance engine
Clawback & Revocation Policy
TRA implements Stellar CAP-0035. These powers exist to protect consumers and satisfy regulators — and they are deliberately constrained by multi-signature governance.
Policy simulator
Select a scenario to see the governance outcome under the published policy.
A competent authority issues a binding order against a holder. Compliance opens a case file, legal verifies jurisdiction, and the board signs the clawback operation.
Why clawback?
Protecting consumer funds. Stolen or mistakenly transferred tokens can be recovered and returned instead of being permanently lost.
Enforcing court sanctions. A regulated issuer must be able to comply with binding orders from competent authorities and sanctions regimes.
Meeting MiCA EMT criteria. Electronic money token issuers must demonstrate control over the redeemable claim, including the ability to remediate illicit holdings.
Multi-signature governance
Live signer configuration of the issuing account, read from Horizon.
Configure the issuing account to load the live signer set and thresholds.
A clawback is a high-threshold operation: the combined weight of independent board signers must exceed the high threshold. No individual key can execute it.
Issuer flags
The issuer can revoke or freeze authorization on a trustline when required by a court order or sanctions screening.
CAP-0035: the issuer can claw back tokens from a holder under a documented, multi-signature governance decision.