RFC registration for Stamping Service

Sovos has created a REST API to register an issuer's RFC for the stamping service.

Content

General Features
What do I need?
Service Location
HTTP Header
Body
Response Codes

General Features

Before stamping through the Sovos service, you will need to register and approve the issuer’s RFC in the platform. It is mandatory to link each RFC with an email address, which will receive a notification with the instructions for the authorization process.

What do I need?

Use the Sovos services to stamp fiscal receipts
To generate an API key on your Sovos account, this is an identifier that authenticates the user on the platform web services. To generate an API key, please review this article: Generating an API Key for web services (Spanish only).

Service Location

To register an RFC for stamping procedures in Sovos, you should send to the REST API the following:

Environment	URL
UAT	https://oat.reachcore.com/api/rest/Timbre/rfc
Production	https://go.reachcore.com/api/rest/Timbre/rfc

All requests must be done through https. Connection done through http will be rejected.

HTTP POST

HTTP Header

Parameter	Value	Use	Description
`RCApiKey`	API Key	Required	Service authentication through API Key generated in the Sovos Mexico platform.
`Content-Type`	`application/json`	Required	REST API only handles JSON structures, you must declare it.

Body

A JSON structure is only accepted in the body of the request. You must send the following attributes:

Atribute	Use	Description
RFC	Required	Indicates the value of the RFC to be registered. Must match the regular expression: `[A-Z,Ñ,&]{3,4}[0-9]{2}[0-1][0-9][0-3][0-9][A-Z,0-9]?[A-Z,0-9]?[0-9,A-Z]?`
Correo	Required	Establishes the e-mail address of the person who will authorize the use of the RFC.
RazonSocial	Optional	Establishes the name of the company name the RFC belongs to.

Example

{
    "RFC": "AAA010101AAA",
    "Correo": "timbre@mail.com",
    "RazonSocial": "Razón social del RFC: AAA010101AAA"
}

Response Codes

As response from the REST Service, you will get a code indicating the result of the procedure. All the responses will be in JSON format (application/json).

HTTP Code	Error Code	Meaning	Description
200	--	OK	The RFC was correctly registered.
400	400-001	Bad request	The RFC is not valid.
400	400-002	Bad request	The email is not valid.
400	400-003	Bad request	The RFC is not found in the list of taxpayers with liability (LCO).
401	--	Unauthorized	The API Key is not valid.
404	--	Not Found	The URL does not exist.
500	--	Internal Server Error	Sovos platform error.

Example of a successful response

{
    "Autorizado": false,
    "Correo": "timbre@mail.com",
    "FechaAutorizacion": null,
    "FechaRegistro": "2016-07-22T12:20:59.1968383-05:00",
    "Habilitado": true,
    "RFC": "HEZD850613C22",
    "RazonSocial": null
}

Example of a response with errors

{
    "errors": [
        {
            "errorCode": "400-001",
            "errorMessage": "El RFC  no es válido"
        },
        {
            "errorCode": "400-002",
            "errorMessage": "El correo electrónico timbremail.com no es válido"
        },
        {
            "errorCode": "400-003",
            "errorMessage": "El RFC  no fue encontrado en la lista de LCO"
        }
    ]
}

For more information or doubts related to this guide, please send an email to MEX-soporte@sovos.com

Regresar