why2 reasons
mandatedestination_not_allowed
op 0 pays GDZVOGARUUC536MRUQCWV5D4FCYBAZMRBMBOVXVOE6P3R6UJHWPC4CEH, which is not in the allowlist
counterpartycounterparty_denied
GDZVOGARUUC536MRUQCWV5D4FCYBAZMRBMBOVXVOE6P3R6UJHWPC4CEH 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
- ec8f9499dfef29e0d2ab691fe5d93f160be9d5e22963d5a9b8f061bfe7a5f6a3
- request
- c27d5422b830a2a7a0a7d3930b7e069b482b3ef312d718d749ce07abc06f11e4
- transaction
- 26cb4d47afd4cae08d7d3a42e1bb11c412d9d53c44d46f682aaa4207bab33150computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2076
the chainentry 2076
- sealed to the entry before
- 3f41f0586cecfebab06f2a00502359c82964c3f691fff2d4f07fdf261822095e
- this leaf
- dc3113f1724ee946108c5af48fbb83fc82582a92032d27ef1f218b6bf31ed88b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SjSOx4xjwLCStHM2q00ubyttBaWcmlJr8S1/XF3N/Luc3DUf7npS4f6To+F+1LFUapw7ohcTdjAvkpUJ9i20DA==