Public supplier status
The panel separates configuration recording, connection test result and integration enablement.
The platform distinguishes between working integrations, integrations configurable by an administrator and those requiring a provider. Payments and invoices are configured in the workspace. GPS, BDO, KSeF, scales, RFID and outbound notifications require credentials, an adapter and acceptance testing.

The panel separates configuration recording, connection test result and integration enablement.
Vendor keys are encrypted on the server. They don't go to the browser or APKs.
Adapters have a specific contract and interface version. Changing the supplier's API requires a new acceptance.
Only the organization administrator can change the integration configuration. Hiding the button is not the only security feature.
MapLibre and OSM data work with required attribution.
We identify the vendors used by the organization and their test environments.
The administrator enters the keys in the panel. Changing fields invalidates the previous test.
The test checks API access without creating a payment or document.
After checking the actual flow, the administrator enables the integration.
SSO, licenses and subscription settlement. The development adapter is running in the pilot; production connection requires an agreed contract.
Hosted Checkout and signature verification notifications. The administrator enters the keys and performs a connection test.
Transaction registration, CRC check and verification confirmation. Requires an organization operator account.
Issuing invoices, PDF and payment synchronization. Requires an API token and an issuer department in your organization's account.
Draft records and validation are available. Submission requires the organisation's credentials and API compliance acceptance, including after the 2027 changes.
Requires separate workflow, authorizations and tests. Not connected yet.
An adapter for the provider selected by the organization. Actual positions appear after that provider is connected.
Identifiers are in the register. Hardware readers require an adapter and on-device testing.
The weight is entered manually and marked as such. Certified scale requires an adapter.
In-app notifications are available. Notifications outside the app require a configured provider.
Operational map with OpenStreetMap data and attribution. Lists also work without a map.
Planned exchange via API and events, without copying the municipality's database. Not connected yet.
The integration is ready to run in the system, but requires organization keys and a connection test. Does not represent confirmed activity on a real account.
We select the adapter according to the supplier's devices and API. We enable it after the test on the organization's keys.
No. Integration with NexaCity OS is planned as an exchange via API and events, without copying the municipality's operational database.
Choose a product and a conversation topic. The request will receive a number and go to the service center; We will respond to the address provided.