why2 reasons
mandatedestination_not_allowed
op 0 pays GBH444DP3W5QQFXPAGFAFXU67IISTLQWB2WJTO5PZZISCWJI6JAMQKVD, which is not in the allowlist
counterpartycounterparty_denied
GBH444DP3W5QQFXPAGFAFXU67IISTLQWB2WJTO5PZZISCWJI6JAMQKVD 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
- a640f072081c32389b771d5d4620d3a86bbd07de675ebe284790e080161f9f53
- request
- 1f1cbdc920cf6d9514ea5427c112036dddcbc5de00defe6d345f15cc21176ae4
- transaction
- ef395ecfeba64cd61b66a3a84531f3c582e3ad0cafc7984c9584585608abc8c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68685
the chainentry 68685
- sealed to the entry before
- 15c7631cd240240f4651be8f533ddcd940744f4ea4e5ac2a3ae1d46445fdc815
- this leaf
- a0ba13e9fe846d03cc28c9eaf436ed4acb469fac5d7c5af538f9c94e643a048c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gR7iBfnSe8FNgym36GQWVth5OY9ukLcE1P5OCs++wLDaufUbkR+KZ+pVM1JV0eT0dFfLrvZ7CX9T4rKM7It0Ag==