why2 reasons
mandatedestination_not_allowed
op 0 pays GBPUNP5FAV64WXUSFWEEO4RNXF4CBD23XR4V5KSH2D3KE7J5TQRHK4LJ, which is not in the allowlist
counterpartycounterparty_denied
GBPUNP5FAV64WXUSFWEEO4RNXF4CBD23XR4V5KSH2D3KE7J5TQRHK4LJ 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
- 89ff2ab726aa05833aa765649064be708284531ec8e20601c0860bfb9c5c1ef9
- request
- c316687a4cb88b79831c6ee1017b85d12fe81846c6898bcbf98a6254fb935e66
- transaction
- e6de880e0f532ba82d04dd376a37393eab5e23e05b7a1dcfa345bf63381a3783computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3570
the chainentry 3570
- sealed to the entry before
- 8675b921539dc6673bef9f65788dba25882deeada7611220807213e222e74dba
- this leaf
- 5526b7d80c7a2daf76b8fa0b76f1dea5bfbeec95efdb7922daa67d6a73a4f484
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a/aDUzvJPVVb3ekB51Rp/uycPFsbl7k4RT99iCMQieCsWn2HdSglV2gGAfXBLrT6KCKbBe2ACDrl/7RdRZtjDA==