Mexico RFC Fetch

Overview
The Mexico RFC Fetch API is designed to facilitate the retrieval of detailed information about Registered Federal Contributors (RFC) in Mexico. This asynchronous API mechanism involves two API calls: the first to submit a request and the second to retrieve the result either via a webhook callback or a direct fetch using the request ID.
Use Case
This API is beneficial for financial institutions, tax advisors, and businesses that need to verify the authenticity of RFC details either for individuals (Personal Finance - PF) or entities (Personal Morales - PM). It supports compliance checks, customer verification during onboarding, and ensures accurate tax-related documentation.
API Details
API 1: RFC Reqest
Request Body
Initiate the process by submitting the RFC data:
Preproduction
Production
curl --location 'https://api.signzy.app/api/v3/global-kyc-fetch/mx/rfc' \
--header 'Authorization: <----Auth Token---->' \
--header 'Content-Type: application/json' \
--data-raw '{
    "rfc": "DIMV970321K28",
    "accountType": "PF",
    "consent": true,
    "callbackUrl": "https://webhook.site/fh37b379-f561-4dbe-9160-7245f74cd80b"
}'
curl --location 'https://api.signzy.app/api/v3/global-kyc-fetch/mx/rfc' \
--header 'Authorization: <----Auth Token---->' \
--header 'Content-Type: application/json' \
--data-raw '{
    "rfc": "DIMV970321K28",
    "accountType": "PF",
    "consent": true,
    "callbackUrl": "https://webhook.site/fh37b379-f561-4dbe-9160-7245f74cd80b"
}'
﻿
Request Body Parameters
Parameter
Description
Optional/Mandatory
Data Type
rfc
The RFC number to retrieve data for
Please see supported regex below. 
Mandatory
String
accountType
Type of account, either 'PF' for individual or 'PM' for business/legal entitiy
Mandatory
String
consent
Consent to process the data
Mandatory
Boolean
callbackUrl
URL to receive the callback with results
Optional
String
RFC Input Field Regex :
For individuals, it consists of 13 characters (4 letters followed by 6 digits and 3 alphanumeric characters) and for legal entities (and certain legal arrangements), it consists of 12 characters (3 letters followed by 6 digits and 3 alphanumeric characters). 
The first letters (4 or 3, respectively) belong to the name, the next 6 digits are the date of birth or date of incorporation, and the last 3 (or 2, for legal entities) belong to the check digits (homoclave). 
Response Body
The initial API call provides a processing status:
102 - Successful
{
    "result": {
        "requestId": "6710fe960ddfa331ae1608d6",
        "statusCode": 102,
        "status": "PROCESSING"
    }
}
{
    "result": {
        "requestId": "6710fe960ddfa331ae1608d6",
        "statusCode": 102,
        "status": "PROCESSING"
    }
}
﻿
Response Body Parameters
Parameter
Description
Data Type
requestId
Unique identifier for the request
String
statusCode
Status code of the request (102 = Processing)
Integer
status
Status of the request, e.g., 'PROCESSING'
String
API 2: RFC Data Retrieval
Request Body
Retrieve the results using the requestId:
Preproduction
Production
curl --location 'https://api-preproduction.signzy.app/api/v3/global-kyc-fetch/mx/rfc-get-data' \
--header 'Authorization: <---Auth Token--->' \
--header 'Content-Type: application/json' \
--data-raw '{
    "requestId": "67fc9c03fe2688109ffdda4e"
}'
curl --location 'https://api-preproduction.signzy.app/api/v3/global-kyc-fetch/mx/rfc-get-data' \
--header 'Authorization: <---Auth Token--->' \
--header 'Content-Type: application/json' \
--data-raw '{
    "requestId": "67fc9c03fe2688109ffdda4e"
}'
﻿
Request Body Parameters
Parameter
Description
Optional/Mandatory
Data Type
requestId
The requestId returned from the first API call
Mandatory
String
Response Body
The final data can be fetched or received through the webhook:
Successful Response
Successful Response (when callback URL is provided)
No Data Found
{
    "result": {
        "requestId": "671100b90yyfa331ae1608f7",
        "input": {
            "rfc": "DIMV970321K28",
            "accountType": "PF",
            "consent": true
        },
        "status": "SUCCESS",
        "result": {
            "rfc": "DIMV970321K28",
            "state": "Active",
            "type": "Digital Seal Certificate",
            "name": "VICTOR AGUSTIN DIAZ MENDEZ",
            "orgName": "VICTOR AGUSTIN DIAZ MENDEZ",
            "email": "[email protected]",
            "curp": "DIMV970321HSLZNC06",
            "issueDate": "2024-06-26 02:58:10",
            "expiryDate": "2028-06-26 02:58:10",
            "counselRfc": "",
            "counselCurp": ""
        }
    }
}
{
    "result": {
        "requestId": "671100b90yyfa331ae1608f7",
        "input": {
            "rfc": "DIMV970321K28",
            "accountType": "PF",
            "consent": true
        },
        "status": "SUCCESS",
        "result": {
            "rfc": "DIMV970321K28",
            "state": "Active",
            "type": "Digital Seal Certificate",
            "name": "VICTOR AGUSTIN DIAZ MENDEZ",
            "orgName": "VICTOR AGUSTIN DIAZ MENDEZ",
            "email": "mars.vic5@gmail.com",
            "curp": "DIMV970321HSLZNC06",
            "issueDate": "2024-06-26 02:58:10",
            "expiryDate": "2028-06-26 02:58:10",
            "counselRfc": "",
            "counselCurp": ""
        }
    }
}
﻿
Response Body Parameters
The detailed response includes the original input and the fetched RFC details.
Parameter
Description
Data Type
requestId
Unique identifier for the retrieval request
String
input
Object containing detailed RFC information
Object
input.rfc
RFC provided in the input
String
input.accountType
account Type provided in the input
String
input.consent
consent provided in the input
boolean
status
Status of the request, e.g., 'SUCCESS'
String
result
Object containing detailed RFC information
Object
result.rfc
RFC number as originally requested
String
result.state
Current status of the RFC whethere "Active" or not
String
result.type
Type of the RFC
String
result.curp
CURP associated with the RFC (if available)
String
result.name
Name associated with the RFC
String
result.orgName
Company name if 'PM' account type
String
result.email
Contact email associated with the RFC
String
result.issueDate
Issue date of RFC
String
result.expiryDate
Expiry date of RFC
String
result.counselRfc
RFC of the counsel
String
result.counselCurp
Curp of the counsel
String
Error Code and Response Mapping
400 (Bad Request)
400 (Bad Request)
401(Unauthorized)
403 (Forbidden)
500 (Internal Server Error)
409(Upstream Down
{
    "error": {
        "name": "error",
        "message": "Invalid RFC Number",
        "status": 400,
        "reason": "VALIDATION_ERROR",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "The RFC must be 13 characters long for accountType 'PF' (format: 4 letters, 6 digits, 3 alphanumeric characters).",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "The RFC must be 12 characters long for accountType 'PM' (format: 3 letters, 6 digits, 3 alphanumeric characters).",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "accountType can be either PF or PM",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "/rfc/ length must be 12 characters long",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "/rfc/ length must be 13 characters long",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

{
    "error": {
        "name": "error",
        "message": "Invalid RFC Number",
        "status": 400,
        "reason": "VALIDATION_ERROR",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "The RFC must be 13 characters long for accountType 'PF' (format: 4 letters, 6 digits, 3 alphanumeric characters).",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "The RFC must be 12 characters long for accountType 'PM' (format: 3 letters, 6 digits, 3 alphanumeric characters).",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "accountType can be either PF or PM",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "/rfc/ length must be 12 characters long",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}

---

{
    "error": {
        "name": "error",
        "message": "/rfc/ length must be 13 characters long",
        "status": 400,
        "reason": "VALIDATION_REQUEST",
        "type": "Bad Request",
        "statusCode": 400
    }
}
﻿
Field
Type
Description
name
string
Text displayed on the screen explaining error type.
reason
string
Reason for the error.
status
number
HTTP status code.
message
string
Error message indicating an upstream error.
type
string
Error type.
statusCode
number
Status code representing the error scenario.
Getting help
Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.
You can reach out to us at [email protected]. We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.
We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!
﻿

Parameter	Description	Optional/Mandatory	Data Type
rfc	The RFC number to retrieve data for Please see supported regex below.	Mandatory	String
accountType	Type of account, either 'PF' for individual or 'PM' for business/legal entitiy	Mandatory	String
consent	Consent to process the data	Mandatory	Boolean
callbackUrl	URL to receive the callback with results	Optional	String

Parameter	Description	Data Type
requestId	Unique identifier for the request	String
statusCode	Status code of the request (102 = Processing)	Integer
status	Status of the request, e.g., 'PROCESSING'	String

Parameter	Description	Optional/Mandatory	Data Type
requestId	The requestId returned from the first API call	Mandatory	String

Parameter	Description	Data Type
requestId	Unique identifier for the retrieval request	String
input	Object containing detailed RFC information	Object
input.rfc	RFC provided in the input	String
input.accountType	account Type provided in the input	String
input.consent	consent provided in the input	boolean
status	Status of the request, e.g., 'SUCCESS'	String
result	Object containing detailed RFC information	Object
result.rfc	RFC number as originally requested	String
result.state	Current status of the RFC whethere "Active" or not	String
result.type	Type of the RFC	String
result.curp	CURP associated with the RFC (if available)	String
result.name	Name associated with the RFC	String
result.orgName	Company name if 'PM' account type	String
result.email	Contact email associated with the RFC	String
result.issueDate	Issue date of RFC	String
result.expiryDate	Expiry date of RFC	String
result.counselRfc	RFC of the counsel	String
result.counselCurp	Curp of the counsel	String

Field	Type	Description
name	string	Text displayed on the screen explaining error type.
reason	string	Reason for the error.
status	number	HTTP status code.
message	string	Error message indicating an upstream error.
type	string	Error type.
statusCode	number	Status code representing the error scenario.

Mexico CURP Fetch

Mexico CURP Verification