why2 reasons
mandatedestination_not_allowed
op 0 pays GA6Z723HASP3NBTR5SAI67JF3TEWQSDDYWVEF36J6U5IPGWDGQ2ILAF3, which is not in the allowlist
counterpartycounterparty_denied
GA6Z723HASP3NBTR5SAI67JF3TEWQSDDYWVEF36J6U5IPGWDGQ2ILAF3 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
- d9649e3c0a237396c76ea34990ce1fbecedccc08c7bcb9a753d063027250c2bc
- request
- 173ef12aa5b8b2270a2c2fbf975f00c96e5f97fe2c94efa02d2ab96db553caa9
- transaction
- 3de35c35688d20a5c86b9705a627f83a9667528e9ea80ce6fcf5317c6ea225a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1801
the chainentry 1801
- sealed to the entry before
- 4d292ddb4e8a6298096291e824cd4e59fe3caa1134eb63cd1243c8f3c93a012c
- this leaf
- d741c0768ebaa84a6feacf46cd83041d6f40f40d362df1771bc56984e586dc79
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RSPddskbLGJJfBludOYEJhLjNPTteghrV5tN5cgcKujN82dg0qOHTyueyHjRsPsh39z+eCPaQki/lIKnFc8aCQ==