why3 reasons
realitydelegated_fee_payer
fees are paid by GDG7BMO7D2RJL3UZ35SLKNOEV64MQOEZBVHQKJPCZ7ULBQIGSN2OK5Y2, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GDTEAFGRT2XFE35WCWYKOSX366RFUZNQ4VRHXS5UDJFIU6OGEFJI4X5F, which is not in the allowlist
counterpartycounterparty_denied
GDTEAFGRT2XFE35WCWYKOSX366RFUZNQ4VRHXS5UDJFIU6OGEFJI4X5F 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
- 490aea6fbe3f746884a31193d25df2495394ed439161e746b458100e39023884
- request
- ae3d4b1ec251895909b4a4b95d77f5bbab479a58e5301fc82a6d8be9c51a0083
- transaction
- 5712552895ce7c8022ae0194c8b23077ce3fa0eb8b68971208df37abfba94787computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53888
the chainentry 53888
- sealed to the entry before
- 69b1c261cc1c520352d67223b95225e965502dee5ff60886f66c3661ad203fcb
- this leaf
- 236543afdee3fa7b4048ebca6c9547b9f3135568e2bbf8da4db0fe4af885aa5e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d7aQFaCcXgw0/0rwdr7hN6sgpSILu6enMoz2rPCB4exOrY3UBhtB4wXuK22Ewnx1Gzfctk+1XGL0Fc+dcCcpDQ==