why2 reasons
mandatedestination_not_allowed
op 0 pays GDKYZXOBVAUUPL7F45EELQCFY5IQE53QR227AH2HCYRSW4FC5O2ZAERU, which is not in the allowlist
counterpartycounterparty_denied
GDKYZXOBVAUUPL7F45EELQCFY5IQE53QR227AH2HCYRSW4FC5O2ZAERU is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- f1c052840c5f5cad548e3e4c6759728a79c8a5d0870ecb6f6bb494cd549c0809
- request
- 5ed943d713d2e8b90ce2b9222ccf79484e4c192635d658e4a028f86d7e912642
- transaction
- d89a3296fe90ef6190b258d336956bbc627cd25e340b28c25468e3d32a82f81dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 287
the chainentry 287
- sealed to the entry before
- 82871d0529db4aa20f2fff379722ee0abc31f4a389c9d9819d80129d4f29b674
- this leaf
- 827d0d6f4e5e5b15897157354219e1f6244381395cff14161e9dcc5feebf0788
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2YNkYk4JnZeKDux2hpZ4IHYZi+O3iov3tQybVkjdn8shLOxUfY1xqkjXSDhg5uwd/k787PsRAxI3ui8rNvbTAQ==