why2 reasons
mandatedestination_not_allowed
op 0 pays GB5JRKAZAKTR6UC5RBUXELVOPIFU6M5GJO7KDO63NDYI5QAQAT3323KT, which is not in the allowlist
counterpartycounterparty_denied
GB5JRKAZAKTR6UC5RBUXELVOPIFU6M5GJO7KDO63NDYI5QAQAT3323KT 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
- 1ee0a8f12e8af8b60e23881e820803ed0aa80d5a191a952afc03d9f77c4f1388
- request
- b236c0316aca9724b0d3cc04bd589cc2a712adcbce5b3e2b7c9540835d30531b
- transaction
- f0c7ff8a01dee6e40ec350a4ad0b02e251fa501bd5dde849512e71c3d41f4873computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49108
the chainentry 49108
- sealed to the entry before
- a55b33fef2fd79340dd383cfe657620fb465a049499041c78a3d252e1a0a1bd2
- this leaf
- 0ea6fe252b2bc479f3c5f46055868433457401ed5720cb834e77c45f07239d3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k5eUiCwQ33OO1FX9uDZ4N48d7WLdi+fdAdUrafBFu1VpNp1Hg6LqWljyW9OoqHXJGsc663OqKHnRE6gqRvkRAw==