Skip to content
Cultural venue box office with a payment terminal

Integrations

Connected, with clear boundaries.

NexaCulture has its own domain database and uses LifeNexa Enterprise contracts. Payments and documents use the institution's accounts.

S

Stripe

Card payments for tickets, with verification of the payment provider's notifications.

Credentials entered by the administrator
P24

Przelewy24

Instant bank transfers and BLIK for online sales. Refunds use a separate callback.

Credentials entered by the administrator
F

Fakturownia

Invoices and sales documents using recorded VAT rates and status checks.

Token entered by the administrator
LN

LifeNexa CORE

SSO, organisations, subscriptions and product permissions.

Requires an active CORE connection
@

Email and push notifications

Notifications in the portal. External email and push delivery require separate deployment configuration.

Configured during implementation
A

Android

A native app for attendees, staff and managers, with an offline queue.

Online payment flow

  1. The visitor chooses seats and the system places a hold.
  2. Payment is made through the institution's Stripe or Przelewy24 account.
  3. The provider sends a signed notification (webhook).
  4. NexaCulture verifies the signature and amount, then issues the ticket exactly once.
  5. Fakturownia creates the invoice with fixed line items and VAT.

For IT teams

  • REST API with OpenAPI documentation
  • Webhooks with signature verification and idempotency
  • Queued retries and manual resumption
  • CORE contracts: organisations, permissions and subscriptions
  • No direct database-to-database connections between products
  • Integration status reports: active, test and unconfigured
OpenAPI specification
Audience in front of a concert stage

See how NexaCulture can work for your institution.

Android app