why2 reasons
mandatedestination_not_allowed
op 0 pays GDFT57ESHKL7M6HQ7LE4YX5WIPAJKMUD7SDJRVTBNTPRT3EIEHJCGGXS, which is not in the allowlist
counterpartycounterparty_denied
GDFT57ESHKL7M6HQ7LE4YX5WIPAJKMUD7SDJRVTBNTPRT3EIEHJCGGXS 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
- e11e77c029169d0628013171cf5dc57d590ffd844dd9304c448b4df2245d75ba
- request
- 85ead974050b9afee320b3cbd17649ce74a9c83b2155b9ee1f4ecb2a592e4bcb
- transaction
- a73bd819f7e72c9fc6a85acb2b27b4cca78043a1b4dbc43c88da155ece64ef39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43189
the chainentry 43189
- sealed to the entry before
- 58081eb410a4f78ca2a2a3d9d06cadaff9e673831f250cb811b867be819e2353
- this leaf
- 9b2c2ff80961b0faf0ecdf0cdc31bb50cf9c7739292f5ef23318f7be700a7d37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rndu7xv17UL2ST6K/Z1dL9oprVSogZyZSCeE0hUHHYq7fJUDRFKuNkrSQkgFlVnlYUJWAcQLvFoHnZV/5fWnCg==