why3 reasons
realitydelegated_fee_payer
fees are paid by GDLKUF6N4EJLE2TR4FSPQRBL4AMTF4OLM2AGAHTPSF2KUK6KXJLOYIQZ, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GBMUHK33XEOBVFFGY4YDE3E5QEXQM5AOGF6AK7KHPAFJQZZUNCO6MRZ3, which is not in the allowlist
counterpartycounterparty_denied
GBMUHK33XEOBVFFGY4YDE3E5QEXQM5AOGF6AK7KHPAFJQZZUNCO6MRZ3 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
- f7f2c965b4344b0287df539e5864412c1d555382f1330f429a9142c961b2bc4f
- request
- 0466b21aa6c3343190ffba86f7ea0edce3ca8f211b434e1f451524a8942f05b8
- transaction
- 7a89990c054dedc08c0850c1370ee1cee5844e5684d6bc784a87c9d3a27c0ec9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33654
the chainentry 33654
- sealed to the entry before
- 305fbc0af8d98378cbc6ba311a24342cf69d56e9e733e99266efade8203176a5
- this leaf
- 6bb9ef6220788fb56028e807930eab8508ea748fc6e76344bf65dbb85dd081d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jvkkSg3G1HRdzv2lx2VGleWILIue6OjChBGmOcKd6wxrA/NwSMZtXeBru+zgm2fZyl0wsoDWidfRBHRaMPdeCA==