why3 reasons
realitydelegated_fee_payer
fees are paid by GCHZUXAYPQJ2AUP23LPUHHWZJRJIMVMX3OP5DL3K634752KOWMIZONI2, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GBFNNMFN4CVPWBOTPTGC6OZSN2LQC7LBTOKS6N5SMNFDC3J3HJL6NV6F, which is not in the allowlist
counterpartycounterparty_denied
GBFNNMFN4CVPWBOTPTGC6OZSN2LQC7LBTOKS6N5SMNFDC3J3HJL6NV6F 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
- de4f5d5285f6f7f3446ffb1935695b846db363fe7160307f5fd6a30b48329a5d
- request
- b2af8c2c9f401897cdbfe86120ca3248e6597c35f60bf51a1dcf55b60773a119
- transaction
- 3999d699e78dcb8c42898a7e79dd5a393d4767f3f094370e6b225be2be2df7dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28944
the chainentry 28944
- sealed to the entry before
- e8e7c0da3e2f130f616b4018e1e26d56a2e996c8ae5ac1bae977f1b2e45423b5
- this leaf
- 403d1ca75c4ca1f0ad3e30c3c1f9432fe900314585659c65d19797eb35efb621
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ybzUP5XQmhsW23AgHnY+gG1mHKpfZNULZeKmmriTBsibeJl1Zd8deseN5NRQlwmK08FS+zZTAHN6I0kEk+IcCg==