why2 reasons
mandatedestination_not_allowed
op 0 pays GDHUZMVTZPC5DUYS2AFPEF4L2PQS77HQIX4AUTC23FCH53DCQV6RWSVP, which is not in the allowlist
counterpartycounterparty_denied
GDHUZMVTZPC5DUYS2AFPEF4L2PQS77HQIX4AUTC23FCH53DCQV6RWSVP 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
- c44f8786182fc3807e605ce7ee507495dbf14eac97e75fad0ea81654fae27d06
- request
- 9a719043db2ff696db9af93fb092b21f38b69d7464bdc874c4832d6d7559ad6d
- transaction
- 51a1efc36c18a3e98ed6596dbe4cd6716623f0a83abe611f837ce8871657db93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30492
the chainentry 30492
- sealed to the entry before
- 3ebc6114eff52ba9e6d0385ef37f12626b3904ad3da6d7b957ecbecf3f992d2e
- this leaf
- c9786998f18229161a66d8f6036ee4ca017e68f81715507fe88b688393dda84c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m7+E0X/R3FML5cSZPrgUkVphF5PIQ4FGISZSKb+1XFDlIM0wQRgt2LsUzCVlelYVTiJGOGhXNoNn8ZktRwVJCQ==