why2 reasons
mandatedestination_not_allowed
op 0 pays GDQ3AOXB4AV65F2X7K6KEFXPKIRG7T2YWMC2OSYXMDFXWZLWH6OAXRNI, which is not in the allowlist
counterpartycounterparty_denied
GDQ3AOXB4AV65F2X7K6KEFXPKIRG7T2YWMC2OSYXMDFXWZLWH6OAXRNI 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
- 1e6347de941f3ecb76511ccbf30172a01b7726fc7868275fb6be1e14f4a19c9a
- request
- 01cecc736ef45d5c2072524271723900a91bed8ce337d631d9bbcddc5db24ab7
- transaction
- 25712e05854af581804721afda4a5b47878ec9aa8b383a40dac33644d6281da1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48176
the chainentry 48176
- sealed to the entry before
- ac7246f585149d5ed8c45942d4bfaa8f888a40cd201a339f8c2ef382d4b68431
- this leaf
- 1a230ba0e01ec7ed3edfafead2c780508839c740058a8260005c631c0c0cf5e0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JwjlXoy18mAZLpe14J6Zs/rCevC3A95+Hibzd1DXH9zJAMXIltSj9jvDNjOdTHTz/LNHatbh59JEQLnYktzKDQ==