Working with Encrypted Tokens

Convirza uses 256-bit encryption for access tokens to enhance security:

Encrypted tokens: Tokens are encrypted before being sent to your application

Automatic validation: The API automatically validates tokens from your Authorization headers

URL-safe encoding: Tokens are safe to use in URLs and headers

No decoding needed: Always use tokens as-is — never attempt to decode or parse them

For Web Applications:

For Mobile Applications:

Security Notes:

Never store tokens in localStorage (vulnerable to XSS)

Never log tokens in console or error messages

Clear tokens immediately on logout

Implement token refresh before expiration