why2 reasons
mandatedestination_not_allowed
op 0 pays GBSUD6NHS6VL3NJ6VAI64BF2JLUNDW2W3XOLGLOHIFYOXB4EQZSDOVKX, which is not in the allowlist
counterpartycounterparty_denied
GBSUD6NHS6VL3NJ6VAI64BF2JLUNDW2W3XOLGLOHIFYOXB4EQZSDOVKX 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
- 4c1a68b13fe3af17a0af6d12a2b068c274775e1797d25709990f87c893b1a0b4
- request
- 6495e75f78ff1184c9e56044714aee3d76b8bf734077dad230913480b1a36261
- transaction
- 01a9b5f374304705e8d978bbeefefa3ced3aed59aca92fb72d4d647c7c2985eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53416
the chainentry 53416
- sealed to the entry before
- 114dd095b39c4acfd035e4a39316a6643ff8db1bbad56c9bfd8ff4814dfc2fe9
- this leaf
- a9e1b4885c5270b17267d7aa03aa3d0f22fc36cf4f4af5129e03cbd9a1387df5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nEQCwMUXIcOHHpgR19BdClN8ft10CX7f851BKWfVE1tpXcwcqVmi3zH6FRhlSix6HHuLVlhP1b3gAvI8T5lDDA==