Using a previously uploaded but incomplete document, you can optionally supply updated details (such as corrections on a previous scan), along with one or more additional ID scans (e.g. additional pages).
The documentId returned previously from an earlier call to /check or /entity or /document
Customer ID issued by Frankie Financial. This will never change. Your API key, which is mapped to this identity, will change over time.
If, as a Frankie Customer, you are acting on behalf of your own customers, then you can populate this field with a Frankie-assigned ID.
Note: If using a CustomerChildID, you will also need a separate api_key for each child.
Any documents, checks, entities that are created when this field has been populated will now be tied to this CustomerID + CustomerChildID combination. Just as Customers cannot see data created by other Customers, so too a Customer’s Children will not be able to see each other’s data.
A Customer can see the documents/entities and checks of all their Children.
If this header parameter is supplied and set to 1, then the request will not wait for the process to finish, and will return a 202 if there are no obvious errors in the input. The request will then run in the background and send a notification back to the customer. See out callback API for details on this.
See more details here: https://apidocs.frankiefinancial.com/docs/asynchronous-calls-backgrounding-processes
Open string that can be used to define the “channel” the request comes in from. It can potentially be used in routing and risk calculations upon request. Default values that can be used are:
Any alphanumeric string is supported though. Anything over 64 characters will be truncated.
Disable check result invalidation for this update request.
The ISO-3166-alpha3 country code of the issuing national. Once set, this cannot be changed.
See https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes for more
Valid ID types
This document’s data was initially created from scanned and processed images. The value cannot be set manually and any attempt to do so will just be ignored.
Collection of one or more objects that describe scan(s) that need to be put through OCR or facial recognition. These should all be from the one ID document, such as front/back, or page 1, 2, 3, etc. You can upload multiple scans in a single call, or in multiple calls.
Note: if you do upload over multiple calls, make sure you include the documentId (see above), and indicate that this is happening with a “more_data” checkAction
When an ID document is created/uploaded, it is assigned a documentId. You’ll see this in a successful response or successfully accepted response. This can then be referenced in subsequent calls if you’re uploading more/updated data.
Current status of a document.
Set of key-value pairs that provide ID type-specific data. If updating an existing document, then existing values with the same name will be overwritten. New values will be added.
If this document is scanned through OCR or similar processes, then extracted data will be found here (Some may be used to populate other fields like idNumber and idExpiry as well)
The expiry date of the document (if known) in YYYY-MM-DD format.
The issued date of the document (if known) in YYYY-MM-DD format.
The ID number of the document (if known).
The sub-type of identity document. Very document specific.
If this document was originally populated from scanned data, then manually adjusted (e.g. if the scan’s results weren’t 100% correct or data was missing), then this will be set to true. The value cannot be set manually and any attempt to do so will just be ignored.
Regional variant of the ID (e.g. VIC drivers licence)
You should always use the local abbreviation for this. E.g.
The request was valid and able to be processed in some fashion. Results may or may not be successful, but it was completed as far as practical with no actual errors. Returns the document object as it stands now. No docScan file data will be returned unless the /full variant is requested.
Unique identifier for every request. Can be used for tracking down answers with technical support.
Uses the ULID format (a time-based, sortable UUID)
Note: this will be different for every request.