why3 reasons
realitydelegated_fee_payer
fees are paid by GBWKE6S3YAUJIJRAQZXR44C6FNKLVKQMDPZQ2UGUZF3M5PN4AZIRBD5R, an account the mandate never named
mandatedestination_not_allowed
op 0 pays GD632JUU7ZH4ZJKX2EJZUKTYD4JKTRJNL5VKWXDOINEBLRXXV4YTT4NS, which is not in the allowlist
counterpartycounterparty_denied
GD632JUU7ZH4ZJKX2EJZUKTYD4JKTRJNL5VKWXDOINEBLRXXV4YTT4NS 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
- d7c8dc91cc3698dcbfe9928b91a9da3dfffdc957ff227e04dbb7290681bd6370
- request
- 457c0f980fd361714979aa9643532ed67a3d3eb97ffe5aabaee8bcb0a532c2c1
- transaction
- 8c0dc6cc0307b48d7487bd3aa806ed0795302f265aadc4f03fe0acf31e835a12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61860
the chainentry 61860
- sealed to the entry before
- b4e3c1fa32de80deba87d4071e926fab981d07bfc2fac5bc65465bb1a34ed5ad
- this leaf
- cc6fb845512acdd3e9687a4b2c90bbeb34e60c1857db077f6ed548a0974c4097
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mHZKViE3QyTDW2NxFddEp8GzUbes4Jg0k6WSs3YndJq3CDVUF94x66heB9eopviDFK6JqtQR7gd0h6CSi0WaDA==