why2 reasons
mandatedestination_not_allowed
op 0 pays GD5C2CPHOMEXEWNXWRCHWND35RRBRYEHS3JZVFKLGLINIKYN74JXIELR, which is not in the allowlist
counterpartycounterparty_denied
GD5C2CPHOMEXEWNXWRCHWND35RRBRYEHS3JZVFKLGLINIKYN74JXIELR 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
- 01e52c9596c67db1240f8ec535d6703c8ec7dc57b64ede0d447d9d5d0844baf4
- request
- d974e9de5f15916575f1bd61062e93c8af3f1af37d178f45db2c25fdec95447d
- transaction
- 3eb25ba84fc3974acc2c6f5d792663a4d439860c7c33cb4dca6bc074f4656e13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25898
the chainentry 25898
- sealed to the entry before
- e2855fa26e1d5ccf446e7697d963dc686e99a5a54981d95cef6bd1e83e057153
- this leaf
- f670e1d21bcbb3333a07c8f64d2d19735722e3f46c6f2a1fb3ed96cb66ad60e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jXhlnljnfEOazoeGKvUocBWGLqKRGJLBgbv8mV6pC3xjv9XsgCyYVJ90CkxNQbkmjUAghrqoR2qtcBiJJ7MOCQ==