why2 reasons
mandatedestination_not_allowed
op 0 pays GBMCIWW3UX6V5I7QBR253EVHI7ZP7EYWTCYSXGEISCHN7QUA4JUK3EIY, which is not in the allowlist
counterpartycounterparty_denied
GBMCIWW3UX6V5I7QBR253EVHI7ZP7EYWTCYSXGEISCHN7QUA4JUK3EIY 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
- ff29a7f1da879d5e73558f622a5e20a6844100f00f02007cecb03de4f121a3c2
- request
- 1c8b969af0f39848bdaa671f2fe1cdad83761db1f23a2efd6a86dae53b025654
- transaction
- 0459485b37c386933a4960f23e9c465b347b9a1ac680abfda2e1ead4311d5b62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2596
the chainentry 2596
- sealed to the entry before
- 51d9c4300650cdb292f60deb50d7bfbe2e878dd203ad45f1b3592438be9254dd
- this leaf
- 33bd84367e7e5991da24f7a7a3013cd63922ce1d0d1111e6f15ec7dc96f7c632
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rBjtN+FPMGN+FJnY1MkxUlb4sMvC8zlZP2vthS70dt2ewKViv5/QJF6IT0vQS08JSV1yKcdvoghp8FVELLwxBQ==