why2 reasons
mandatedestination_not_allowed
op 0 pays GD5MXTF2MXWATCDXFM3WCBPOLSSPAG4DZVRA62D6NV4KERO5LYZWNKDE, which is not in the allowlist
counterpartycounterparty_denied
GD5MXTF2MXWATCDXFM3WCBPOLSSPAG4DZVRA62D6NV4KERO5LYZWNKDE 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
- d87cb3fd27727f6feb677c8ada7c42a2a5e2d7cd34aac34af62397f7b68d2e31
- request
- 3c4d77f851456de992b51080607262641bbb26780630c8e6a4c655532f55c888
- transaction
- 284392b9f61c7a3ec9373dfbbf6a08013de46a6a14e49aad23036880fee9d3ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31232
the chainentry 31232
- sealed to the entry before
- 22d06cdbde5d826861c8bd5893e741248e2e28d0b162452ff665cf5e48065c69
- this leaf
- e253bb7972d98b8fd2a62a472d8fc4db7e80b1e00bedf17e0ee1c6ba8e3d49cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7cjV+nq0Tt4IFLQkzG7I4PJoiyIM6ItZvyUEq0a5XSQnFBg+ZPR/eBDvSzS9uoUY0oXBkCYDGXvI//VP+DQ8Bg==