why2 reasons
mandatedestination_not_allowed
op 0 pays GB5QXSPHL6M35EYLHVMQM35YQEKKCWZKWNLLUIBMQY7U7UKRYDL5REH6, which is not in the allowlist
counterpartycounterparty_denied
GB5QXSPHL6M35EYLHVMQM35YQEKKCWZKWNLLUIBMQY7U7UKRYDL5REH6 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
- a842eaac10a7e36a41eabf8ba6754bbf7664fc693a7993f270b33786c04aa981
- request
- a454c4dd7defd842163a415758811b880a372596e3d9a58f57d7e704cbef2533
- transaction
- b58abf40c0519c380156e36fed1476529384298dc512504a37db70fbe3e0199fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52219
the chainentry 52219
- sealed to the entry before
- 87345eb95f78a30b38e6c776946fcccdc3f46be91c007a6889186103f6da5d7b
- this leaf
- 0617d7407f7c83b0c939350ec0de75756fd48afae577b49ca160d7bd253bc480
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QVh8HR6n2eA1QcR50qhT4UzGZc1P822C5OPkh+j84x3AhH893z4zhe/TrdFLu6a5BgEJynnIwyEE3SBpi8TAAA==