why2 reasons
mandatedestination_not_allowed
op 0 pays GB3MZAONIHO7TN2MJOFSV566OK5KDUBO6VNYTREUZLSZ4BRAWYNB3S7Q, which is not in the allowlist
counterpartycounterparty_denied
GB3MZAONIHO7TN2MJOFSV566OK5KDUBO6VNYTREUZLSZ4BRAWYNB3S7Q 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
- 9ba713f1dc9e54a83dac6fea485eb09ea2caeb615a3a0ad6a81cf1a141f0a74a
- request
- 40c7f38d96a5fc3c054808d08d2d003c7a19f43a21c059d88e1f77c1a1f82520
- transaction
- 708c45ecc77b8f7d7a9047b2eca9ed7750855591c1f79490f8c951079fef509fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21844
the chainentry 21844
- sealed to the entry before
- 22760dfd0823837fdad7bc6f3c7cf0a6a405075c690ec474ffabb4fe8616069d
- this leaf
- c7e185b77093964b9a74bacbdd9bac4b0f36637f719238a28bb81a32987cc3cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4086qMqede1GxRNE4p9uTChcbtm6iqFBvNA122JPOeC1otaiGIwBxr9mnMMDvfgaf7E4pRh6+vwjh0N1sEo+Bg==