why2 reasons
mandatedestination_not_allowed
op 0 pays GBVBYSNT5C3WFON7Q2DYLUKVGLOV32YU2SALQJHO4ZP4E6B7V2LODGVK, which is not in the allowlist
counterpartycounterparty_denied
GBVBYSNT5C3WFON7Q2DYLUKVGLOV32YU2SALQJHO4ZP4E6B7V2LODGVK 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
- b3b67a70dd332a1a34a2df35d5f858444703ff6e6a0dae16f41224a881cf37c5
- request
- 21dc717e85fa737b9c736b6c36688e06ffb5857dfde88568598aa0e237ee1408
- transaction
- 13086b537f05f74bb9e8039f2fc72bdd7dea71cd95c3f9281fabdc9ffd0f6413computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2391
the chainentry 2391
- sealed to the entry before
- cbef907493c7536cbe13e633a377aa07f18271ca17406ff6b4dd8a2019e18a3a
- this leaf
- 538d5814811ca846b57473d72c4a05f378e90a35959039232a8868279f37edc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f08bXSDN6wpEYTv0ooS0Xx8B11nSuLXVDvp6WzwIuIkkV/swf4wdJfkvPy3VolIMbQt1XiC+JmO5kza6ASSMAQ==