why2 reasons
mandatedestination_not_allowed
op 0 pays GDOVYV4DIZXVUTI7O6JUC5LUY4XIAAAZCUYJANMGDZVMQ4CT6JEWEFP4, which is not in the allowlist
counterpartycounterparty_denied
GDOVYV4DIZXVUTI7O6JUC5LUY4XIAAAZCUYJANMGDZVMQ4CT6JEWEFP4 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
- 1433c728ca69c8cd7d72c826ed0a35169d0adc0692e5df2f9cf47fcba7e9c522
- request
- 8e6cda10cdce5e1a026b989aa2e1a4eb81bc2f6d20345c33116d2a0008f35856
- transaction
- 287849b321f55bdb8654234ebcf7ca5acb0a49f45f557894c25b08a9d4282711computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42433
the chainentry 42433
- sealed to the entry before
- 97fd4947768495070103b3c7d64fe047b27a9162d9555851aabd97675f4ec3ad
- this leaf
- a2bd4aef72c8c5753265a3fd77674409c2820394980e1624ad247f92c2f98279
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3Mt04A9E+wrhTUSwDIcKjNuhr5x1D1/Y12qIU0a7MN+CwRgApT13kghVLxfn+yevdNAPETqQLlP+mxhQiTz3Ag==