why2 reasons
mandatedestination_not_allowed
op 0 pays GD4RIFP3DA2RCJOZLDLCSANJVT5SKRLZZCHX2OGGADZHD2V2OZKRJYZ4, which is not in the allowlist
counterpartycounterparty_denied
GD4RIFP3DA2RCJOZLDLCSANJVT5SKRLZZCHX2OGGADZHD2V2OZKRJYZ4 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
- 1000506d439cbacc7a228f14d9b569817760f553d80a2f63fe9859c6312b8df6
- request
- 5164f91db4aa03568aa76e27a430e4966018f7ab8b47cd9ac6e8630251b2813c
- transaction
- b271d37a851412c274cb646a7f82c1a861a5cb7a5b0ae060cd1cdc64b8616ef2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64003
the chainentry 64003
- sealed to the entry before
- b7854ae35f791f91665a4a4ed6be8b18e07b9cbbc8a9bd5bd7d02bfbead428de
- this leaf
- f78f2c588923529da9ca41043b3517a8986e3bbad3808ee4f94dd1c73f69e445
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +sfJGsHJVWvD5rd44bUZF9NKt0IlR8o9Ll+aOTM407O6j05JlMPpfTwVRRkg9xAD0ROpVd8o1NjbP8sW4ME+DQ==