Thanks for your patience.
We were able to replicate the issue in our environment while testing the scenario using your images. We have also observed that API gave correct output (i.e. commas were recognized correctly) when we did not use RecognitionBlock. However, the issue remained for slash in date format.
Therefore, we have logged this issue as OCR-706 in our issue tracking system for further investigation. We will look into details of the issue and keep you posted with the status of its correction. Please spare us little time.
We are sorry for the inconvenience.