Credit Card Redaction

Last Updated : Oct 25, 2021 |

Avaya Oceana® introduces the Credit Card Redaction feature which allows credit card patterns sent by the user in a message to be redacted, and not shared with the agent, or stored in the transcript.

The feature is enabled at an application level and applied to all user messages received on any platform. Only the user messages having the credit card details redacted, the agent messages are not checked. The feature scans for common credit card patterns, such as 16-digit numbers, including combinations of credit card numbers separated by dot, space, or dash. For example, 4242 4242 4242 4242.

Configuration

The Avaya New Product Introduction (NPI) team configures this feature on behalf of the customer.

Operation

The credit card masking function is enabled at application level. The Avaya NPI team administers the operation on behalf of the customer.

Scenario

Operation

Mask Credit Card Numbers Enabled

When a user sends a message that contains any combination of a credit card pattern, the card number is redacted.

Masked Credit Card Numbers Disabled

Messages must pass through without masking the credit card numbers.

Limitations

PIN numbers, expiry dates, or CVV codes are not redacted by this feature. Also, if the credit card pattern is different from the pattern mentioned above, it may not be filtered.

For example, if a user replaces a zero with the letter 'O' - the examples may be missed by the filter.

Enabling this feature only impacts future messages. The existing credit card numbers in conversations, already in queue, or already in historical transcripts are not redacted.