why2 reasons
mandatedestination_not_allowed
op 0 pays GBYCCNOWNQV2PRMNONTLDJDWCCHEYP6EVJLJPZRRXBIOI5KQLUNKKQB7, which is not in the allowlist
counterpartycounterparty_denied
GBYCCNOWNQV2PRMNONTLDJDWCCHEYP6EVJLJPZRRXBIOI5KQLUNKKQB7 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
- dd20ccad81e85b6429b77c592c3dcabb0b2856c2e255a0f6f68a0f3c6363e9a1
- request
- 56288818c55dc5df06e7de2be9e0fa1aeaf51ce33895ca3be744773f051bb5d3
- transaction
- a9833d6aae02e0744ccab4dcb69ba132a65d2a0f9a10e6eba23f4b3fe8bc4728computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31018
the chainentry 31018
- sealed to the entry before
- ee8c2d01affe31d9cb4632de022164c864a87eff94f2779e490fe76f2761bfed
- this leaf
- ae806e8e41b5492fa133521112844a849cf669218039446b565ceed9a216bfc0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jTLp/NuDfp1BauetDzabF4CDgn2gmmY4/J4JyVOHDreAQIlzTXUJzS1DJ4ArlYeum/D41sytX1NzPEP39771BQ==