why3 reasons
realitydelegated_fee_payer
fees are paid by GDN4XURKGCSAJEWR5GOHSHFIZH7Y7J72XYJ7USD3BNX7CCVH5D7EPCW4, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GDQGN6I7WO4OVDG4SYLZTKL6BQDTGYPICSRWVSBF2RKEP4Z4OQD4CODD, which is not in the allowlist
counterpartycounterparty_denied
GDQGN6I7WO4OVDG4SYLZTKL6BQDTGYPICSRWVSBF2RKEP4Z4OQD4CODD 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
- 180fcc81b21699cb3b0baf211402f50d7451b8f5086a4f0ab916cfc18c873401
- request
- e26f16fe59e5faec3160ba0ad5e96c23793a5bcd2f97c41b273173d8bc365084
- transaction
- 51d59b3b21842d819551b6adfa1346673d936c5aa97b541369de127ba6ee143ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39665
the chainentry 39665
- sealed to the entry before
- e660ec969429b6b83dd4c26a7641304cad78b824274699fcef39f6078b4ad655
- this leaf
- fab2b5b39eefe6d0e1a79155c1eccb72133ef19fdefebf848eb18e72a018cc74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OXLeIVJ9KsAmqwHYaqluQjnzEh9MhPtzWOWay1s63DeiqIK50hgbMu5dV9gVABq3sIQpErhdPaM8DpTTWSWyBQ==