Validation for RFC with data (DEPRECATED) DON'T USE THIS API

Intro

This API is meant to validate a list of RFCs for Persona Física and for Persona Moral with the full tax information in the SAT system, checking for every RFC if the postal code and name of the person is correct.

Important points

Mandatory Fields

The request contains a list called rfcs, it is mandatory to send at least one element.
The fields rfc, cp and nombre are mandatory for every RFC sent.
The field "nombre" can contain a name of a Persona Física or the razón social of a Persona Moral.

Validations applied

For the field rfc, kiban cloud applies a RFC format validation according to the SAT rules, the RFC must contain an RFC with homoclave and could be for Persona Física or Persona Moral.

Test cases

To recover a successful response in sandbox environment it is necessary to send a test case (see query param testCase), the posible values are:

  • valid it will return an example with valid RFCs
  • invalid it will return an example with invalid RFCs

Possible Errors

The next errors can be returned if there is a problem with the request body or the execution of this service:

"RFCs": "EMPTY_ERROR; can't be empty",. rfcs array cannot be empty.

"rfc[1]": "EMPTY_ERROR; can't be empty". The field "rfc" of the first element in the rfcs array cannot be empty.

"cp[1]": "EMPTY_ERROR; can't be empty". The field "cp" of the first element in the rfc array cannot be empty.

"nombre[1]": "EMPTY_ERROR; can't be empty". The field "nombre" of the first element in the rfc array cannot be empty.

Possible responses
The next results are the possible responses after apply the validation to RFCs:

"RFC no registrado en el padrón de contribuyentes": This means the RFC is not registered and it is not valid

"RFC válido, y susceptible de recibir facturas": This means the RFC is registered and it is valid

"El nombre, denominación o razón social no coincide con el registrado en el RFC": This means the RFC is  registered but the name or the company name is not valid

"El Código Postal no coincide con el registrado en el RFC": This means the RFC is  registered but the postal code is not valid
Language
Credentials
Header
Click Try It! to start a request and see the response here!