why2 reasons
mandatedestination_not_allowed
op 0 pays GB7ANPIP7XJXZYEE353NKCAJ3UW4F3AKALZYG5FPBBO7SYOOITBWXF7C, which is not in the allowlist
counterpartycounterparty_denied
GB7ANPIP7XJXZYEE353NKCAJ3UW4F3AKALZYG5FPBBO7SYOOITBWXF7C 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
- 2ff5e15b3b43fe1eebf6fbae8b446d3b8955c7c99a6ed4780bf0af62939bf7fb
- request
- 2094dfc9adae653aaab2aa5a0f151bc74de37f097777133edfb85bab66ba0ae0
- transaction
- 08a394795834dee932ed4dce42af0fd8c54365c28c9b7a5e9c43e9aba2210be1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1079
the chainentry 1079
- sealed to the entry before
- 53620cc3fdecaba74dda700fda60f42a7c63c76e1c6922813ebed9e6e2e3b5df
- this leaf
- e32d6816f29703c51ad71f49fa02ec1f30e750bec7d9d3ca135379df1c7e798e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fGrYIdPXDg769aqeckQtDBfpGovxtNFJtREDg84qJaRiv0zCc61TVt5m/CYtWkxeCm/rKcIbn8kvyr4I2IscDQ==