Skip to content
XSIS
Talk to an engineer

Industries

The industries we build for, and the systems and integrations each depends on. Fintech comes first: it is where we go deepest.

Fintech and financial services

Banking, payments, lending, wealth, insurance and digital wallets: the platforms they run on, the rules they work under and the connections between them.

See the industry
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/JSONOAuth 2.03REST/JSONwebhook4REST/JSONISO 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).

Tell us what you need to build or connect.

Describe the systems, the timeline and the constraints. The right engineers take it from there.

  • Our team will call you within 24 hours during your preferred time slot
  • Our team is available 24/7