why2 reasons
mandatedestination_not_allowed
op 0 pays GBLWVPU3U55DJNN62VLZTFIDAIGKUV2376PJZE4EHUW2IHZC4RCV3G7E, which is not in the allowlist
counterpartycounterparty_denied
GBLWVPU3U55DJNN62VLZTFIDAIGKUV2376PJZE4EHUW2IHZC4RCV3G7E 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
- b516b2ffbe0ac956168297af1d4b5d324303e94b769542e5dfe88765b57354d9
- request
- c918425ddfb84bca1055ea5f97fefdcb7007f3d3b2bb5160dde21d434f29196d
- transaction
- 6dface8e231d96715e377128dd720fbd511106cd8457d4e9bce0aeb60a0764b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 872
the chainentry 872
- sealed to the entry before
- 48213c6486d42405e59677fd0efe44494a9ab9183e63efe71f0464da78ce839d
- this leaf
- e9aaf4cac9e01908511a8388f67354a9166cc6bb8b85a6728204cf1926648c34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IKO9DE/fX6MLTDSrkTO7p+Ly8Efxs3Cw9p5y4c7dAC1tYybDhKdlU1gq4f20KUkw3NKRaCGix4OhkhGp46/ACg==