Skip to main content
All CollectionsDesktop
PALIDIN Custom Field Feature
PALIDIN Custom Field Feature

How to use the custom field option in PALIDIN Desktop

Allie Roberts avatar
Written by Allie Roberts
Updated over 4 months ago

Organizations may at times need to associate a data point like a driver#, employee name, or employee# to a particular transaction. PALIDIN’s custom field feature allows you to configure up to two custom fields, which are then associated with the record related to a specific identity document authentication transaction.

The custom field feature provides two setup options: (1) Validation, (2) Regular Expression. The validation option allows you to configure the custom field using common validation tests like field type, field length, support for special characters, etc. The Regular Expression (RegEx) option allows you to configure the custom field using more advanced validation processes.

Once the feature is enabled and configured, the user will be prompted to enter the data point and it will be associated with the historical record. The following screenshots summarize the process from setup, user prompt display, to displaying the custom field in the transaction report.

Two custom fields setup in the PALIDIN app. Custom field 1 uses the validation approach and custom field 2 uses the RegEx approach

User is presented with prompt to enter guest's last 4 digits of SSN and the current Canadian postal code

Transaction Report displaying the two custom fields setup in the system.

The flexibility of the custom field feature means that it can be implemented in a broad range of situations. For instance:

  • Shipping & Receiving: entering a driver pickup code when entering a warehouse.

  • Credit Unions: creating a record confirming that a guest’s identify was verified for shared branching transactions.

  • Auto Dealerships: entering a deal or loan# during the loan approval process.

  • Or any other situation where a custom data point needs to be associated to an authentication record.

  • Detail instructions on how to setup this feature can be found on the PALIDIN System Manual.

Note: currently, the custom field is only integrated into the transaction report. In future releases, it will be integrated into other historical records (e.g. local database file, and PALIDIN Enterprise records)

If you have questions, please contact support by:

Monday-Friday 7AM - 5PM PST

Did this answer your question?