What's new for July 2025

Sign up to recieve these product updates directly to your email here

New API support portal for our API clients

We have launched a new dedicated API support portal which will host all API documentation to support you with Credas integrations. Previous API documentation will be removed from the current portal w/c 14th July

Tell us what you think

Please take a moment to fill out our quick, anonymous form to share your thoughts on our support, guides and training. Your feedback helps us improve and better support you: click here.

Coming Soon: Smarter Document Matching! 

We will soon (estimated mid July) be introducing updates to enhance the integrity of identity verification by ensuring the right identity documents are used every time. This will:

• Reduce the risk of incorrect document uploads
• Improve check accuracy and processing time
• Provide clearer guidance to individuals during their verification journey? 

What's changing for you in the Credas portal?

Highlighting mismatches in results - To help you stay on top of documents discrepancies, new alerts will be introduced in the Client Portal when an uploaded document does not match the selected document type and isn't valid for the journey configuration. 

In some rare cases, like when upload attempts are exceeded, users may still submit an incorrect document. In these rare cases, the mismatch in document type will be clearly flagged. 

You will notice:

• A new 'mismatch check' appearing in the identity document results (both in the portal and on PDFs)
• A warning icon labelled 'mismatch' along with a message: ''the provided document type does not match the selected document type''

Results will be labelled as:

• Pass - The document selected matches the document provided
• Fail - The document selected does not match what was provided
• Not performed - The mismatch check was not run (e.g., the check occurred before this feature was introduced)
• Unknown - The mismatch check could not determine the document type

What's changing for individuals completing the checks?

When an individual selects an identity document type (e.g., passport) but attempts to capture a different document (e.g., driving licence), they will now be promoted to either:

• Upload the correct document type, or
• Go back and select a valid alternative from the list

This aims to reduce confusion, errors and improve check success rates.

What's changing for API clients?

When the uploaded document does not match the selection and is not a valid configured required document type - but does manage to be submitted - and is flagged as a mismatch we will highlight this in the API:

• API responses will include a document_type_mismatch flag when applicable
• A descriptive error message will be included detailing the mismatch
• The API response will remain consistent with schema expectations, with clear documentation

Endpoint affected:

• /api/v2/ci/entities/{entityId}/idv-entries
• /api/v2/ci/entities/{entityId}/idv-entries/{entryId} 

Once updated in the IDV entry itself, any endpoint that returns the IDV entry will include the new IDV entry object where applicable such as

• /api/v2/ci/processes/{processId}/details

• /api/v2/ci/entities/{entityId}/summary

• /api/v2/ci/entities/{entityId}/active-checks

Source of Funds changes

After hearing your feedback, we have updated our Source of Funds journey, your client will be able to declare how much they are receiving from the sale of a property (once any mortgages, loans and other charges etc. have been satisfied), to get better clarity for you on the individuals source of funds.

Other enhancements we have made to our Source of Funds journey over the last few months include:

• Adding a back button for easier navigation during Open Banking
• Including percentages in Source of Funds reports for clearer insights
• Displaying bank account holder names in Open Banking

If you would like a demo of our Source of Funds solution to see how it could work for your business contact sales@credas.com