why2 reasons
mandatedestination_not_allowed
op 0 pays GBMSJOMRLL5AHHYTLMZK5SH3CZRTYHKEGIZHE4INORO5VCZRSURM4BQF, which is not in the allowlist
counterpartycounterparty_denied
GBMSJOMRLL5AHHYTLMZK5SH3CZRTYHKEGIZHE4INORO5VCZRSURM4BQF 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
- c2eb8c2ca0bf1b8490fe5a7496915b5fd1d3076bc4b533172469a5a991849031
- request
- 29fc6c543a599f5959a8ce249ac4e707c51d2e07922a93f3317dab56258b9d28
- transaction
- a72ad27e34e1f582709f6c1e994ce4d9c58f4b7595316a4f4cd61cb777d99f56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37509
the chainentry 37509
- sealed to the entry before
- 5d0c3d48094a6e11f70e1b546c2e5b65d3650e3ef803dd9934181d9f3ec9207a
- this leaf
- d200cace8cff5c3150271a05667929c2ddd6a99e6a1317ac1992debe7e972e0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dadr8xLiRtWYxMlBiVEaAKVm1bYgXKWDyGW7QRYoNYzvmSokxG3jGvEmS6tyurFmD6KnPJuEvM94xSkpdFL4Bg==