why3 reasons
realitydelegated_fee_payer
fees are paid by GDZUXVK2E6SOWOVAEBDE43GBAROJOXLC5YOYMJYYBMTERHPUZ5IHM5KW, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GD3XORO6MO2KD2E2IT5FROS5F7PXWFIBZRXMRZ2LNJXV4EBENGRDIZ4S, which is not in the allowlist
counterpartycounterparty_denied
GD3XORO6MO2KD2E2IT5FROS5F7PXWFIBZRXMRZ2LNJXV4EBENGRDIZ4S 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
- 9788c47783f23e9ba3548870386ea5c445760973f827ab901bc90a974acf29d3
- request
- aee171a72531ea3beddccae749ce07c0d83f583cd786ddaa071564f8656ec5cb
- transaction
- 634555d2236cbfd188323eed4c7c51fe43d52d506f0531bd662ad9bdba7698facomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17048
the chainentry 17048
- sealed to the entry before
- bdd67b847063638facba29b9afa18275eadd9fc8cf74fcc38318fd1ee02c5f54
- this leaf
- 243372d245adb78d725f2cee746177baf4324111019bbedc279e91cd2ae4129c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 84Bw99OzlX0dvV5BfiXVMQI0aPp1FwOL6ZMeQSOrFgBUvrTDlyPnQrxKq7N66ueQEL16am7m6n8F/oo+E6iKBQ==