why2 reasons
mandatedestination_not_allowed
op 0 pays GB5MXCGH6FOCUZKWCUTM7FUAQKUOKPMA5UAWEEN7FW7CTD4WBVZEXL3X, which is not in the allowlist
counterpartycounterparty_denied
GB5MXCGH6FOCUZKWCUTM7FUAQKUOKPMA5UAWEEN7FW7CTD4WBVZEXL3X 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
- 5924d6cd0f6024e7b3005809208ab028e225d1002c2f0ed346bf290fa80aca2b
- request
- c8b1123d0d3689efaa16f403ac0a2b62d6cd5936bdc443e55bf446c8a1c45692
- transaction
- e53fc59d81dbbee33c6991328a0932dca9564f508b8d5d74f379f22710879397computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30088
the chainentry 30088
- sealed to the entry before
- 98b51327926b649a77ab0305661a4097c2d860b536126a38e6ff29c6ef6d2016
- this leaf
- 09c3807bdf09ba76e5861f0019ebff285101b17d10a87ac4b09c864b71880929
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VRwAJIpp0GBipD35aEW9noVJJMKoqR138kq4dcwGaaKmA6p2Uv8SNPxa2WBlfTzSyL8TPhXNynDZ0uONozCIBQ==