why2 reasons
mandatedestination_not_allowed
op 0 pays GD3PWYGMPBLAFRR43YZATRUN4YILYUDC2HWMTZWHYERPMLGETL2T53R4, which is not in the allowlist
counterpartycounterparty_denied
GD3PWYGMPBLAFRR43YZATRUN4YILYUDC2HWMTZWHYERPMLGETL2T53R4 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
- 16b4d34058bf6eab2ed5314fef78e24efc6c3bb7f74ddc985306d793e2ad484f
- request
- ce9273a2595921bde5ffe98db8a122e0954ed19a02dad5d89200fffb1098eed7
- transaction
- 3c90382d60bb01691c6b5a9cfab411077ee62e4ad64dc6e03139ab80f2c62847computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49032
the chainentry 49032
- sealed to the entry before
- 253bac6259b3135f19afd8a0f84c6c3cf4d07a9cc2212e663bd07b80a4bb9f3f
- this leaf
- 7dae1883c8aa0774c2a0ea0775f75b7208e534e709b73b64e09978780b579303
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KgJXXjOeBSQffDE9EvFiELHXzYdaAV3ZWf+Kthc1hOpx0EzIGwsKS+p8CKayyrHr6+VGTUfhEMfW8mZFvFB0AA==