why2 reasons
mandatedestination_not_allowed
op 0 pays GBWAODFQQTN4HOBUPRB3EHMPEEIVVEORWTVALKMQRJ7QCEZCPJO34P6A, which is not in the allowlist
counterpartycounterparty_denied
GBWAODFQQTN4HOBUPRB3EHMPEEIVVEORWTVALKMQRJ7QCEZCPJO34P6A 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
- ed386019ccbd5a7c159224b3712376fe21533280e70ea9b332267aeb4f20892d
- request
- d35bce3de9035bbda9b66d27e383e93a6da6f59c2659788d4b4240b8c21235f1
- transaction
- 5e7d54a28a1ae8cc8ec3a080c1a3c3ffc5a9093cbfb93443f4d0b9ce6be53eb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44659
the chainentry 44659
- sealed to the entry before
- 93bfed35c0d329c573ecbac8684a9e57ed691c8679212d52cb94484fc5c5683a
- this leaf
- 5e9e2f070be4a8516b6be554ad124445758ba0d44c9bd5cf8947d1ddfd1f00d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PPD79Ywt/LvqCizz5P36E06ekywvOTOdYxn6Bi5VG4BjMJfHGXNZ+glssKI17e0c184aQAAOPH9gxKaQoUj1CA==