The public URLs that Mosce ERP exposes so the DGII and other issuers can send incoming e-CF and commercial acknowledgments to your RNC. What to paste in which field of the Virtual Office certification process, including the optional Authentication URL.
During certification as an Electronic Issuer, the DGII asks you to register the public URLs where your system receives incoming e-CFs and commercial acknowledgments. Mosce ERP exposes those URLs centrally; you paste them in the corresponding fields of the Virtual Office and from that moment the DGII uses them to route vouchers to your RNC. This guide covers which they are, what each one does, and how to register them.
The Fiscal configuration is complete (RNC, legal name, regime). See Fiscal configuration.
You have access to the DGII Virtual Office with your taxpayer digital certificate.
You have already started the certification process in the DGII and you are on the step that requests the URLs (typically Step 7 or Step 12 of the Electronic Issuer flow, depending on the current version of the certification process).
You have access to fiscal:manage in Mosce ERP if you want to save the DGII confirmation ID in the tenant.
Note on the regulatory source. The exact detail of step 7 / 12 of the certification process is specified in the DGII document Proceso de Certificación para ser Emisor Electrónico. Before submitting your organization for certification, verify the values and the field names against the most recent version of the DGII PDF available on the DGII portal. The URLs that Mosce ERP exposes (described below) are the implementation truth; the mapping to DGII form fields may be updated with future revisions of the official process.
The e-CF issuer when confirming commercially on one of your outgoing vouchers
Authentication (seed)
https://api.helix.do/fe/autenticacion/api/semilla
Optional
Whoever sends you vouchers, if you decide to require an access token before receiving them
Where to see them. Mosce ERP has a dedicated Inbound URLs screen (fiscal section) that shows each URL with a Copy button and a Registered / Pending registration badge that updates when the DGII confirms each one. The values are also in this guide in case you prefer to copy them from here.
Public URL: https://api.helix.do/fe/aprobacioncomercial/api/ecf
It is where your customers send their commercial decision (ACECF - e-CF Commercial Acknowledgment) about the vouchers you issued to them. When one of your customers accepts, rejects, or partially accepts one of your e-CFs, their system signs an ACECF and POSTs it here. Mosce ERP:
Receives the XML.
Identifies the issuing tenant by the internal RNC of the XML.
Verifies the receiver's signature with the public certificate of whoever signed.
Validates the ACECF XSD.
Maps the <Estado> (accepted, rejected, partial acceptance) to the voucher's corresponding status.
Persists the decision and updates the voucher's commercial approval summary so it appears on your e-CF Documents screen.
That decision becomes visible on the e-CF Documents screen of your outgoing issuance - you know at any time whether your customer confirmed the operation commercially.
Authentication is optional per the DGII: you only register it if you want whoever sends you vouchers to authenticate before you accept their e-CF or their commercial approval. As long as you do not require it, reception works just as it does today - Mosce ERP validates the XML digital signature as the primary security control and does not reject existing issuers for not bringing a token.
POST where the issuer sends the signed seed and receives the token
The exchange, in three steps:
Whoever is going to send you vouchers requests a seed from the seed URL (a single-use XML file).
They sign that seed with their digital certificate and send it to the certificate validation URL.
If the signature is valid and their RNC is authorized, they receive a temporary access token (RFC 6750, valid for 1 hour) that they include in the Authorization: Bearer … header when sending you the e-CF or the commercial approval.
In the OFV portal only the seed URL is pasted. The certificate validation URL is the second step of the exchange and is shown only as a reference.
Mosce ERP uses a single-host architecture: the public URLs are on a single domain (api.helix.do) and serve all tenants. The routing to the correct tenant is done by the <RNCComprador> inside the XML, not by the URL.
When the voucher arrives at https://api.helix.do/fe/recepcion/api/ecf, Mosce ERP reads that field, finds the corresponding tenant, and persists it in its scope. If the RNC in the XML does not correspond to any tenant in Mosce ERP, the response is a signed rejection ARECF - no information is leaked about which RNCs are registered.
Practical consequences: you do not have a URL "of your own" (all Mosce ERP taxpayers share the same public URL); the XML digital signature and the content-based routing ensure isolation; the DGII allows this model because the specification defines routing by content, not by URL.
In the fiscal section of Mosce ERP, open the Inbound URLs tab. Each URL comes with a Copy button and a badge that indicates whether the DGII has already confirmed it (Registered) or whether you still have to paste it in the OFV (Pending registration). The Authentication row shows its two addresses (seed and certificate validation). The fixed values, in case you prefer to copy them from this guide:
Reception (required) https://api.helix.do/fe/recepcion/api/ecfCommercial Approval (required) https://api.helix.do/fe/aprobacioncomercial/api/ecfAuthentication - seed (optional, registered in the OFV) https://api.helix.do/fe/autenticacion/api/semillaAuthentication - certificate validation (informative, not registered) https://api.helix.do/fe/autenticacion/api/validacioncertificado
Verify the exact field names against the current version of the DGII Proceso de Certificación para ser Emisor Electrónico before submitting for certification.
Enter the Virtual Office with your taxpayer digital certificate.
Navigate to the Facturación Electrónica → Proceso de certificación menu (or equivalent according to the current version of the process).
Locate the URL Request steps (Steps 7 and 12 in the historical flow). You will see two forms:
e-CF Reception URL.
Commercial Approval URL.
Paste the corresponding Mosce ERP URLs (previous section), one in each field.
If the form includes an optional field for Authentication URL and you want to require a token, paste the seed URL there (.../fe/autenticacion/api/semilla); if not, leave it blank. The certificate validation URL is not registered in the portal.
Save the form. The DGII returns a confirmation ID or a request code.
Save the confirmation ID in your process file. In the Inbound URLs tab of Mosce ERP you will see each URL's badge change to Registered when the DGII confirms it.
Wait for the DGII to approve the step. At that point, the URL becomes active and you start receiving real e-CF and ACECF.
DGII - Proceso de Certificación para ser Emisor Electrónico. Before submitting your organization for certification, verify the current steps against the most recent PDF on the DGII portal. The values pasted in the form are the same even if the DGII renames the fields in future revisions of the process.
DGII - Descripción Técnica de los Servicios (block Comunicación Emisor-Receptor). Defines the receiver authentication service: GET /fe/autenticacion/api/semilla returns the XML seed; POST /fe/autenticacion/api/validacioncertificado validates the signed seed and returns { token, expira, expedido }, a temporary access token via the Authorization: Bearer … header (RFC 6750, valid for 1 hour). Available on the DGII portal.
DGII - Informe Técnico e-CF v1.0 - «URL Autenticación Opcional»: the registration of the authentication URL is optional for the receiver. Available on the DGII portal.