MVE Technical Requirements: What Importers Need to Know About VUCEM Integration

Technical Architecture of MVE Filing

The MVE is filed through VUCEM using a two-step SOAP web service call. Step one is the Ingreso (submission) service, which receives the signed MVE XML document. Step two is the Consulta (query) service, which retrieves the assigned MNVA number asynchronously. The submission must be signed using RSA-SHA256 with the importer's e.firma certificate (FIEL). This is a strict requirement — customs broker digital seals (VUCEM or COVE seals) cannot be used for MVE signing.

Key Technical Specifications

• Protocol: SOAP/WS-Security over HTTPS.
• Production endpoint (Ingreso): https://privados.ventanillaunica.gob.mx/IngresoManifestacionImpl/IngresoManifestacionService?wsdl
• Production endpoint (Consulta): https://privados.ventanillaunica.gob.mx/ConsultaManifestacionImpl/ConsultaManifestacionService?wsdl
• QA endpoint: https://privadosqa.vucem.mx:9105/ (for testing).
• Signing: RSA-SHA256, Base64-encoded signature, using the importer's .key and .cer files.
• Certificate: Must be a valid e.firma (FIEL) issued by SAT to the importer's RFC.
• Format: XML conforming to VUCEM's E2 schema (Formato E2, Regla 1.5.1, Anexo 1 RGCE 2025).

For companies building their own MVE integration, plan for the asynchronous nature of the VUCEM response. The Ingreso call returns an acknowledgment, but the MNVA number is assigned asynchronously and must be retrieved via the Consulta service, sometimes with a delay of minutes to hours. Implement a polling mechanism or use Camtom's integration, which handles the full asynchronous workflow including retry logic and error notification.