why3 reasons
realitydelegated_fee_payer
fees are paid by GAGBKTB2TYHVC63O2AKDC4DVAERG5OB7JIPKFQNCLAM62OX234GM4RMC, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GDPRXXL4YBF3FMJG5XVHZLO7BWUJJGI5OCS43SBXFU2WNSDGPRNWHMCH, which is not in the allowlist
counterpartycounterparty_denied
GDPRXXL4YBF3FMJG5XVHZLO7BWUJJGI5OCS43SBXFU2WNSDGPRNWHMCH 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
- 40e84fdcf3a5d0d3e084bc9f8f6ab2ae2024a9e24635e1086b9bf46c7101b19d
- request
- 731d5cbc5ead17270f1300d86fddefa30981d03ef42bb51b846f400d13b0be57
- transaction
- 4b33e4aabae293d84fa58809f060ae56e0b407aa796ce8a87e90e6104238bd66computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70880
the chainentry 70880
- sealed to the entry before
- f7e7e9a44ae14b9d7846aa3bcf974ddbdd0205881f95ea240a9732d2b1cf6a71
- this leaf
- b8bb8bb60503fe1a8f4b8b20cc3031f588a243453ca4ab4f4d341694a370d32f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ac2oyAKebLF/2fU2u9nm3uwV+OFHavV3cspRcgqSPpJAkbdZeyZH2H1rR6/Wf2Ql11OaCcP/T2PvzLSvXWSjCA==