The hard integrations are already done
Payments, e-signing, identity, email, storage and analytics are implemented against real providers — including Baltic-specific services that are non-trivial to build from scratch.
Montonio Payments
Baltic online checkout via the Orders API, with signed order requests and resilient HTTP. Manual/cash capture is also supported.
Dokobit E-signing
Documents Gateway flow: upload → create → poll, producing a PAdES-signed PDF stored as the legal record.
SK Smart-ID & Mobile-ID Identity
Estonian/Baltic identity verification. Personal codes are stored HMAC-only, never in plain text.
Resend Email
Transactional and operational email over REST, delivered through a retried outbox worker with status visibility.
Cloudflare R2 Storage
S3-compatible object storage for contract templates, generated/signed PDFs, invoices and model imagery.
Sentry Monitoring
Error monitoring across backend and frontend, with token-redaction hooks so secrets never reach breadcrumbs or events.
PostHog + GA4 Analytics
Product analytics and web analytics, both consent-gated — they load only after explicit consent and when configured.
QuestPDF + OpenXml Documents
Invoice rendering via QuestPDF and contract docx→PDF generation via OpenXml with a headless LibreOffice conversion step.
OpenTelemetry Tracing
Tracing and metrics exporters, inert until an OTLP endpoint is configured — ready for the acquirer's observability stack.
Env-gated and safe by default
Every integration follows one pattern: configuration is read lazily inside each client, and when keys are absent the integration is inert — no calls, no crashes. A staging or local instance with no secrets runs safely and degrades gracefully.
This makes the codebase easy to evaluate: a buyer can stand it up with zero third-party credentials, then enable providers one at a time.
What transfers vs what doesn't
- Transfers: the integration client code and flows (payment signing, e-sign gateway, identity, storage recipe, consent-gated loaders).
- Does not transfer: the live provider accounts, keys and secrets.
The acquirer stands up fresh provider accounts and supplies their own secrets. No live keys are part of the package.
Review the integration code
The acquisition pack details each client, its configuration surface and the provider flows. Book a demo to see payments and e-signing run end to end.