why2 reasons
mandatedestination_not_allowed
op 0 pays GDPJVAMUQLL55FSRIKAWTXXC4V4ALPCXRWJXNJLLMW45H4QDTY6L2OZ2, which is not in the allowlist
counterpartycounterparty_denied
GDPJVAMUQLL55FSRIKAWTXXC4V4ALPCXRWJXNJLLMW45H4QDTY6L2OZ2 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
- 2b12edf02e4985378d3895b3d7c88332c0fd4b7516b450ba92e7fdaf64b924d3
- request
- 9460295302ce7cbf0a47f29e1823e985bc756e4c0e94f4e03ff80ee627c73915
- transaction
- 452d7c2bb9630d5bdd96c2fabbfe0eb6ed0fc8278780bd2c695e1603191547c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44177
the chainentry 44177
- sealed to the entry before
- ae0fbc25c272e28390fcc8ae9a125a60188f8192f4974b50ebd26a95f9ba8f64
- this leaf
- ec237af000729bf712c68d52fe885b0d5ba68dff1d4837851f9e8cdeb65bd805
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o6tXbpNV+Dw4K0MH1THN5tJdZOT8yR9HM8y2J2oKJsV1MXiR33SkloQyTKLVvdD4XP7CmlrGdCpgRF3gmas0Cg==