why2 reasons
mandatedestination_not_allowed
op 0 pays GBNSBNZ6UZYDLI4WASHI5HH2UEU2E6QA4UBYJQPRI5Y7DDW6VQTWMNRG, which is not in the allowlist
counterpartycounterparty_denied
GBNSBNZ6UZYDLI4WASHI5HH2UEU2E6QA4UBYJQPRI5Y7DDW6VQTWMNRG 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
- f630714a531a649ca6a83c58b5eb0df835955d4cb244d8495a696d77bd8fe243
- request
- b3724806501d79a13495171563016bee0ac45a7c2b0d518c77801f9aec175534
- transaction
- 4635fda31e0a8e2e10d64f0b56a18c42b1491a8d36fef0411f0c1abf2a6850a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1133
the chainentry 1133
- sealed to the entry before
- 8ef2eb992a998bf6c841556af69ffc14e11afa5c176a3624b79a07afefacf2da
- this leaf
- 8ba5e0237de3005dbf28d9a51f824d42574d43912c130a00cb2381ccb74e9520
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jtRC9WaZK668pA4pfbzEeL6+agoUm1NG6SN0oZ121jhrIWmHY635ibBm8yILNYsyPDhT4lvNjXI0e3SlS9wsCQ==