why2 reasons
mandatedestination_not_allowed
op 0 pays GBBVGUUP2P4NZVHFIIIGGMMPN3FUAO6YXEJ4HLQJMG637AWIMTAQVBCQ, which is not in the allowlist
counterpartycounterparty_denied
GBBVGUUP2P4NZVHFIIIGGMMPN3FUAO6YXEJ4HLQJMG637AWIMTAQVBCQ 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
- 374de6e59307cf4bb25554581adf5588a8a33d99bb7a987a2fbf5e04682f0c0a
- request
- edb1d96c8927a4e0a4c1bee06608d74a53dfcee5d7828d814477ede7ad3a8467
- transaction
- b329b9dd37183388b7ca8ff53d57ca32745cc75369a080a2881463c7acc7eff5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63611
the chainentry 63611
- sealed to the entry before
- 306a4864dc1e8c373901ef0b9dfb6a89af7fc6d9ce73fbc8be99fab9fb96725a
- this leaf
- 0a57014f5b64a1e96c5aed339153499db151026deaabb334cedf95596dff3a86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4dtIDz6QLUVWcpoYbt5uOtB8CDQ7+CJRQRQKway+KZS7Tpe/UrEjaOEKEKltTkEMwoYIii/8f+KlMRiscGRBAQ==