DGII 30 — Invalid XAdES-BES signature
Firma XAdES-BES inválida
| Field | Value |
|---|---|
| DGII code | 30 |
| Category | Signature |
| HTTP status | 422 |
| Retryable | No |
| Tenant fixable | No |
Problem.type | https://errors.api.erply.pro/dgii-30-firma-invalida |
Probable cause
DGII could not verify the XAdES-BES signature. Typical cause: the digest does not match or canonicalisation is not Exclusive C14N.
How to fix
- Retry — if it persists, open a ticket: the issue is in the ERPly Pro signing layer.
- Include the
correlationIdso we can correlate the signer Lambda log.
Example application/problem+json response
{
"type": "https://errors.api.erply.pro/dgii-30-firma-invalida",
"title": "Invalid XAdES-BES signature",
"status": 422,
"detail": "DGII code 30: Invalid XAdES-BES signature",
"instance": "/v1/invoices",
"correlationId": "1-65fa7c3a-6f9c2d8e0a1b2c3d4e5f6789",
"dgii": {
"code": "30",
"trackId": "20260501-DGII-9988"
}
}
Source
DGII PSFE Technical Spec + Norma 06-04. Exact citation pending review by the compliance specialist.