why2 reasons
mandatedestination_not_allowed
op 0 pays GDLBRQ3Y3YT7EBDDY62RYH6L4XOR72DMJU56UE7CHV6FYM6L5DUHJ7YG, which is not in the allowlist
counterpartycounterparty_denied
GDLBRQ3Y3YT7EBDDY62RYH6L4XOR72DMJU56UE7CHV6FYM6L5DUHJ7YG 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
- aeb025db02b28c21e0851766a7dd45e372b5e3d06df9e075fc3e0707f6794304
- request
- 646ee6e028bc58232519c9ad7dc64cc06b93be88432795b39115f5237c8b3a6d
- transaction
- b522e5dbd87ebf0a7be4dcc7db5c1bb7c52615477bacdd0d15d1512997303512computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1311
the chainentry 1311
- sealed to the entry before
- 49cbab8326e3501117016d40e68845edfc73471ad8e3b559f27818b2ab096aec
- this leaf
- 1a5baadff639d580049952153ca73409f647d466e58eea804c664e76833721fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F0HYqruh7p0uwT13NaUgIE1A5vpguJVB5uKYQoesRCmCmhV7WLfeubNSHMUDicXIHD93wWVSlnTvgvlvFjboBA==