Skip to main content
JSON files contain data structures specifying the number, types, and names of the documents, as well as the number and names of the pages for each document. To configure mobile upload for a specific user’s scenarios, use the JSON file in the mobile upload link. The md parameter can accept a JSON file in two formats: direct encoded link or encoded JSON. To use an encoded link:
  1. Generate a direct access link to the JSON file.
The link should start with “http://” or “https://”.
  1. Encode the obtained link to URL-encoded format.
  2. Specify the encoded URL as the value for the md parameter in the mobile upload link.
To use an encoded JSON:
  1. Encode the JSON file to URL-encoded format.
  2. Specify the encoded JSON file as the value for the md parameter in the mobile upload link.

JSON structure

TransactionStructure defines a set of documents expected to be captured by the user during a mobile upload session for further processing in a transaction. The transaction will not start until all documents are captured. ElementStructure defines a collection of one or multiple sets of documents expected to be captured by the user for further processing in a transaction. DocumentStructure defines a collection of the properties for each document in the set. PagesStructure defines a collection of properties for the document pages expected to be captured by the user.

JSON sample

This JSON sample defines the document structure for a bank application. The following document pages are expected to be captured by the user during a mobile upload session for further processing in a transaction:
  1. The first page of the passport.
  2. All pages of the application.
  3. Proof of residence, which includes pages of the rental agreement or pages of the utility bill.