How It Works

The verification lifecycle: collect consent, start a verification, receive a webhook, and fetch the data.

Every verification follows the same four-step flow. Use an 18-char CURP for individuals or a 12-char RFC for businesses — the same flow applies to both.

1. Collect consent

Every verification needs the data owner's consent. First, contact support to register your company's privacy notice.

Have your user accept that privacy notice and capture the IP address from which they accepted it. Send that ip_address with the verification in step 2 to record consent under your company's registered privacy notice.

For the requirements, see Consents.


2. Start a verification

Send the identifier together with the customer's phone and email, and the ip_address from which they accepted your privacy notice. The rfc is optional — for individuals you can include it to increase the probability of recovering invoice data.

Individual (CURP):

POST /verifications

{
  "identifier": "CUAI911021MOCRQS09",
  "rfc": "CUAI911021ABC",
  "phone": "+525512345678",
  "email": "[email protected]",
  "ip_address": "201.141.22.10"
}

Business (RFC):

POST /verifications

{
  "identifier": "MNT850612KR4",
  "phone": "+525512345678",
  "email": "[email protected]",
  "ip_address": "201.141.22.10"
}

Each request that includes ip_address records a new consent for that verification only. Include it in every verification request. The initial response returns status: "in_progress" and the consent_id.


3. Receive a webhook

When processing finishes, BDI sends a verification.completed webhook to your registered endpoint.

Individual webhook:

{
  "event": "verification.completed",
  "verification_id": "01982e40-d53a-7560-8c69-ddb96bd9ca8c",
  "identifier": "CUAI911021MOCRQS09",
  "status": "completed",
  "data_available": true,
  "can_retry": false,
  "entities": ["profile", "invoices", "employment"],
  "last_updated_at": "2025-07-24T10:01:30Z",
  "timestamp": "2025-07-24T10:01:30Z",
  "external_id": null
}

Business webhook:

{
  "event": "verification.completed",
  "verification_id": "5fc3a4d1-7e2b-4d8a-9c0e-1f5b8d2a3e74",
  "identifier": "MNT850612KR4",
  "status": "completed",
  "data_available": true,
  "can_retry": false,
  "entities": ["business_profile", "invoices"],
  "last_updated_at": "2025-07-24T10:02:15Z",
  "timestamp": "2025-07-24T10:02:15Z",
  "external_id": null
}

For delivery, retries, and signature verification, see Webhooks.


4. Fetch the data

Once the webhook arrives with data_available: true, iterate over entities and fetch from each corresponding endpoint.

Individual (CURP):

  • GET /profile/CUAI911021MOCRQS09
  • GET /invoices/CUAI911021MOCRQS09
  • GET /employments/CUAI911021MOCRQS09

For individuals, also call GET /estimates/CUAI911021MOCRQS09 to get the estimated monthly income, employment status and tenure. It isn't listed in entities, and it isn't billed. See Estimates.

Business (RFC):

  • GET /business-profile/MNT850612KR4
  • GET /invoices/MNT850612KR4

For the full Verification object and the entities reference, see Verifications.


Batch verifications

Need to verify many identifiers at once? Send them all in a single request to the bulk endpoint instead of calling /verifications one by one. See Bulks for the full payload and limits.


Test your integration

Use the Sandbox to validate your integration end to end with fictitious but valid-looking identifiers.


Get API access

Contact us to request a demo account and receive your API key.


Did this page help you?