why2 reasons
mandatedestination_not_allowed
op 0 pays GCJN7L64QGX6JY5IHHF4KYXY67MVJR4S46E35IDLK6JQEF5F3BTVK6Q2, which is not in the allowlist
counterpartycounterparty_denied
GCJN7L64QGX6JY5IHHF4KYXY67MVJR4S46E35IDLK6JQEF5F3BTVK6Q2 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
- 4d1a36d5a1cad5a8fb9161c231d5dd8643d33f996a73effac54b481310be7574
- request
- 82188e45ca069a35b3af3d463e78684e69be05006251ce78d881c0bb993735b5
- transaction
- d4e025ced3e79b2d36a18424118bb7e535b22c4b7285b68d9be33ccf791686c2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65209
the chainentry 65209
- sealed to the entry before
- 6da4d9110b588281b129dc4fec1336477dfb07593732e7576dda7708d7b14454
- this leaf
- b059431399c8ba50638254877d5a0e905c5e2bcf785d1ac69bb75fbe9ed00261
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NE609MqbgYC9pAoIv40lmNDdFK4610tPV5cnouwFa+ejHKefmYD0PJmtxHG4fwtRd7uxuFBllhdo8ib/EJWHBw==