As per discussion in #98, the function signatures for above two types should define message to be &str to correctly capture the spec requirement of payloads being valid UTF-8 data. As is currently the case for Claims.
This constitutes a SemVer breaking change.