why2 reasons
mandatedestination_not_allowed
op 0 pays GDUQ7YRNT3654HDTQMCOLHO3Y6JOR22BPVFEVR6Z6DBYBMGA2MYX5LH5, which is not in the allowlist
counterpartycounterparty_denied
GDUQ7YRNT3654HDTQMCOLHO3Y6JOR22BPVFEVR6Z6DBYBMGA2MYX5LH5 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
- e21441d64ad99ed2dfe28e616fdec5cb09a6cf94e74c72736cac1b2b2bb36fdf
- request
- d7cc2821316df637519b779dc078c2cc8d0a327d5e9487d9bb571c787bfd888a
- transaction
- ff92d4ec2fca4aea040ea08a078166e0434f7dd889323c516c702b0e1ba20d51computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39375
the chainentry 39375
- sealed to the entry before
- 880423ec8b1f9e8877c6661a841ffc51875696f7e59b1ab957f390fa9b543e36
- this leaf
- dfe62a6e567f9e3629d19083c75e0e1988ea1dbd53c0cd5dca2fbb259e68ca68
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZI6Pw/C8PaiHW4pGbUuBmB3aoOpLCCFcyNB2QqcuDq6NaI4jCrhkTCzC7839aixApQFqjWeN8PhUbLf9sYSoDQ==