Synqpay Root CA Certificate
The Synqpay Root CA is a self-signed certificate used to establish secure connections for:
- HTTPS communication with the device
- WebSockets for real-time data exchange
- Raw TCP communication with the device
Clients can trust this certificate to enable secure TLS connections.
Certificate Details
Synqpay RSA2048 Root CA
| Field | Value |
|---|---|
| Common Name (CN) | Synqpay Root CA |
| Organization (O) | Codeblocks Ltd. |
| Organizational Unit (OU) | Payment |
| Location | Raanana, Central District, IL |
| Valid Until | 19/Jan/2035 |
| Serial Number | 6D:09:78:7B:F0:41:B7:F1:F8:3A:E2:28:FA:06:79:75:C1:E1:CF:1F |
| SHA-1 Fingerprint | 52:69:D0:5C:DB:24:B9:A4:13:E0:E8:F0:A8:EA:60:42:52:D0:96:E4 |
| SHA-256 Fingerprint | 61:AA:67:E7:0D:4B:C5:4A:25:31:E1:E4:40:16:87:C0:B1:D9:61:0D:EC:16:E2:49:AF:F3:F4:12:3A:D1:1D:5C |
Certificate Usage
The server certificate used for secure communication is signed by this self-signed Root CA. The certificate includes the device’s local network IP in the Subject Alternative Name (SAN) field. If the device’s IP changes, the certificate is regenerated with the updated IP.
Clients can either trust this Root CA or disable certificate verification to establish a connection. Since the certificate may change when the device IP changes, clients should handle potential certificate updates accordingly.
Certificate Verification
By default, TLS clients will reject self-signed certificates unless the Root CA is explicitly trusted.
Option 1: Trust the Root CA (Recommended)
To properly validate the device’s certificate, install the Root CA in your system’s trust store.
Option 2: Disable Certificate Verification
If needed, clients can disable certificate verification to allow HTTPS/WebSocket connections without trusting the Root CA.
Warning: This method removes TLS security checks and should only be used in controlled environments.