Payment Idempotency Key Deduplication with Distributed Redis Lock

When processing payment authorizations, network retries from client mobile apps can cause accidental duplicate charges. Given a list of payment authorization requests, ensure **strict idempotency**: - If `request_id` has already been processed in the current batch, return `ALREADY_PROCESSED`. - If `request_id` has not been processed yet, record it and return `SUCCESS`. ### Input Format - First line contains an integer `n` (number of requests). - The next `n` lines each contain a string `request_id` and a float `amount`. ### Output Format - Print space-separated status strings for each request. ### Constraints - `1 <= n <= 10^5` - `request_id` contains alphanumeric and hyphen characters.