> It can be a real payload (generally encoded).
Based on your definitions, a JWT is therefore a specific kind of opaque token. I don't think it is personally.
I think we really should be talking about tokens as falling into two categories, of which JWT is an implementation of the first:
1) stateless - the token contains meaningful content that can be verified by a consumer. JWT is such an implementation with a standardized way of verifying the content without additional database queries (excepting revocation here)
2) pure identifiers - the token is merely an identifier, and all consumers must reach out to some other service (eg redis) to retrieve the details/capabilities that the session should have.
Edit: alternative proposed terms: content-full, content-less