TensorFrog

Projects — systems we implement

Six flagship scopes written the way they enter an offer: payments, documents, reporting, KSeF, mail and SMS, and ticketing. We structure the code with SOLID so the next stage does not break the last one. Price and start — after a separate quote.

Payments

System płatności

PayU, Przelewy24, ING imoje — keys, transaction flow, verification and refund of funds after a product return.

Documents

Document management system

Report design

In-app reports — designer and API

After-sales and settlement reports — ActiveReports or open source, PDF, Excel and API.

KSeF

KSeF i systemy księgowe

KSeF 2.0 API, FA(3), receive and issue of e-invoices and a flow in the accounting system.

Mail and SMS

Mail and SMS platform

Mail and SMS, queues, an API for company software and AI analysis — one log instead of inboxes and gateways beside each other.

Ticketing

Ticketowanie i call center

Queue, case card and call center — phone and mail in one case, wired to the mail system.

How we structure the code

SOLID in systems that stay in the company

A system should outlive one stage. We split the code so the next integration does not break the last one. Practice in assembling modules — not a lecture.

One responsibility

A class or module has one responsibility. The next task goes into a separate piece of code; it does not swell what already works.

Extend without breaking the core

A new feature arrives as new code beside the existing contract. The core stays.

Depend on an interface

Code leans on an interface and a contract, not on a concrete implementation. A layer can be swapped without rewriting the rest.