Skip to content
XSIS
Talk to an engineer

We build. We connect. We run.

XSIS designs and builds software, AI and data platforms, and connects your ERP to banks, POS and third parties, with in-house and outsourced teams that stay to run what they build.

An engineer works on network cabling in blue light
The ERP at the centre, every connection monitoredBanks, stores, payment networks and third parties connect to the ERP through one integration layer. Anything that fails lands in a queue with an alert, never in silence.ERPERPSAP S/4HANA, OracleNetSuite, Dynamics365, Odoo, SageXSISIntegration layerAPIs, queues,mapping andvalidationBankBanksPayments, statusreports, statementsPOSPOS and storesSales, returns, stockand pricesGatewayPayment gatewayand acquirerCard authorisation andsettlementThird partyThird partiesCRM, logistics, tax,KYC and identityServiceMonitoring andexception queueRetries, alerts andreconciliation breaksPeopleYour operationsteam1REST/JSON · ODataIDoc2ISO 20022 pain.001SFTP H2H3camt.053MT9404REST/JSON5REST/JSON6ISO 85837SFTP8REST · SOAP · webhook910

The ERP at the centre, every connection monitored

Banks, stores, payment networks and third parties connect to the ERP through one integration layer. Anything that fails lands in a queue with an alert, never in silence.

  • Primary flow
  • Asynchronous
  • Exception path

The flow, step by step

  1. From ERP to Integration layer: Orders, invoices and payment runs, over REST/JSON · OData · IDoc (primary flow).
  2. From Integration layer to Banks: Payment files, over ISO 20022 pain.001 · SFTP H2H (primary flow).
  3. From Banks to Integration layer: Statements, over camt.053 · MT940 (asynchronous).
  4. From POS and stores to Integration layer: Sales and returns, through an event queue, over REST/JSON (asynchronous).
  5. From Integration layer to POS and stores: Prices and stock, over REST/JSON (primary flow).
  6. From POS and stores to Payment gateway and acquirer: Card authorisation, over ISO 8583 (primary flow).
  7. From Payment gateway and acquirer to Integration layer: Settlement files, over SFTP (asynchronous).
  8. From Integration layer to Third parties: Customers, shipments and tax documents, over REST · SOAP · webhook (primary flow).
  9. From Integration layer to Monitoring and exception queue: Failed messages, to a dead-letter queue (exception path).
  10. From Monitoring and exception queue to Your operations team: Alerts and breaks to resolve (exception path).
A card is used at a payment terminal

Lead industry

Fintech is where we go deepest

Banking, payments, lending, wealth, insurance and digital wallets run on systems that must be right every time. We build those systems and the connections between them, with the regulation in mind from the first design.

Fintech and financial services
  1. Banking

    Digital banking channels, core banking extensions and bank connectivity for corporate clients.

  2. Payments

    Gateway and acquirer integrations, payment orchestration, settlement and reconciliation.

  3. Lending

    Origination, decisioning and servicing platforms, with explainable credit models.

  4. Digital wallets

    Wallet apps, tokenised cards, onboarding with KYC checks and transaction monitoring.

A digital financial product, end to endA banking or wallet app talks to one API layer. Behind it sit identity checks, card processing and the core ledger. Transactions are screened as they happen, and anything suspicious is held for a person to review.PeopleCustomerServiceBanking or walletappWeb and mobileXSISAPI layerAuthentication, limitsand audit logThird partyKYC and AMLproviderOnboarding andscreeningGatewayCard processorIssuing andauthorisationBankCore banking orledgerAccounts, balancesand postingsServiceFraud andtransactionmonitoringRules and modelsPeopleCompliance andoperations teamReviews holds andreferrals12REST/JSON · OAuth 2.03REST/JSONwebhook4REST/JSON · ISO 200225REST/JSON6ISO 8583789

A digital financial product, end to end

A banking or wallet app talks to one API layer. Behind it sit identity checks, card processing and the core ledger. Transactions are screened as they happen, and anything suspicious is held for a person to review.

  • Primary flow
  • Asynchronous
  • Exception path

The flow, step by step

  1. From Customer to Banking or wallet app: Signs up, pays and transfers (primary flow).
  2. From Banking or wallet app to API layer: Requests, over REST/JSON · OAuth 2.0 (primary flow).
  3. From API layer to KYC and AML provider: Identity and screening checks, over REST/JSON · webhook (primary flow).
  4. From API layer to Core banking or ledger: Postings and balances, over REST/JSON · ISO 20022 (primary flow).
  5. From API layer to Card processor: Card issuing and controls, over REST/JSON (primary flow).
  6. From Card processor to Core banking or ledger: Card transactions, over ISO 8583 (asynchronous).
  7. From API layer to Fraud and transaction monitoring: Transactions to screen, as an event stream (asynchronous).
  8. From Fraud and transaction monitoring to Compliance and operations team: Held for review (exception path).
  9. From KYC and AML provider to Compliance and operations team: Failed or unclear checks referred (exception path).

What you can check on this site

services, each with deliverables, process and answers
22
integration blueprints with the failure path drawn in
5
technologies, products and standards we work with
141
answered questions, by topic
237

Questions clients ask first

Who is XSIS?

XSIS is KONG GROUP’s technology company. We design, build, integrate and run software for enterprises: AI and data, custom software, web and mobile, cloud, and the integrations that connect ERP systems to banks, POS and third parties. Fintech is our lead industry. We deliver through our own in-house engineers and vetted outsourced teams, under one set of standards.

Link to this question
What does “in-house and outsourced teams” mean?

XSIS employs its own engineers, who lead projects, set the technical direction and are accountable for quality. Where a project needs more capacity or a specialist skill, we add engineers from vetted outsourcing partners. They work to the same standards, contracts and security rules, and you always know who is on your team and who employs them.

Link to this question
How do you estimate cost?

We estimate from the scope, not from a rate card. After a first conversation we break the work into parts, size each one and write down the assumptions behind the estimate. The main drivers are the number of systems and integrations, the state of your data, security and regulatory requirements, the testing needed and the seniority of the team. You receive a written estimate with options, so you can choose what to do first. You see the price and the timeline before we start.

Link to this question
Who owns the code and the work you produce?

Intellectual property in the work we build for you is yours from the first commit — no assignment step at the end. That covers the custom code, documentation and other deliverables made for you. Anything we bring that existed before, such as internal tools or libraries, stays ours, and you receive a licence to use it in your systems. Open-source components keep their own licences, and we list them for you.

Link to this question
How do you protect our systems, code and data?

Access is granted per person, limited to what each role needs, and removed when that person leaves the project. We work in your repositories and environments if you prefer, use multi-factor authentication, and keep secrets in a vault, never in code. Code is reviewed before it is merged, dependencies are scanned, and production data is not copied into test environments without masking. We agree these controls with your security team at the start.

Link to this question
How soon can work start?

It depends on the team you need and on what has to be in place first: the contract, access to your systems, security reviews and, for integrations, your partners’ test environments. We tell you what we need from you and when, and confirm a start date in the proposal. Discovery work can often begin while access is being arranged.

Link to this question
All questions

Tell us what you need to build or connect

Describe the system, the integration or the team you need. We come back with questions and options.