why3 reasons
realitydelegated_fee_payer
fees are paid by GB2XEZSMO7BHRXUOTXB6PFRPLDQZSHZGIJ2AT37OONJHIGNS7NCMD6EM, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GD4KJVGTSGWO7LEE3FHNYPLR4JLITPOGYS72YGA3NO6YYGGBXUQL2MXC, which is not in the allowlist
counterpartycounterparty_denied
GD4KJVGTSGWO7LEE3FHNYPLR4JLITPOGYS72YGA3NO6YYGGBXUQL2MXC 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
- 999c42d37c500d7caac983b780136675b9627efdcd949eaeedeca9a18b65ee5a
- request
- 89e91da6d9de0ff269d2fd1f780d4e9de14fb05a30616ba06a79d78e729a485a
- transaction
- 48af6f6c20c5ac0471d33be1937c70e9fb9ee2350a6e2015a50c00153f473cd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28400
the chainentry 28400
- sealed to the entry before
- 770cbd309542243af25cc44fadda89819071da58f96d4b492c1abec949c5ed10
- this leaf
- d2f60bfc3f7805834e9601b2716aca86a106d427bb82b19a7b8665f8726aa01a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4iWCPjShoh7W4xmQSZib3FlAEymoNo/RtVKFH0RhZaaiXs1kTQwiV5Wjm2szTsUi767BfWy7YQrwKpAO/G4uAw==