Integrations
We connect ERP systems to banks, card networks, POS and third-party services. Each connection uses the standard its partner expects, is tested with that partner, and has a path for every failure.
Scroll sideways to see the whole drawing.
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
- From ERP to Integration layer: Orders, invoices and payment runs, over REST/JSON · OData · IDoc (primary flow).
- From Integration layer to Banks: Payment files, over ISO 20022 pain.001 · SFTP H2H (primary flow).
- From Banks to Integration layer: Statements, over camt.053 · MT940 (asynchronous).
- From POS and stores to Integration layer: Sales and returns, through an event queue, over REST/JSON (asynchronous).
- From Integration layer to POS and stores: Prices and stock, over REST/JSON (primary flow).
- From POS and stores to Payment gateway and acquirer: Card authorisation, over ISO 8583 (primary flow).
- From Payment gateway and acquirer to Integration layer: Settlement files, over SFTP (asynchronous).
- From Integration layer to Third parties: Customers, shipments and tax documents, over REST · SOAP · webhook (primary flow).
- From Integration layer to Monitoring and exception queue: Failed messages, to a dead-letter queue (exception path).
- From Monitoring and exception queue to Your operations team: Alerts and breaks to resolve (exception path).
How we build every connection
Specify before building
Every interface starts as a written specification: fields, formats, timing, volumes and error codes, agreed with you and your partner.
Test with the real counterpart
We test against each bank’s, acquirer’s or provider’s test environment, and keep the evidence for your auditors.
No silent failures
A message that fails is retried, queued or handed to a person, with an alert. Nothing disappears.
Reconcile what moved
What left one system is matched with what arrived in the other, and every difference is shown to someone who can act on it.
Observable in production
Dashboards and alerts show volumes, delays and errors for each connection, so problems are found before your partners call.
Documented and handed over
Mappings, runbooks and test evidence come with every connection, so your own team can run it.
Connections
Reference blueprints for the flows we build most: each shows the systems, the protocol on every line and what happens when something fails.
- ERP and banksPayments sent as ISO 20022 pain.001 over host-to-host SFTP or bank APIs, with camt.053 and MT940 statements matched back to the ledger.
- POS and ERPSales and returns posted from every store, stock and price changes sent back, and end-of-day totals reconciled.
- Card paymentsEMV terminals and payment gateways connected to acquirers over ISO 8583 or APIs, with settlement files reconciled in the ERP.
- Open banking APIsAccount information and payment initiation through regulated bank APIs and aggregators, with consent and token handling.
- ERP and third partiesREST, SOAP, webhook and iPaaS connections between your ERP and the services around it, with retries and alerts.
Integration services
The services that design, build, test and run these connections.
- ERP integrationIntegrations for SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365, Odoo, Sage and others, monitored and reconciled.
- Bank integrationHost-to-host and API connections to banks: ISO 20022 payment files, MT940 and camt statements, and automatic reconciliation.
- Payments and POS integrationISO 8583 and gateway integrations, EMV terminals, acquirer settlement files, and POS to ERP sales and stock sync.
- Third-party and API integrationREST, SOAP, webhooks and iPaaS integrations with CRM, logistics, tax, KYC and identity providers.
Systems and standards we work with
Naming a product here does not mean a partnership with, or an endorsement by, its vendor.
- ERP systems
- SAP S/4HANA
- SAP Business One
- Oracle NetSuite
- Oracle Fusion Cloud ERP
- Microsoft Dynamics 365 Finance and Supply Chain Management
- Microsoft Dynamics 365 Business Central
- Odoo
- Sage Intacct
- Sage X3
- Banking standards and channels
- ISO 20022
- pain.001
- pain.002
- camt.052
- camt.053
- camt.054
- MT940
- MT942
- SWIFT
- EBICS
- SFTP (H2H)
- OpenPGP
- PSD2
- Berlin Group NextGenPSD2
- UK Open Banking Standard
- FAPI
- Payments
- ISO 8583
- EMV
- EMV 3-D Secure
- PCI DSS
- Integration
- REST
- SOAP
- GraphQL
- Webhooks
- OpenAPI
- EDI (EDIFACT, ANSI X12)
- AS2
- MuleSoft
- Boomi
- Azure Logic Apps
- Apache Camel
- RabbitMQ
- Identity and access
- OAuth 2.0
- OpenID Connect
- SAML 2.0
- SCIM
- Keycloak
- Microsoft Entra ID
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