The AES cryto library provided to us from company, does not generate a different encrypted value for plain text.
If text is "abcd" , it will generate the same encrypted value over multiple iterations.
So when we have to interact with other applications ( they redirecting it to our website and we redirecting back to their website), the scheme we use is to add a timestamp with a "#", and then encrypt.
Like in this case text becomes "abcd#32342534234232" , and then we encrypt it. The caller application decrypts it and discards the timestamp part.
I want to know the pros and cons of this scheme considering "abcd" is a user data but not a critical data like password.