why2 reasons
mandatedestination_not_allowed
op 0 pays GD2S25O5SZFQ23LUUCDFDCIWIGWXEGN5AZ2BXZOSALFOUFW7FYYA5DDX, which is not in the allowlist
counterpartycounterparty_denied
GD2S25O5SZFQ23LUUCDFDCIWIGWXEGN5AZ2BXZOSALFOUFW7FYYA5DDX 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
- b79c6db1ec892f6610f1b979b2729134c3f389feba8a0e52e8470678063e0d1b
- request
- 807426e2cad8d167b766930c42130fb5e1d1baa33537325e46e0823f2b30554a
- transaction
- 0f1e7f4eea8cb4a1aabf6ac8074e659123d1b7fa4bd84a67d169865dabdc8444computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57818
the chainentry 57818
- sealed to the entry before
- 1d312008319e678a501ae6a44311672b5fd89324886625f767767e56f73759bc
- this leaf
- e2ac331164e853d657dad37ed5930a40a6ace19bac972a6879da3711a94326f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lpThtx/Xu57bjb3NY1OZDQChmrhv4Diz2r51qhQWeyzxfa6kFPHvF4tZmugUghYrR8XRLCKkmS00dyXChZkaDg==