why2 reasons
mandatedestination_not_allowed
op 0 pays GBNFYXH3USERXLH7LPGCPZIBXAFYZFEZPI3MPOZESNAEUB6PJXWRV4ES, which is not in the allowlist
counterpartycounterparty_denied
GBNFYXH3USERXLH7LPGCPZIBXAFYZFEZPI3MPOZESNAEUB6PJXWRV4ES 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
- cdeb29cdb6b3f7b07100dfcef81f7fe60b7f1bb38746fa717d15ea89074d2490
- request
- aa7a7ca93f8b93c554f8632f0c2c55d90d414fce8908247c3acca354ddbd20d1
- transaction
- 5eb013b1876b1d942eda80b6bdd9817e0eb784305ebe281851041f2130fda993computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28788
the chainentry 28788
- sealed to the entry before
- b8d6df0dd6d4321499606356804653befd54860529eeba362946bf9790e19b9f
- this leaf
- 5d9ce3c9df67a19f991e22c2839946d800ac42bba6b18e22469007b0ac0ae895
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JPB32GnvpVBsWPOgFNHEKCV1ujU8jQFgeFua7r+IDVRWeR6qI9yKic6nAp9FC7djV8a7k4nz8ghnLCc/53mKDA==