Connect, don't replace
Your institution's IT team will do work on their side — that is normal and expected. The quality of what we hand them decides whether that work takes two weeks or three months.
Four ways to feed the platform
Which mode applies depends on your information system, not on a prerequisite we impose. One of them requires no technical integration at all.
- Real time
Your origination journey calls NEXCLARA and receives the decision in the same request. The natural mode for integration into the origination flow.
- Batch
A set of files is processed asynchronously. Suited to volume and to loading an existing history.
- File drop
Files arrive on a secure channel in an agreed format, with quality control on entry.
- Assisted entry
No technical integration required. The analyst enters the file, with a completeness indicator flagging what is missing.
Returning the decision matters as much as receiving the request
A decision that never returns to the institution's system forces double entry, and double entry is the leading cause of a decision tool being abandoned. The same pivot model serves both directions: an adapter translates, the core stays unchanged.
- Synchronous response
The decision is returned immediately within the originating call.
- Outbound notification
NEXCLARA calls an endpoint of your institution as soon as a decision is produced or amended. Essential for asynchronous processing and portfolio alerts.
- Return file
For a processed batch, a results file in the agreed format, delivered to your secure channel.
- Query interface
Your system queries NEXCLARA to retrieve a past decision and all of its elements.
- Analytical export
Periodic extraction into your business intelligence, for your own risk analysis.
- Decision document
A formatted, digitally signed document, filed with the credit application and admissible in audit.
Four ways to feed the platform
- Real time
- Batch
- File drop
- Assisted entry
One internal representation, in both directions. An adapter translates; the engine does not change.
Returning the decision matters as much as receiving the request
- Synchronous response
- Outbound notification
- Return file
- Query interface
- Analytical export
- Decision document
A decision that has been produced is never lost
An outbound notification that fails must not make a decision disappear. The mechanism is designed for that.
- Persistent queue: delivery survives a restart.
- Retries with increasing back-off, without saturating your system.
- A failure log you can consult, and manual replay when needed.
- Message signing, so your institution can verify the authenticity of what it receives.
What your IT team receives
An integration document is produced for every institution. A well-equipped integrator becomes the project's strongest internal advocate.
- The interface specification, versioned.
- File formats, with complete examples.
- The field mapping agreed with your teams.
- Error codes and their exact meaning.
- Authentication arrangements and rate limits.
- A test environment populated with synthetic data.
An unavailable source does not block the decision
If a data source is temporarily unreachable, the platform neither stops nor invents: it produces a decision in degraded mode, explicitly flagged as such, stating what was missing. An analyst then knows whether to conclude or to wait.