01
Analysis
We understand the product, users, flows of funds and systems involved.
FINTECH SOFTWARE DEVELOPMENT
Connect payments, dataand financial processes.
We build dedicated FinTech software for digital payments, financial administration and integrated services. From customer apps to admin platforms, we deliver solutions with clear control over transactions, access and data.
Operations dashboard
Recent transactionsIllustrative view
- Payment request
- Provider confirmation
- Booked
- Reconciled
- PAY-2042Invoice #F-311€48.00Pending
- PAY-2041Subscription · Pro plan€29.00Captured
- PAY-2040Order #8812€64.50Partially refunded
- PAY-2039Payment link€120.00Failed · retry
Provider reconciliation
Awaiting reportOperational notice
1 payment needs review
Payment details
Demo Shop
€48.00
Ref. PAY-2042
Awaiting confirmation
Customer returned from the payment page
Activity
- Payment PAY-2042€48.00
- Refund RF-301−€10.00
- Integrations with financial providers
- Traceable actions
- Architecture built to grow
DEDICATED SOFTWARE
Software built around the logic of your financial business.
When payments, customer data and reports live in disconnected systems, control gets harder and manual work grows.
At ENOR, we build platforms that connect these processes and define exactly what happens at each step. We design simple interfaces for customers and detailed tools for the teams that manage transactions, verifications and operations.
Exchange
Illustrative viewCustomer
Your platform
App
Admin platform
Reporting
Outside the platform
Financial provider
Each system receives only the data it needs. Boundaries are set during analysis.
PROBLEMS WE ADDRESS
More control over processes that can’t afford ambiguity.
Each difficulty maps to a specific platform function.
Today: Payments with unclear status
With a structured platform: Verifiable status and historyToday: Manual reconciliation across several sources
With a structured platform: Structured matching and handling of differencesToday: Duplicated data
With a structured platform: Integrations and defined sources of informationToday: Changes without a trail
With a structured platform: Action history and authorisationsToday: Reports that mix billing with receipts
With a structured platform: Indicators separated by financial meaningToday: Platforms that are hard to extend
With a structured platform: Modules and interfaces designed for new integrations
FINTECH SOLUTIONS
What we can build for your business.
Modules chosen and combined around your product.
Digital payments
Integrations for collections, subscriptions, refunds and reconciliation.
Learn more
Digital wallets
Apps for balances, history and use of funds or credits, depending on the service model.
Learn moreFinancial portals
Interfaces for customers, partners and operations teams.
Learn moreLoan management
Processes for applications, documents, review and repayment administration.
Learn moreInsurTech
Platforms for insurance quotes, policies, documents and claims handling.
Learn moreKYC & RegTech
Verification integrations and controlled review processes.
Learn moreFinancial analytics
Dashboards, reports and indicators with clear data sources.
Learn moreEmbedded finance
Financial providers’ services integrated inside your product.
Learn moreAI for financial operations
Document processing, classification and flags for review.
Learn moreModernisation and integrations
Connections between apps, existing systems and external providers.
Learn moreFor regulated functions, the technical build follows the operating model, the operator’s licences and the relevant financial partners.
DIGITAL PAYMENTS
From payment request to reconciliation.
We build the full payment flow, with distinct statuses you can verify at every step.
- Payments on websites and in apps
- Payment links
- Subscriptions and recurring payments
- Authorisation and capture, when the provider supports them
- Full or partial refunds
- Handling of failed attempts
- Dispute handling, where offered
- Fees and net amounts
- Reports and exports
PAY-2042 · €48.00Illustrative view
Awaiting authorisation
Idempotency key: ord-8812-1
Events
- payment.created · from the server
The net amount is calculated after capture
Try returning to the success page, the webhook, its repeat and a partial refund.
How we handle it technically
- Server-side confirmation
- Status comes from the provider in the backend, not from the page the customer returns to.
- Webhook verification
- Every notification is verified using the provider’s mechanism, e.g. a signature.
- Amount, currency and identity
- Checked against the order before a payment is marked as completed.
- Idempotency
- Repeating a request never creates a second payment or refund.
- Late or out-of-order events
- Status only moves along allowed transitions.
- Periodic reconciliation
- Data is compared with the provider’s reports.
The status in the browser is not a source of financial confirmation. A payment is marked completed only after the provider confirms it.
PAYMENT PROVIDER INTEGRATIONS
Integrations with the services you use or plan to use.
We connect the providers you choose, after checking their current documentation and the integration methods they offer.
Providers that can be assessed
- POK
- PayPal
- Stripe
- Paysera
- Pago
- Banks and other processors
For each provider we check
- Availability by country
- Account type
- Currencies
- Recurring payments
- Refunds
- Marketplace payments
- Contractual limits
Illustrative view
- 01Your server calls the provider’s API
- 02The provider returns the payment ID
- 03The status is stored in the platform
- Payment data
- Requests with secret keys are sent only from the server.
- Used for
- Creating payments, refunds, reports
Switch integration methods to see the flow and where payment data travels.
Provider names are examples. They do not imply a partnership with or certification of ENOR.
Fiscal reporting and connections to tools such as devPOS are handled as a separate integration from payment processing.
DIGITAL WALLETS AND BALANCES
Clear balances. Every movement traceable.
We build interfaces and logic for digital wallets, user accounts and credit systems, depending on the product model and the providers involved.
- History of incoming and outgoing movements
- Available balance
- Reserved amounts
- Usage limits
- Refunds
- Notifications
- Reports
- Admin control with authorisations
Four values that are not the same
- 01Real moneyFunds held by an authorised institution.
- 02Electronic moneyWhere applicable, issued by a licensed issuer.
- 03Internal creditsValue usable only inside your platform.
- 04Loyalty pointsRewards under the programme’s rules.
Wallet · Demo userIllustrative view
Available
€120.00
Reserved
€0.00
Internal credits
€15.00
Loyalty points
340 points
Credits and points are not added to the money balance.
History
- Top-up · bank transferTRF-118+€120.00
Reserve an amount, then capture or release it: every change has its own history entry.
A balance in a database does not make a platform a financial institution. Holding funds depends on the model and the licensed partners.
NFC payments and similar features depend on devices, providers and the relevant programmes.
LEDGER OF FINANCIAL MOVEMENTS
A reliable foundation for every movement.
A balance is the result of movements, not a number edited by hand. A structured ledger shows where each amount came from, where it went and who approved it.
- Balanced entries for every movement
- Unique references
- Link to the source payment or document
- Draft status and final posting
- Corrections through offsetting entries
- Available balance kept apart from reserved amounts
- Amounts with suitable precision
- A defined currency for every amount
- Clear rounding rules
- History that ordinary users cannot change
JE-118 · Customer paymentIllustrative view
- Source:
- PAY-2042 · provider · evt_7781
- Status:
- Posted
| Account | Debit | Credit |
|---|---|---|
| Provider clearing account | 46.80 | |
| Fee expense | 1.20 | |
| Customer receipts | 48.00 | |
| Total Balanced | 48.00 | 48.00 |
Stored as an integer: 4800 (cents) · EUR
History
- Draft created by the webhook
- Amount and currency check
- Posted
Select a movement to see its source, entries, fees and history.
Monetary amounts are stored as integers in the smallest unit or as exact decimals, never as floating-point numbers.
A balance is never edited directly: every correction is recorded as a new movement linked to the original.
MULTI-CURRENCY AND RECONCILIATION
Every amount in its own currency. Every difference explainable.
We store the original amount and currency of every operation and convert only with a recorded rate and time.
- ALL, EUR, USD and other currencies as needed
- Original amount and currency
- Conversion rate and time
- Fees
- Net amount
- Reporting currency
- Exchange-rate differences
- Reconciliation by provider and period
Six states we keep separate
- 01Customer paymentWhat the customer paid.
- 02Balance at the providerFunds the provider holds for you.
- 03Payout to the bankWhat arrives in your account.
- 04FeesProvider costs for each operation.
- 05RefundsAmounts returned to customers.
- 06DisputesPayments contested by the customer.
Illustrative view
| ID | Original amount | Net | In ALL |
|---|---|---|---|
| PAY-2042 | 48.00 EUR | 46.80 EUR | 4,605 ALL |
| PAY-2043 | 35.00 USD | 33.95 USD | 3,059 ALL |
| PAY-2044 | 2,500 ALL | 2,450 ALL | 2,450 ALL |
Switch views to see transactions, payouts to the bank, differences and reports by currency.
Different currencies are never added up without a conversion explained by the relevant rate and time.
A successful payment does not mean it has reached the bank: payouts are tracked separately.
BANKING PLATFORMS AND PORTALS
Digital experiences on top of existing financial services.
We build the interfaces customers and staff use every day, connected to the institution’s core systems and authorised providers.
- Customer portals
- Mobile apps
- Account and transaction views
- Service requests
- Documents and notifications
- Approval workflows
- Integrations with core systems and authorised providers
Customer portalIllustrative view
Current account
AL·· ···· 4821
€3,240.15
ALL account
AL·· ···· 9033
86,400 ALL
Recent movements
- Card payment · Demo Shop−€48.00
- Incoming transfer+€500.00
Open Banking works through APIs and customer authorisations, depending on the market and the relevant partner. Access depends on the connected banks and providers.
ENOR builds the interfaces and integrations; the core banking system and the licences remain the institution’s.
LOAN MANAGEMENT
From application to repayment administration.
We digitise the journey of a loan, from the first documents to the last instalment, with decisions documented by authorised people.
- Application forms
- Document collection
- Completeness checks
- Verifications with external providers
- Review and approval workflows
- Contracts and documents
- Instalment plans
- Partial payments
- Outstanding balances
- Reminders and reports
Demo loan · L-5512Illustrative view
€6,000.00 · 12 instalments · illustrative terms
- Application
- Documents
- Completeness
- Verification
- Review
- Decision
- Contract
- Instalments
The decision was made by the authorised person
| Instalment | Due | Amount | Paid | Status |
|---|---|---|---|---|
| 1 | 05 Jan | 520.00 | 520.00 | Paid |
| 2 | 05 Feb | 520.00 | 520.00 | Paid |
| 3 | 05 Mar | 520.00 | 0.00 | Due |
| 4 | 05 Apr | 520.00 | 0.00 | Upcoming |
Outstanding balance€5,200.00
Record a partial payment for the third instalment and see the outstanding balance.
Calculations follow the product’s defined terms. Risk-scoring models and automated decisions need validation, controls and review appropriate to the context.
P2P lending is handled as a separate project, depending on the operating model and the relevant requirements.
INSURTECH
More connected processes for insurers and brokers.
We connect quotes, policies and claims in one flow, integrated with insurers’ systems.
- Quote requests
- Product comparison, where authorised sources exist
- Policy administration
- Renewals
- Documents
- Claims reporting
- Evidence upload
- Review and authorised decisions
- Notifications
- Integrations with insurers’ systems
Issuing policies and deciding on claims stays with the insurer or the authorised person, through the relevant integrations.
Policy P-7781 · Property insuranceIllustrative view
Renewal: 12 Nov
- 1ReportedClaim reported by the customer in the app
- 2Evidence uploaded
- 3Under review
- 4Authorised decision
- 5Payment
Step through a claim, from reporting to the authorised decision.
KYC, AML AND REGTECH
Integrated verification. Documented decisions.
We integrate specialised verification providers and build the process around them: cases, review and decision reasons.
Case KYC-204 · Demo business customerIllustrative view
Technical result
- DocumentReadable
- Selfie / livenessPassed
- Business registerMatches
Flag
Possible name match on a list
Needs review by a person
Decision
Awaiting review
Review the flag and make a decision with a reason.
- Identity verification with specialised providers
- Document checks
- Selfie / liveness checks, where offered
- Business and ownership verification
- Screening against lists through authorised sources
- Case management
- Manual review
- Decision reasons
- History and export
Three steps that are not confused
- 01Technical resultWhat the verification provider reported.
- 02FlagWhat needs a person to look at it.
- 03DecisionCustomer acceptance by the responsible person, with a reason.
A list match is not automatically a violation: it is reviewed and the decision is documented.
Integrating an API is not enough for AML compliance. Storage of documents and biometric data is designed according to need, risk and project requirements.
EMBEDDED FINANCE
Financial services inside your product.
We connect your platform with financial providers so users can complete actions inside one integrated experience.
Examples
- Payments inside the platform
- Subscriptions
- Marketplace payments
- Fund disbursement, where the provider supports it
- Financing through a partner
- Insurance offers from authorised providers
Who is responsible for what
Your platform
- Product and experience
- Relationship with users
- Commercial agreements
ENOR as developer
- Architecture and code
- Technical integrations
- Testing and maintenance
Financial provider
- The regulated service
- Licences and holding of funds
- Its own controls
The user
- Accurate data
- Consents and authorisations
- Use according to the terms
A technical integration does not replace licensing or commercial agreements with the financial provider.
AI AND FINANCIAL ANALYTICS
More useful data for your team.
We use AI for time-consuming work and leave decisions to people when the impact matters.
- Data extraction from documents
- Transaction classification
- Reconciliation suggestions
- Report summaries
- Anomaly detection for review
- Search across authorised documentation
- Assistants for administrative processes
- Operational forecasts, where the data supports them
How we make it reliable
- Data quality assessment
- Accuracy measurement
- Handling of false flags
- Human review for impactful decisions
- Access control over sources
- Performance and cost monitoring
Flags for reviewIllustrative view
AI flags; staff decide. No funds are moved automatically.
- PAY-2077Unusual amount for this customer€420.00For review
- Account U-3185 failed attempts within 10 min—For review
- PAY-2081Possible duplicate payment€64.50For review
Review the flags: mark one as normal or escalate it.
AI does not move funds or approve sensitive actions without defined authorisations and limits.
Flags help the team find cases to review; they do not forecast markets or replace controls.
INVESTMENTS AND DIGITAL ASSETS
Platforms for portfolios and digital assets.
When the product calls for it, we build dashboards and integrations for portfolios, with a clear source and time for every price.
- Portfolio dashboards
- Integrations with licensed market data
- Transaction history
- Position and valuation reporting
- Integrations with authorised providers
- Blockchain and smart contracts for justified cases
- Digital asset interfaces depending on the project model
Illustrative view
| Position | Quantity | Price | Price source |
|---|---|---|---|
| Asset A | 12 | €41.20 | Data provider · 10:30 |
| Asset B | 3 | €118.00 | Data provider · 10:30 |
- Unrealised valuation
- +€84.00
- Realised gain
- €0.00
A position’s valuation is not a realised gain. Custodial and non-custodial wallets have different requirements.
Exchange, custody and automated advice need dedicated analysis and are not standard features. Blockchain is not a prerequisite for security.
SECURITY
Security built into every layer.
Measures are set according to the project and its risk, from user identity to how data is stored and monitored.
- Access control and least privilege
- Multi-factor authentication
- Authorisation for every sensitive action
- Segregation of duties
- Two-person approval where required
- Encryption in transit and at rest
- Key and credential management
- Rate limiting and abuse protection
- Protected audit logs
- Monitoring
- Backups and restore tests
- Incident management
- Security testing according to the project scope
Card numbers, security codes, keys and identity documents are never written to logs.
For card payments we favour provider components and tokenisation, with a clearly defined scope of responsibility.
REGULATORY REQUIREMENTS
Development driven by the project’s and market’s requirements.
Requirements vary by service, the country where it is offered, the company’s role and the partners involved. During analysis we define the technical controls, integrations and documentation the project needs to support.
Providers’ certifications do not transfer automatically to your product or to ENOR. The applicability of each requirement is assessed for the specific project.
- PCI DSSIndustry standardSecurity standard for card data, for entities that store, process or transmit it.
- GDPREU regulationPersonal data protection, when the service involves users in the EU.
- PSD2EU directivePayment services, e.g. strong customer authentication and account access through authorised providers.
- KYC / AMLLegal obligationsCustomer due diligence and anti-money-laundering duties, for entities subject to them.
PERFORMANCE AND RELIABILITY
Ready for load, and for when a service fails.
Architecture is chosen for the real need. What matters is that the system knows what to do when a response is late or lost.
- Testing for the expected volume
- Queues for asynchronous processing
- Controlled retries
- Idempotency
- Concurrency management
- Limits and timeouts
- Monitoring of latency and errors
- Recovery and reconciliation
- A clear status when the result is not yet known
Request to the providerIllustrative view
- Request to the provider
- Timeout after 10 s
- Unknown status
- Check with the same key
- Confirmed: captured
While uncertain, the customer sees “Payment being verified”, not “Failed”.
Simulate a timeout and see how the unknown status is resolved.
A timeout does not mark a transaction as finally failed: the status is checked again with the provider.
Capacity and service levels are defined after measurement and by agreement.
WHITE-LABEL AND MULTI-TENANT
Your platform. Your identity. Separate control.
The same platform can serve several brands or organisations, with separate looks, configurations and data.
- Logo and colours
- Custom domain
- App with the brand’s identity
- Languages and currencies
- Business-specific configuration
- Roles for admins and partners
- Data isolation
- Reporting by organisation
Three different layers
- 01Visual customisationThe brand’s look: logo, colours, domain.
- 02Technical isolationData is separated on the server; a frontend filter is not enough.
- 03Financial separationFunds and licences belong to the relevant operator.
White-label does not transfer financial licences from one operator to another.
ABrand A
Balance
€120.00
Pay
Wallet
Illustrative view
Organisationtenant_a
Data is filtered on the server by organisation
Same code, separate configuration
Switch the brand: the look changes while the data stays separated by organisation.
SYSTEM MODERNISATION
Improve the platform without losing control of its history.
We modernise step by step and verify balances and transactions before and after every switchover.
- Audit of the existing system
- Identification of data sources
- Gradual integrations
- Trial migrations
- Balance and transaction checks
- Reconciliation before and after migration
- Pilot
- Rollback plan
- Documentation and training
Historical references are preserved and links between payments, documents and actions are not lost. Possible downtime is assessed before the switchover.
Trial migration reconciliationIllustrative view
- 01Audit
- 02Data sources
- 03Gradual integrations
- 04Trial migration
- 05Balance reconciliation
- 06Pilot
- 07Final switchover
| Data | Source | Migrated |
|---|---|---|
| Accounts | 8,214 | 8,214 |
| Transactions | 412,380 | 412,380 |
| Matching balances | 8,214 | 8,211 |
3 balances with a difference → reviewed before switchover
Rollback plan: ready
DEVELOPMENT PROCESS
From business modelto a tested platform.
Phases and timelines are set once we know the project scope, partners and integrations.
02
Scope and responsibilities
We define functions, partners, requirements and acceptance criteria.
03
Architecture and UX/UI
We design the technical structure, data model and user experience.
04
Development
We build in phases with regular demos.
05
Integration and testing
We verify the financial logic, permissions and communication with providers.
06
Pilot and launch
We go to production with a plan, controls and monitoring.
07
Maintenance
We handle updates, issues and extensions under the agreement.
What financial product are you building?
Talk to ENORGoing to production happens with a plan, controls and monitoring.
TEST SCENARIOS
We also test what happens after an error.
Tests check the financial outcome and permissions, not only how the interface looks.
- 01The user clicks “Pay” twice.Expected result: Only one payment is created thanks to the idempotency key.
- 02The webhook arrives several times.Expected result: The event is processed once; repeats are acknowledged with no effect.
- 03Events arrive out of order.Expected result: Status follows only allowed transitions and never moves backwards.
- 04The amount or currency doesn’t match.Expected result: The payment is not marked completed and a case is opened for review.
- 05The payment goes through but confirmation is late.Expected result: Status stays pending and is checked with the provider.
- 06A refund is partial.Expected result: Net amount and balances update correctly without closing the payment.
- 07Two requests try to use the same balance.Expected result: Only one succeeds; the other is refused without taking the balance below zero.
- 08The provider is temporarily unavailable.Expected result: Requests are queued or a clear status is shown, with no duplicates.
- 09A user tries to view another company’s transactions.Expected result: The server refuses the request and the attempt is logged.
- 10Migration must preserve balances and history.Expected result: Balances are reconciled with movements before and after the switchover.
WHY ENOR
A development partner for processes that demand precision.
- Business logic analysisWe understand the flows of funds before writing code.
- Documented integrationsEvery provider connection has defined rules, errors and reconciliation.
- Traceable actionsWho did what and when, for every important action.
- Clear interfacesFor customers, operations teams and administrators.
- Testing of critical casesDuplicate payments, late events and provider outages.
- Ongoing support and developmentUpdates and extensions under the agreement.
FAQ
Frequently asked questions.
Let’s turn your FinTech idea into a concrete plan.
Tell us what you want to build or improve. We define the functions, integrations and development phases.
What our clients say
5.0
AArben Hoxha, CEO
Sample Logistics Co.
“They translated complex technical concepts into clear decisions for our team.”