why2 reasons
mandatedestination_not_allowed
op 0 pays GDVRHSMSOPJRFPWBMLK3S2GTTVKTNYPETW2C35A5VGMLWEC3CSBBHNV6, which is not in the allowlist
counterpartycounterparty_denied
GDVRHSMSOPJRFPWBMLK3S2GTTVKTNYPETW2C35A5VGMLWEC3CSBBHNV6 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
- 4227e2ea94bbf0ad01c0a7cfbf3ac50a0e61e7af965e11cdbdbdfffa1c29be40
- request
- bc9e345fe05fa337819f0bb2ebaf10adf531bd5c9fbe0548ca53d8ce7bf10206
- transaction
- 5d51ebcc13786135c79edb4f972452b75a7ff5c3d8504d704e40732082a2ea64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19962
the chainentry 19962
- sealed to the entry before
- c3e847eca49994ead9c9697763771f158129e99cb7834802ac1d17f060765b60
- this leaf
- 5256392e8f289f6ca9d496b2a343527b3dbe4299ee53a50cb15c1ac03b17f552
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hV4uAVWSaITxXBO3ZDwwP0geOkHsE3O+y9vFj0OGuh1l0ptfSTPMAPI7bxeMivfPd4PwWmti0jOtv8U3zbbpAw==