why2 reasons
mandatedestination_not_allowed
op 0 pays GBFGQVO7AR2GEZDWYW3E4MKWYLSXPU7C7Q3MIOSE4YM6BLSHPGZQ7GDR, which is not in the allowlist
counterpartycounterparty_denied
GBFGQVO7AR2GEZDWYW3E4MKWYLSXPU7C7Q3MIOSE4YM6BLSHPGZQ7GDR 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
- 2ff6561b3735fd2354e5d9c96e9c73ea88f3c6616fdf396e238268407472ddd7
- request
- 6223a535305445aaa04e5297997b510b9c57283d3d430ba0557c3db0674cef0a
- transaction
- 4e5ac1c5aeeaeb4d56c8d0c924cd212cd7e98f387b81052a3f5fdc977ab5e17acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9706
the chainentry 9706
- sealed to the entry before
- c8c9ca73bda0bf6727609849a6e36d13c854c733a119a32cb007afd037589a35
- this leaf
- c188782294aa6536992784275dc0e8ac98793a1011e6646127a30acce119eb31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1A5zpz1G6PC8I+5ede6GDZHfT7b3lqRNrpN2eSfmZhvK6ZtjwiAKEnxBbm7CLDe552k+pfVPn7Y/g2fjJIO4Bg==