Issue
Depending on when you scan the card on the device. They come out with different types of Card Data.
When scanning the CARD between the SDK and the G-SDK, there may be a part of the confusion in the data.
Example
>>> Scan a card...
Card data: { "type": "CARD_TYPE_CSN", "CSNCardData": { "type": "CARD_TYPE_CSN", "size": 32, "data": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOLkOCgAQBeA=" } }
>>> Generate real-time events for 10 seconds
Event: { "ID": 850, "timestamp": 1631698099, "deviceID": 543308151, "eventCode": 4352, "subCode": 2, "cardData": "NDA4NzMxMzU3MjkyODk0NzY4MAAAAAAAAAAAAAAAAAA=" }
Comparing Card Event and Event Log
| G-SDK API | Hex(32byte) | Data | Converting Method | Result(CardNumber) |
| Scan Card | 0x00000000000000000000000000000 00000000000000000004f39580a001005e0 | AAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAATzlYCgAQBeA= | BASE64 > Hexadeimal(32byte) > Decimal | 5708690802642781664 |
| Event Log | - | NTcwODY5MDgwMjY0Mjc4 MTY2NAAAAAAAAAAAAAAAAAA= | Decode from Base64 format | 5708690802642781664 |
Result
In conclusion, the card scan values look different because it developed by SDK, BIOSTAR, and G-SDK is different.
it shows that each data of type has a result, but eventually, the result is the same.