why2 reasons
mandatedestination_not_allowed
op 0 pays GDTUAS4KGOFRADFUPP7NGDBFO2PTUM3HLGXBSBETTKHTC732O3CA427A, which is not in the allowlist
counterpartycounterparty_denied
GDTUAS4KGOFRADFUPP7NGDBFO2PTUM3HLGXBSBETTKHTC732O3CA427A 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
- 9e1e96da55b64baf56f83834022a1c4376168c60a6353af536cb266c5c52c091
- request
- 52ea4b6f58c8a8daff7ab6dcb060e0b870cbcc4fc29ed7f51e5046e9b2cd0aad
- transaction
- a188853b4dc97fe1a890073f9f30c96986098d0f560afe63ea6a01ad40b215dbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16198
the chainentry 16198
- sealed to the entry before
- 9ea4cb9b459d48e7f85e316b96b158c08755e7bf985dfe1cca39e34d3c5acaf1
- this leaf
- d7b9289cd875b563848cd57c04414b8b5e21d71265d34282b842562a138831f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2Aa4L9un9iquBXImWZCh4bSF6npiHLpSHjYYMzfxD3wspi6lqk1Fvt35mNZCXcvISRG9DGQ6lhzf6gBlPhB5Dw==