why3 reasons
realitydelegated_fee_payer
fees are paid by GDJKTTJJCMHEIKGJ3MPEU2EOTGA6TFQ4HAPBJCGJGPR65I5IRUHFE6IK, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GDDYQ6SMHIWCU7V7AAYZF3ZHSPSEEAJ326JI7NVEGMPML7GPT5PFS2BS, which is not in the allowlist
counterpartycounterparty_denied
GDDYQ6SMHIWCU7V7AAYZF3ZHSPSEEAJ326JI7NVEGMPML7GPT5PFS2BS 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
- c13d1d9f4f231ec6a9ce13fafe6cedf92338d6e7348b00789bfa8481d272f029
- request
- 42213ff348a646d2af8d70504ef7a6aa650e5312be2e8d358ab080380e0c45a6
- transaction
- 21646bd2b51a7eae969831e13f0c09f0c9cc4e82660558111147ad8c5de4b193computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73680
the chainentry 73680
- sealed to the entry before
- 11788cf2739ab222977873535e5d372a3515d314042843a447496ca63c64c70e
- this leaf
- 97080ea3fc3c7453d8610c825d764f32be8ee2b57dde4f476d0269a5b4511fae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5/9PDYcBDZa58FkangBK4Plo1r+TDCTY0B1QnvzVaA72lBBZeDr2I4ZeURZZ2q6f6TE7jZNnrg430uElRWaJCQ==