DEVELOPERS
Integrate AC with the systems you already use.
ACPROTOCOL & ORACLE was designed to operate alongside the institution’s existing infrastructure. Banking systems, ERPs, document management, registry platforms, public systems and in-house applications keep performing their functions and start using AC as an additional layer of canonical identity, query and correlation.
What the integration will enable
- Register an occurrenceSend a new occurrence to the protocol.
- Query an identityLocate the canonical identity associated with the available information.
- Check the current stateQuery the state made available for that identity.
- Follow the timelineQuery occurrences and events associated with the asset.
- Integrate institutional systemsExisting applications use AC answers within their own flows.
The institution sends the occurrence or the query and receives the corresponding answer.
Integration alongside your systems
Canonical Identity for institutional and corporate assets — banks, brokers, city halls, notaries, companies and institutions connected by a single identification infrastructure. The institution keeps control of its operation, its documents and its internal processes.
1. Origin
The document or data originates in the institution’s own system.
2. Integration
The occurrence reaches AC through local processing, structured integration or API.
3. Identity
The protocol relates the occurrence to the applicable canonical identity.
4. Answer
The institutional system receives the information to continue its own flow.
Occurrence
A representation of an asset that was received.
Identity
The persistent ACIDN associated with the asset.
State
The condition recognized at that moment.
Event
A recognized occurrence that takes part in the asset’s evolution.
| Input | Public answer |
|---|---|
| Document, structured data or institutional occurrence | ACIDN, when determinable |
| Occurrence context | UNI · DUP · PAR · QTN · INL |
| Asset class, when applicable | Recognized state, when applicable |
| Institutional source | Reference to evolution and timeline |
The public surface delivers protocol results. The proprietary logic of generation, correlation and decision remains encapsulated in the AC core.
- The same identity follows the asset over time.
- Different representations can correspond to the same identity.
- The client application consumes the protocol’s public answer directly.
- Integrations preserve version, origin and traceability of the occurrence.
Product stage: What has been developed — and what's roadmap →
How your institution joins
On-premises deployment
Processing takes place inside the institution’s own environment. Suited to operations that require greater control over documents, data and infrastructure.
Dedicated environment
An environment reserved for a specific organization or operation.
Institutional API
Existing applications and systems communicate with AC services. Suited to bringing queries and registrations into their own digital flows.
Hybrid model
Combines local processing with control, update and integration services, adapting the deployment to each operation’s requirements.
The availability of each model follows the product stage, the institution’s needs and the technical requirements of the deployment.
Early access
APIs and SDKs are under development. Selected institutions, technology partners and developers will be able to join the early access program for integration, testing and validation of real cases.
Request technical implementation details and documentation for AC partner developers and programmers.
