why2 reasons
mandatedestination_not_allowed
op 0 pays GB5UEYAZZAF6GYAH5TZFWPPZJCC55B7MVWEHGACEIGVZDBKJ73Q33TYM, which is not in the allowlist
counterpartycounterparty_denied
GB5UEYAZZAF6GYAH5TZFWPPZJCC55B7MVWEHGACEIGVZDBKJ73Q33TYM 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
- 3b0f4f6dc911bd48e7b1957a2bd5e03f20a70c881b96590d9b8f36095bba2574
- request
- 3f9ea82c02e72f738e7092cf3801340dd760cd50385d756d6c08ec910864baf0
- transaction
- a8210404714fd4355bb67398cd40bcc4bd36b386a784b7c9d0fc108da54d4b29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 607
the chainentry 607
- sealed to the entry before
- 3d0756166b1486c7c4db12451369976ccfa213c03d733c1c08cc00c9f6b8aecd
- this leaf
- 00ba07f54ffe7b2b1f2da07322136b6cf320075783940b8754a92ac0a78b09b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pp3ULvAb//EudmrFsJIrGKZL7sCvXbRQcYfZvBW5iVTJ0cQxStGkDhMC6F3Phi8iGSQkExNmU4X+hRWUCe9mDw==