Utilerias.agregarEmisorFirmaFiel
Create a new issuer in the implementation, automatically generating a manifest and providing a URL where the Manifest can be signed with the issuer's e-signature FIEL.
- Parameters
-
Name Description Required usuario Username registered for use of the Web Service. Yes password User password. Yes emisor A composite type "Emisor" in which the data of the issuer to be registered is specified.
Yes - Complex type Emisor
-
Name Description Required rfc Issuer's RFC. Yes razonSocial Name or business name of the issuer. Yes nombreComercial Trade name. No email Email address where the registration notification should be sent and the URL for signing the Manifest. No domicilioFiscal Composite type to specify the issuer's tax address. No - Complex type DomicilioFiscal
-
Name Description Required calle Street. Yes noExt Exterior number. Yes noInt Interior number. No colonia Cologne. Yes codigoPostal Zip code. Yes ciudad City. Yes estado State. Yes pais Country. Yes This method returns a composite type: Response. Please see the details in the "Atributos de Response" (Response Attributes) table. If the status is 200, the message will be the URL where the user must log in with their e-signature (FIEL) to sign the Manifest.
Once the user signs the manifest with their e-signature, the issuer is automatically activated.
Example request:
Download this example
Headers:
POST / HTTP/1.1
Accept: text/xml, multipart/*, application/soap
Host: testing.solucionfactible.com
Content-Length: 1271
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://utilerias.timbrado.ws.cfdi.solucionfactible.com#agregarEmisorFirmaFiel"
Return:
- This method returns a composite type: Response, as detailed in the following table. If the status is 200, the message will be the URL where the user must log in with their e-signature (FIEL) to sign the Manifest.
Once the user signs the manifest with their e-signature (FIEL), the issuer is automatically activated. -
Response AttributesName Description Required status Indicates the transaction status; for details of the status codes, see Response codes.”
Yes mensaje Detailed message of the operation performed or description of the error. Yes
Example response
Download this example
Response Codes
- 200 — The transaction has been completed successfully.
- 500 — Errors have occurred that have prevented the process from being completed.
- 501 — A database connection error has occurred.
- 502 — It has failed to retrieve or store information in the database.
- 503 — The limit of concurrent access licenses to the database has been reached.
- 601 — Authentication error, the username or password is incorrect.
- 602 — The user account is locked.
- 603 — Your account password has expired.
- 604 — The maximum allowed number of failed authentication attempts has been exceeded..
- 605 — The user is currently inactive.
- 611 — The data received is incomplete or not located where it would be expected.
- 612 — The XML file or one of its attributes is malformed.
- 624 — Violation of uniqueness restriction.
- 630 — The implementation stamps have run out.
- 631 — The issuer's stamps have run out.
- 632 — The fair use limit allowed per transaction has been reached.
- 633 — The transaction has been completed successfully.
