why2 reasons
mandatedestination_not_allowed
op 0 pays GB465GVCUISQSE7C6LMBT6D56K7EVE45HK4WZ3TUGZ5YJFYGHGJGEUH3, which is not in the allowlist
counterpartycounterparty_denied
GB465GVCUISQSE7C6LMBT6D56K7EVE45HK4WZ3TUGZ5YJFYGHGJGEUH3 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
- b9df6988746e9aab9f9b3428596c4eff2c0ac5418587b281cdfea45243357612
- request
- a84f67b41821160f1c02d42312be4caea38ef449b9c6183d9a2acf56396d1065
- transaction
- 79e7d8c25c098461bdcc2e93d0b0ff6e79c894fdeaee985a07fd690a228d48c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54675
the chainentry 54675
- sealed to the entry before
- d10a0bc827806644d3c4d866b8d662bb95257101e91a07fd7a8760435c7fd144
- this leaf
- ed83d4f67b793b726e758e75b5d7d9330edcfca855d85c9a99338bccc5e5573e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9AMmJ90CGq9UYaWv4UGVRuzHsKPmNKNtz5Zol2QbI0tybtO+LhNuuZGyaFFq1iudpD1c3gfZhPvbomKY4TwuAw==