why2 reasons
mandatedestination_not_allowed
op 0 pays GDQ3QF4FCZAZ7A4SMNOPZDXDY5QMFQYEL43IE265ZUOHDDEDIF2TK6RY, which is not in the allowlist
counterpartycounterparty_denied
GDQ3QF4FCZAZ7A4SMNOPZDXDY5QMFQYEL43IE265ZUOHDDEDIF2TK6RY 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
- d8a69482d5ed717a0c4d3141095a0b4e6b9c961bdb10f0245975c116827a0ebc
- request
- 0969d5a1131835670c670e607ec572b5153e2b074c5ccdf5cdcccfebe98ff4d1
- transaction
- 9c1c8de46523c9b46d9a45fa5e44534c290d9919e1f88caa5afbd398e928b3f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75640
the chainentry 75640
- sealed to the entry before
- acc232462300323011eddd4c9f746e66646886a044540008f7a08187abcd7ce1
- this leaf
- 3945f4b7029f9e0e6af7f87575fbe4b452e1bb24bb444612db2ad2da7304b73c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0wDx0SffVPSKMuVJpCMDG9fjzphUuTYcJreQHRN6EQVZ9pDNiHUQkCNAL/5eY7Q5XpYaNuLUV7IkxTBSzooHBQ==