why2 reasons
mandatedestination_not_allowed
op 0 pays GB5CQRPMOCV2EPJ2ISLIHBZP4MA7MWSRLHCS5ND2FQNIQ5QMKF4FG4D5, which is not in the allowlist
counterpartycounterparty_denied
GB5CQRPMOCV2EPJ2ISLIHBZP4MA7MWSRLHCS5ND2FQNIQ5QMKF4FG4D5 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
- 131b9652e0f3cb443d52108a2a3b468b6b9841ae03e5b93951e4cfbbd1c0e1af
- request
- 809ff35d35ba3ed062f0085094675d2bdced52b0eb8a571fefe93247076d59c6
- transaction
- a59cba1c8ba695ad0581fcb0a09b312ce9d14e7c8bd19fa913e603802368562dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13523
the chainentry 13523
- sealed to the entry before
- 36e99c3d96994a4c9c562d630b21713ddf76fe620718bfbc34cd822ca00e53a7
- this leaf
- 11e815d783069906e57de043cca51f8a15b3ce9b26ee749934415be4cc444c4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OXNasMn/f/AYG3fKIGHm3ner6rttNmAZCaMEShmqTYCadZYd9Os7Vsp422u61vr/EZQ9I+ppKwEx2O0YRsJnDg==