why2 reasons
mandatedestination_not_allowed
op 0 pays GBVEMJXEPCVQLSMMWWT7RN4H7OSHVODZDWA3WBJUJLQDCXVX5IOHX6XO, which is not in the allowlist
counterpartycounterparty_denied
GBVEMJXEPCVQLSMMWWT7RN4H7OSHVODZDWA3WBJUJLQDCXVX5IOHX6XO 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
- b76d13e1b87fdea1aef208741192a7ffce881f26912c40a27cde700b37499fab
- request
- 152f6fe4d229399f7db51d880b5d98de6d12489a9a0d89df8c83fb7dc035cee2
- transaction
- 8bc645cf413ef997d1e1ebe8266f0d8cf8b1d47a241ed284259d5f7cbc4baab8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68977
the chainentry 68977
- sealed to the entry before
- 0aa228a36c3f2a75ac88d45f208ffb59251f192167829547a21c1d8ff908a475
- this leaf
- 7fdfa7f2941c4e183a049648737df5bd8fe17c11f95585477c649e430b01da22
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tscbRcY0Tj+SmaavZg8UI8ROYYwuaQ9uuRL+zjavZuuLxvIoIoFiESljqSn3shNqkSDeuySbIUmVh12cq0eWDg==