Valida INE, CURP and identity information before advanced
Confirms information about his or her public information about his or her official sources before approving his or her release, operation, contract or file. KYC complete when you don't have to.
- CURP
- INE
- RFC
- PLD/AML
- API
Examples: No actual personal data are shown.
Capturing a data doesn't mean validation.
Name, CURP, RFC or a credential can be properly captured and still require confirmation before using them to make a decision. JAAK allow to add a time validation exactly where your process needs it.
REGISTRATION
The user provides his data.
VALIDATION
JAAK check with the appropriate source.
DECISION
Your system gets a structured result to continue the process.
Valid only what you need
Confirm a CURP against RENAPO
Valid existence and status of CURP and get available data associated with registration.
- Existence of registration
- Estatus
- Associated data
- Resultado estructurado
- Operating ID
Valids a Credit to Vote
Incorporates additional credential validation INE within your identity processes.
- Credit Validation
- Response information
- Resultado estructurado
- Integration through API
- Evidence of operation
Valids fiscal information
Incorporates validation related to RFC within your information release, compliance or update processes.
CONOCER VALIDATION RFC →Research individuals and businesses into risk lists
Check compliance lists and add a scrolling layer as your operation requires.
_Not every process needs a KYC complete
It starts with a punctual consultation and adds new layers as the risk of operation increases.
_
A consultation.
ONBOARDING LIGERO
Confirm data before creating an account or file.
FUNCTION OF EXPEDIENTS
Unrepeated information KYC complete.
FURTHER
Check data before entering a new supplier.
EMPLOYMENTS
Add validations to some high processes.
FIRE OF CONTRACTS
Valids information before starting a signature flow.
FUNCTIONING
Add focused consultations within processes PLD/KYC.
The applicable validations depend on the process, sector and regulatory framework of each organisation.
Don't just get an answer. Keep the operation context.
In sensitive processes, knowing the result is only a part. It also matters to be able to rebuild what validation was performed and when it happened.
Consumption JAAK as you have to
PLATAFORM
Realizes operations from the environment JAAK When you don't have to develop an integration.
API
It integrates validations directly into your products and processes.
HIGH VOLUME
Design a configuration commensurate with the volume and operational needs of your organization.
POST /api/v1/official-list/mx/curp/validate
Authorization: Bearer <api-key>
{
"curp": "XXXX000000XXXXXX00"
}
200 OK
{
"isValid": true,
"eventId": "evt_xxxxx"
}A consultation can be just the beginning
_
Building an appropriate level of confidence for each operation without duplicating providers, integrations or flows.
FAQ
They're called API independent and validating an information about an identity or compliance -CURP, credential INE, RFC or a person / undertaking against risk lists - against the appropriate source, without a verification session KYC complete.
No. Validation of CURP against RENAPO an atomic consultation: you send the data and get a structured result at the same call. KYC complete (document, biometrics, lists, file) is a different flow for when you have to fully check a person.
That's right. CURP independently from the rest of the Official Consultations or from biometric KYC.
Yeah, by the front image of the credential. JAAK It removes data and validates its status against the electoral status of the National Electoral Institute.
A public consultation is an individual HTTP call: you provide data (or an image of the credential) and get an immediate result. KYC It's a session flow with several phases - document capture, biometrics, liveness detection, lists - intended to fully verify a person's identity.
Yes. Each query is an endpoint REST authenticated with API Key (Beaner token) that you can invoke directly from your backend or from the Platform JAAK without developing an integration. API requires a Setup fee and enabling share as required by terms and conditions and using from the web platform does not require integration.
Yes. Each consultation is independent, so you can invoke one, several or all within the same process, depending on the level of risk of the operation.
Yes. The availability of a testing environment is evaluated with a commercial specialist JAAKAccording to the type of integration, project needs and terms and conditions that have been contracted. Access isn't automatically enabled by buying autoservice packages.
Validate data and then decide.
It starts with a timely consultation or builds a complete process of monitoring with JAAK.
See documentation API →