why2 reasons
mandatedestination_not_allowed
op 0 pays GB26ZD7RGYWDC57HSUTPXTO3T7VMKB2IBYDWENQFBBOA75PGS575YW2C, which is not in the allowlist
counterpartycounterparty_denied
GB26ZD7RGYWDC57HSUTPXTO3T7VMKB2IBYDWENQFBBOA75PGS575YW2C 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
- d777d6cfed988403eb0e895bda928c95ce5cdf2d910f164ff74a9da4ed6659ae
- request
- 466886720ada926ec8510a2387a9f5c3b2b5a9dc7145e5a5fd211e88ebd9480a
- transaction
- 8aee22e956d8e0e431525f3c58ebcd5cd03016118a53454486295f91cf5969b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6415
the chainentry 6415
- sealed to the entry before
- be899d5362ab0125c0a752ccea01a90f11f01458d23e11b2b8aa31c0d6c20f0e
- this leaf
- 0a35d936ca5c35bf39afa0aa84d9bc445de25cb2dc32d22c160c1405d144db12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4ydHAMAmCG2ApgUzIQncdzrOJnpipYiDuFTZ2J/xQbWHiqdc0kifbqkjIig7SssoQ8eqBguDkUDCc0gfbEXuCw==