Submitting Captured Data

After you receive a response from the /start endpoint, the next step is to submit captured data to another endpoint. Captured data might be in the form of a barcode, a front image, or a back image from the identification document. You must submit different types of captured data based on the combination of document_type and signals in the /start request.

For example, suppose you submitted na_dl as the document_type along with idcheck in the signals array. This is a common combination used to verify the barcode of a North American driver license. The /start endpoint returns a transaction_id value. You could next use the /submit-barcode endpoint to submit transaction_id along with barcode, which is a base64-encoded string of the barcode data from the backside of the driver license.

👍
Our Direct customers must capture and encode the document images separately.

The following table shows the capture data requirements for common document_type and signals combinations.

Document Type	Signals	Barcode	Frontside of ID	Backside of ID	Selfie
`na_dl`	`idcheck`	Yes or Backside of ID	No	Yes or Barcode	No
`na_dl`	`idcheck` with `ocr_scan`	Yes or Backside of ID	Yes	Yes or Barcode	No
`na_dl`	`idcheck` with `ocr_match` and `ocr_scan`	Yes	Yes	Yes	No
`na_dl`	`selfie` with `ocr_scan`	No	Yes	No	Yes
`passport`	`ocr_scan`	No	Yes	No	No
`passport`	`ocr_match` with `ocr_scan`	No	Yes	No	No
`other`	`ocr_scan`	No	Yes	Yes	No
`other`	`ocr_match` with `ocr_scan`	No	Yes	Yes	No

👍Our Direct customers must capture and encode the document images separately.

👍
Our Direct customers must capture and encode the document images separately.