# Payload Encryption
source: https://developer.mastercard.com/transactions-service/documentation/api-basics-options/e2e-encryption-intro/index.md

## Payload Encryption {#payload-encryption}

Loyalty Transactions Service uses TLS to protect requests in transit. As described in [API Basics](https://developer.mastercard.com/transactions-service/documentation/api-basics/index.md#encryption), requests containing sensitive data such as card numbers should also use JWE payload encryption.

The transaction search schema accepts an opaque RANAC account identifier; do not substitute a card number for `userId`. Check the [API Reference](https://developer.mastercard.com/transactions-service/documentation/api-reference/index.md) for accepted fields and obtain the encryption configuration required for your integration from your Product Delivery or CIS Implementation Manager.

Manage your encryption keys in the [Developer Dashboard](https://developer.mastercard.com/dashboard). Encryption does not replace [client authentication](https://developer.mastercard.com/transactions-service/documentation/api-basics/index.md#client-authentication).

## Next Steps {#next-steps}

Follow [Encryption Configuration](https://developer.mastercard.com/transactions-service/documentation/api-basics-options/e2e-encryption-config/index.md) and the official [Securing Sensitive Data Using Payload Encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/) guide.