INTEGRATIONS

Integrations with explicit status of each connection.
Each integration has a clear status: available, awaiting configuration or requiring provider credentials.

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.

Key features: Integrations

Public supplier status

The panel separates configuration recording, connection test result and integration enablement.

Secrets only on the server

Vendor keys are encrypted on the server. They don't go to the browser or APKs.

Versioned contracts

Adapters have a specific contract and interface version. Changing the supplier's API requires a new acceptance.

Permissions checked by API

Only the organization administrator can change the integration configuration. Hiding the button is not the only security feature.

OpenStreetMap Maps

MapLibre and OSM data work with required attribution.

REAL SCREENS

This is what it looks like
in the working version.

  • Payments and invoicesStripe, Przelewy24 and Fakturownia configured by the administrator: test or production mode, connection test, invoice settings.
  • Operational mapLocations, route plans and fleet positions. Actual positions require a GPS connection.
  • Operations dashboardcollections, fleet, notifications and PSZOK on one screen, with access to details.
Actual product screens: Payments and invoices. Click on the screen to see the next one.
HOW IT WORKS
  1. 01Supplier selection

    We identify the vendors used by the organization and their test environments.

  2. 02Configuration

    The administrator enters the keys in the panel. Changing fields invalidates the previous test.

  3. 03Connection test

    The test checks API access without creating a payment or document.

  4. 04Acceptance testing and activation

    After checking the actual flow, the administrator enables the integration.

LifeNexa CORE

SSO, licenses and subscription settlement. The development adapter is running in the pilot; production connection requires an agreed contract.

Requires a provider
Stripe

Hosted Checkout and signature verification notifications. The administrator enters the keys and performs a connection test.

To be configured in the panel
Przelewy24

Transaction registration, CRC check and verification confirmation. Requires an organization operator account.

To be configured in the panel
Fakturownia

Issuing invoices, PDF and payment synchronization. Requires an API token and an issuer department in your organization's account.

To be configured in the panel
BDO

Draft records and validation are available. Submission requires the organisation's credentials and API compliance acceptance, including after the 2027 changes.

Requires a provider
KSeF

Requires separate workflow, authorizations and tests. Not connected yet.

Requires a provider
GPS and telematics

An adapter for the provider selected by the organization. Actual positions appear after that provider is connected.

Requires a provider
RFID, QR and NFC

Identifiers are in the register. Hardware readers require an adapter and on-device testing.

Requires a provider
Scales

The weight is entered manually and marked as such. Certified scale requires an adapter.

Requires a provider
Email, SMS and push notifications

In-app notifications are available. Notifications outside the app require a configured provider.

Requires a provider
Maps (MapLibre/OSM)

Operational map with OpenStreetMap data and attribution. Lists also work without a map.

It works
NexaCity OS

Planned exchange via API and events, without copying the municipality's database. Not connected yet.

Requires a provider
SCOPE IN PILOT VERSION

What works today,
and what requires configuration.

Running on the system
  • MapLibre/OSM maps
  • Stripe, Przelewy24 and Fakturownia
  • PDF, XLSX, CSV and GeoJSON exports
  • In-app notifications
Requires your or provider details
  • GPS/telematics, scales and RFID/NFC readers – adapters for organizational equipment
  • BDO and KSeF require the organisation's credentials and compliance acceptance testing.
  • Email, SMS and push notifications require a configured notification provider.
  • LifeNexa CORE (SSO, licenses) and NexaCity OS (API and events)

Frequently asked questions

Awaiting configuration

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.

Can you connect our GPS provider?

We select the adapter according to the supplier's devices and API. We enable it after the test on the organization's keys.

Does NexaWaste copy data from municipal systems?

No. Integration with NexaCity OS is planned as an exchange via API and events, without copying the municipality's operational database.

LET'S START WITH YOUR NEEDS

A cleaner city.
A more efficient team.
Let’s talk.

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.

Presentation of real screensScope tailored to processesClear stages and acceptance criteria

Operational contact does not require marketing consent.