OCR Verification
OCR Verification extracts identity data from document images. The customer sends photos of their ID card — front and back — through earlier Ask File nodes, and this node sends those images to a specialized service that reads the document and returns structured data: name, identification number, birth date, expiration date, and other fields printed on the card.
The service currently supports identity documents from Ecuador, Colombia, Mexico, and Guatemala. Ecuador requires both front and back images; the other countries work with just the front, though providing both sides typically yields more complete data.
Configuration
| Option | Description |
|---|---|
country | Document format to expect: EC, CO, MX, or GT |
frontImageVariable | Variable holding the front image (from Ask File) |
backImageVariable | Variable holding the back image (required for Ecuador) |
responseVariable | Where to store the OCR output |
storeInPackage | Create an audit record with images and OCR data |
saveImagesToIdentity | Attach images to an existing Identity record |
imageIdentityKey | Which identity key to attach images to (e.g., person_id) |
maxRetries | Retry attempts on failure (1-5, default 3) |
The response variable receives the complete OCR output, with extracted fields nested under a data property. To use specific values elsewhere — the identification number in a message, or the name in a Customer Update — follow with a Set Variable node to extract what you need.
Store in Package creates an audit record linked to the borrower containing the full OCR response, images, and metadata. Enable this for compliance or audit trails.
Save Images to Identity attaches the document images directly to an existing Identity record on the borrower, making them accessible from the borrower's profile. Requires imageIdentityKey to specify which identity.
Output Handles
| Handle | When |
|---|---|
| Success | OCR completed and returned extracted data |
| Error | Missing configuration, image processing failed, or extraction failed after retries |
Things to Know
Processing takes a few seconds. Typical responses come back in 2-10 seconds, but retries can extend this. Consider a "please wait" message before the node.
The extracted fields vary by country. Ecuador's cédula includes education level, occupation, parents' names, marital status — fields other countries' documents don't have. Check the response structure for your specific country.
Test mode returns mock data. The node skips the actual OCR call and returns sample Ecuador data, regardless of which country you've configured.