why2 reasons
mandatedestination_not_allowed
op 0 pays GDU3UTKMN37CPVYY3WZOXWW3VDW6Z6RGDQJ75E2OL73FSMCG4QWNEBJ7, which is not in the allowlist
counterpartycounterparty_denied
GDU3UTKMN37CPVYY3WZOXWW3VDW6Z6RGDQJ75E2OL73FSMCG4QWNEBJ7 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
- cb9ce5e48d1fd6afeb9369ec5f0f9411a355f89286868d4f9493e2f2c2ce7101
- request
- 9dc2f0bc01884fcb1a625d1dc5cfb59aad8cdd532ea5f6f66ba4cb05ff394f8f
- transaction
- b90093eb42fcedda6dd2f8261193af3624c2f2868eb7499993651b88c8ff3f17computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24124
the chainentry 24124
- sealed to the entry before
- abfea7929915f1218860e532894e4f28e3f71cd4e7f72696e0d64700251c3ea0
- this leaf
- eca8097fd1f5ca428cff6edafd0bee5614a7412d88d0b3852089d320f8af0f57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W0FPek75lkkqQtXdfz+Hl5F9JQKi4M34iacOxUDUJlh/zpKDRSKkc4W6fzB7oaiL79KoAx23aQY0v2/OZTVLBg==