why2 reasons
mandatedestination_not_allowed
op 0 pays GB5WG3YSOICNLHTXRXAJEULB3VV2DD3VTZ4PTDWJGN7GLQ6B2LRQ6C2T, which is not in the allowlist
counterpartycounterparty_denied
GB5WG3YSOICNLHTXRXAJEULB3VV2DD3VTZ4PTDWJGN7GLQ6B2LRQ6C2T 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
- cc6234931ebafa30db2c9af15c2d71e382d8d5498fe5fe46f878c05a3f55a61b
- request
- 4911852aeafff5afced900da696a43983f728b79e3351826b1a24b3fe60a3c3f
- transaction
- 9d1ca4266663274ded6f856ace5dee58040361fc9dc1f6b96e538c5aa4c216b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60054
the chainentry 60054
- sealed to the entry before
- aad3082eaa3e9ad0d1050820f5fdbf22fc50e4f3fd5f14ac03e9719e85cb2938
- this leaf
- f14091419ce59a22718d7a25d0ab75fa5896cc754381115fa34291afb3ebecdd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yl0xqy0Z+8i/3umzJYREJVHNkcd8ltDd3sHyJVOJIRgE5Eenz1oVpUFLklxCQ48HJq0jI4I3ge5WsHfbJPdPAw==