API Documentation

User Interface Restrictions

Although CorePro is essentially just an API, banking partners have some user interface restrictions that, by law, must be followed.

The user interface restrictions apply to all user-facing applications that consume CorePro. e.g. desktop browsers, mobile apps or browsers, etc.

When using CorePro to perform identity verifcation for on-boarding customers:

  1. The html for the document type of eStatement (aka e-Sign) must be displayed first and in plain text or html.
  2. The user must accept the e-Sign document by clicking a checkbox, button, or link.
  3. After the e-Sign document has been accepted, all other required bank documents returned via /bankdocument/list must be viewable by the user (available in html or pdf format).
  4. The user must perform an action to signify acceptance of each and every document.
Note: By passing isDocumentsAccepted as true to /customer/initiate, your code is signifying the user has performed actions outlined above. i.e.: The user has read and accepted all documents.


  • All statements returned from CorePro's /statement/list route must be accessible

    Note: This includes both Monthly bank statements and Year end tax statements, distinguished via the type property on each statement object returned.


  • Display a listing of all transactions (by account) returned from CorePro's /transaction/list route, for every CorePro account assigned to that user.
  • If the nachaDescription of a transaction contains a value, it must be displayed to the user. Otherwise, the FriendlyDescription should be used.

    Pseudo-Code Example
                    var myDescription = transactionItem.FriendlyDescription ;
                    if (!string.IsNullOrEmpty(transactionItem.NachaDescription))
                       myDescription = transactionItem.NachaDescription;

Lincoln Savings Bank Requirements

Ready to start a conversation?

Email Us