why3 reasons
realitydelegated_fee_payer
fees are paid by GDZQY72B4ODUCIKNMOBC42354YTZYFX3CJKJGHBR6RDZFNGD476UNI5E, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GD5UDJQQOJHOFMJIVCKCWZ7QJ6V7YNJMUYR4S57G4MZIFYGFZE2FRDBT, which is not in the allowlist
counterpartycounterparty_denied
GD5UDJQQOJHOFMJIVCKCWZ7QJ6V7YNJMUYR4S57G4MZIFYGFZE2FRDBT 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
- 2c4d69fe89ad313595b6262a032a79c83063bb953decd10a829a28a201b09b00
- request
- 0b6aa6b9c5a349f50a101dc20733ef0448210009d6cee68adae56f30a5bf0512
- transaction
- d56ea6e8408790b039e523e5213e44aca6a5bbcc094212e59f853e1565f48ceacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63652
the chainentry 63652
- sealed to the entry before
- e4762be09a51c4d6d996d93834bc183d921910c4b158550d5171dda6fb51df19
- this leaf
- bf48e2b3501b074a84658e5cf785c100751cabcdeb5c90fe70f3507bff58c3f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XH5vXKOf5f5pqYD/ZZqiFRwmdUVOFrYkU6w1iMFsuyivrZw0L41YZQZmxHJ2SmoOEEbNnm90F+3xxoi4R4bHBA==