why3 reasons
realitydelegated_fee_payer
fees are paid by GA2PVRUXWVADAYOSHCPYPXCXQKYGTBMRRL6ONY63WLWHXAZVVIG2UJV5, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GDPTMXVEVXS5QA3BVM6D3Z5M2C36QOAAFGG6HEX65WA5TMU6RMYLVSUX, which is not in the allowlist
counterpartycounterparty_denied
GDPTMXVEVXS5QA3BVM6D3Z5M2C36QOAAFGG6HEX65WA5TMU6RMYLVSUX 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
- 896c7bfb90bad78d6b3ed46fd45276965699cd16fd2fd1e3e6d075a8c986ea05
- request
- 127f9381492a0fcecea6430832879b16496bea17dbbdd6d187e099af1d6f5d39
- transaction
- 654a976763f6caa75690e9939e1e7247e1ed1a60ee38d82b85b4a9b1e6636f5fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73402
the chainentry 73402
- sealed to the entry before
- d484d3f132b50f4bea08ddb93330511fc6071f9737ca5dd20b571e115e22200b
- this leaf
- d46a7aec72f19d37f424f0db861fb69a3a3adb280d1e3153485b332c315c632f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BsAd81vkGozeXvH3ho7YE5a496c4yyzekobcIdpkqgpSWC9PZ3Z0x7olpeBXdvgE4mjskgm2wfZ2BdVviSz5Aw==