why2 reasons
mandatedestination_not_allowed
op 0 pays GD6325WHOYDM2CKETXKUKYKB3OE5OG7UOHADIOLQW55ZQEYNW3EG6Z5O, which is not in the allowlist
counterpartycounterparty_denied
GD6325WHOYDM2CKETXKUKYKB3OE5OG7UOHADIOLQW55ZQEYNW3EG6Z5O 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
- 5f4378019326c1b5de5bd9dc247390bb2ec4c3c798ac2fb4033665927682811b
- request
- 8bc5b945f2ba0ed459d4692e241db55fdd496862386d98d7dffddd904651dfd7
- transaction
- 24a35adb5be7eaac005ce99dd8d5cbab3253279cfac44f04cb93cbcdb610bca4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26290
the chainentry 26290
- sealed to the entry before
- 692cfb3d76b765ea06d8f88915f8c2bc6cdbe56c9ea92e3e8c1cb3b56ce380c6
- this leaf
- b5fad33524a2d6854db035f9f57bdba9aa6ebdcceb73de3d411dac5280e69b2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ny+v9mn24kRwIvEbz1jlvpTAYumfzTXBDuSLyDFqGykIDIwXKzRFIOcP37YoHtRPWsIPOsjL1uZc5qVeifLTCg==