why2 reasons
mandatedestination_not_allowed
op 0 pays GBB5ENV4DGXCS2FFGYFE7IPMYKREH33OXXRDOFWFXPJSK5UNSCZEC253, which is not in the allowlist
counterpartycounterparty_denied
GBB5ENV4DGXCS2FFGYFE7IPMYKREH33OXXRDOFWFXPJSK5UNSCZEC253 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
- 0b90bcf3271bdb88ed1706f8e9e3367914638f4c0aa07fd6b8133e9c0ec448e1
- request
- cdf1602289f5308decd405ec012948c8e427b298011be0f8ba3ca96adfba2f7c
- transaction
- f7b9ac5228d7e84cfbb98e3df17c3316438ad4a5b704ca88419a98a6746aa039computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14774
the chainentry 14774
- sealed to the entry before
- 6a0a2f1fe75880b3125c6ad8c7f8329cbebc04e2d243b83c3e22ec37a54f3aa8
- this leaf
- 51e868064a6df02501f1b2a2025aa29649ad91a419f951986c200b364e52adea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ujWvLK5ecbmvNS6GSHvx+BTgLWSbx/aZ+sFba3LYsGPMo0d/IJr8Y+1/7Q930AQjKS8jc1SY5oR1b9LJWmMnCg==