why2 reasons
mandatedestination_not_allowed
op 0 pays GD5ENGY2B34Y5KW6KGTOJO56NYWZ66ASVVYXANBJIPPH62L7I6SFWGQJ, which is not in the allowlist
counterpartycounterparty_denied
GD5ENGY2B34Y5KW6KGTOJO56NYWZ66ASVVYXANBJIPPH62L7I6SFWGQJ 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
- 2fce65df23daacbbf2ec79575d3c9ebd09678647b4e1775df17144d6d04a4700
- request
- ef3d881554198249684cbb26de0ae8f7d9ef8886b357ea75cc8506f553620c5c
- transaction
- 0750d926eca132ef8ac258c22357c35c1bf303e16a522f80fc73de1cac6978cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73917
the chainentry 73917
- sealed to the entry before
- 5011e37b58b953d2971e19fcc092bdd095598865d1150d2d8d875742820a9678
- this leaf
- 8c1fb973c1867c573c997daf9735e177e91e8a5e6b8d577b547f33781055a0d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WCHxXjqf0DTLAKIjUErN2HQ9TBRwDpg9IC5EWCk4yl72diDs4YsQ/v2BLi1ccT3gt78+gFkDhJFo9mBsz7DSAQ==