why3 reasons
realitydelegated_fee_payer
fees are paid by GDDI522IS3RISDC2VU4EKW3C64TZOPILO5AJQ5JRGY7Z25DX5BYOPTAG, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GD5YKIT6NK5Q3AM3YTJYBTT7GO5J76CE4YXDDUYAZ7623Q7NQIWD2QNG, which is not in the allowlist
counterpartycounterparty_denied
GD5YKIT6NK5Q3AM3YTJYBTT7GO5J76CE4YXDDUYAZ7623Q7NQIWD2QNG 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
- f45de435eb46664df10a0a3b88075f7334c99ded5019207d6f0b38386080fd34
- request
- 8eee9024fabec1a3458009754cf0f45e8b7709eb24a102906f329fe143c0f62f
- transaction
- 18e4991a0779cde64042302daa39dc41b22da32dee940f34f03b8a4ff1e6c4d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75731
the chainentry 75731
- sealed to the entry before
- d055cb346feb581782a464ba4e1d977f479b510a2c447ea63204033d99ac97bd
- this leaf
- 44d446cb00d37131c87a06debbbf1770c90247e45de474cbe20e8d4c68720b96
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ioWWR3svC9oXJpkn8A1lfgNqaSovo27JYoFegvhZX8rJmVSeoKGIrC0WsyaZ+cQLYYoAxm7CKgRC0W8IZZvODw==