why2 reasons
mandatedestination_not_allowed
op 0 pays GCVFCNMCL2MMURN5D4DE7TICSYH7RLW5YVWIUFNGMHHRLBRQKKGDBO2G, which is not in the allowlist
counterpartycounterparty_denied
GCVFCNMCL2MMURN5D4DE7TICSYH7RLW5YVWIUFNGMHHRLBRQKKGDBO2G 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
- 8f373996569defab2c97fb469d068bbb39d1821b3d5bee7d869d461c4c43d3be
- request
- 882fd7970553a272f8bc15978b6c6f42229589192bd4984269016dbf091dee16
- transaction
- b71f39051c44b4229afe79085b96fc5a95b02accb5f89871081c9686b945a316computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1736
the chainentry 1736
- sealed to the entry before
- 98beb52d3d4b0d9dd45b5f548a70f0af93d3b21a47bcaf63f661b6c52d240564
- this leaf
- 7895e5ea71f535f68fe06f99e689822c373bda763d61ac2108d4a3befe2b3167
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AYfheDHkXQKAKFOKKbQ75PLezzHehK6Fras4YB6sjaCeOxUCwefYiX3jnBLvkjTHARIIeaTMUsieJtBwkxR0CQ==