why2 reasons
mandatedestination_not_allowed
op 0 pays GBNLQXCB3M5O5S4WLFGFXI6BSCWWQ6LNXASCGILW3WA6KPORCSMVLZM3, which is not in the allowlist
counterpartycounterparty_denied
GBNLQXCB3M5O5S4WLFGFXI6BSCWWQ6LNXASCGILW3WA6KPORCSMVLZM3 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
- 2c2721e0cb5d565333b8c44f6215c93173a7444234565547874da755636b8dbc
- request
- 702b13ce8b5b78c8f921473411ff8e9911d6d621737be6c86dbe73ddb268b07e
- transaction
- 5fb210235ae3d7e4fbab6f318e7e82f3946b3c932467961bc78045f181b20a48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42615
the chainentry 42615
- sealed to the entry before
- 1a3b55814e733bfa1497c0cc13eebff47aa8d55ab18e9e4acdb55ddeacbbbf18
- this leaf
- d46ea1949b6c574c7c0e64267aba12c2b36f5a985efc49f1f3c80562380d2e90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yh7xy1VrYOAFSNa9B3yMUpTCSf0dVcrmwFoDiBwB98uljWfdNA2OvTwwEQEox/W3C6DBbItSND5GEaVIEj15BA==