why2 reasons
mandatedestination_not_allowed
op 0 pays GDYBBSEAQ4WQIKXQDUPLQFUO4KGGTWW3M43GCXLOSDIKGC24QOUUTRL5, which is not in the allowlist
counterpartycounterparty_denied
GDYBBSEAQ4WQIKXQDUPLQFUO4KGGTWW3M43GCXLOSDIKGC24QOUUTRL5 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
- 645a6939270d3d827f0ef69e806daf2136c7eb9508cd3f18c17ab63efe9d494e
- request
- 8c15a63bdef31926946f6349948e57d6fd999d55bc86d920741ab80db7859e56
- transaction
- d86b9989ac5e2e7f9ed62951c611e2c3b7dd42f512db2fda9fdbbe65eead2b24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1064
the chainentry 1064
- sealed to the entry before
- 3ae6cb0321a1dad9c16051a9004b1a40a2dbb82b9aac64b02d35aed003f2f8bf
- this leaf
- 3f5e24962a309590ea228ca2cdeda293655370fe26e4c0a5289c5c0240adf981
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 78En9xXPStUHZ9Fflmz1BaXjV10in20MgGzb8Cmi2ESz0C46w1QvyV72ngWhddG+mrp9M2jT3+oUWRy/5VjVDg==