why2 reasons
mandatedestination_not_allowed
op 0 pays GBKUQDTNRZIYDXYPBDL3VN4KBDZP7A3XPA63PBKWCYHQBKVWOMBBJXEM, which is not in the allowlist
counterpartycounterparty_denied
GBKUQDTNRZIYDXYPBDL3VN4KBDZP7A3XPA63PBKWCYHQBKVWOMBBJXEM 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
- ba010d1f9902a90fb502d4c449a008f8bedac529e5b93da47af67a0bb2b99e0f
- request
- 07da4c5775bead73a93f545f7c1315f57afc235937fc3eea6bc32d6de3b9fc70
- transaction
- a9ed6ab33002dee5f6093f0007add89a2d5aafac4db276d06589836d4ce131d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50078
the chainentry 50078
- sealed to the entry before
- 2968fb01168ef1c784a38bcf8fdd83c3825f924ca14c49e08f09e98021590015
- this leaf
- 98010221f6600ff515350e642f9c94392f6a17b8354b19f0ff94e9acc23af3ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SZYE1EJ2306YreAZW818U0LWwe4oBQ95Y13yURgmYC6K4fY8XOihJetk8t/6+fmjhVfbLFFI37rairbY+7EqBQ==