why2 reasons
mandatedestination_not_allowed
op 0 pays GD6ZZAK4BPTYDW66PCBYTDNSBN7SD4QUA2AMQ5LLTJLUMENJBGVMS43J, which is not in the allowlist
counterpartycounterparty_denied
GD6ZZAK4BPTYDW66PCBYTDNSBN7SD4QUA2AMQ5LLTJLUMENJBGVMS43J 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
- ee8917844592b902a17bc221f6a5f65bd5e750bdbd019a8215370f41d3c10557
- request
- d915fc8a1d48af600bf68f8577aa7cd0058b2885c9dfc08b9437a3496063530f
- transaction
- e37eb6493235f8abf3274c051e6ab9dce02cbf7422c69e22d5cb4f06ec4d9c64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58276
the chainentry 58276
- sealed to the entry before
- c53c1f3ed213662e68c9d51a5f1055ca220b7c2f2827e3c6979354e6625fb56e
- this leaf
- c3dd58c45b93b3fcacd2855e11807bb153d6cce9805eb046b3371cc42065eb16
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G/XR/CkR6keHALdhBr8BiAInkpmmArC4tpsTSJuA1gp7nEmv4FMcrLf88/IUGUrs7fb6o/7JWCwfHD0gw4/mCQ==