Softomate's discovery phase produced a complete data-flow diagram across all seven systems, identifying every point where a customer identifier crossed a system boundary, every webhook in current use, and every batch sync running on a schedule. The diagram revealed 23 distinct integration points across the stack, of which 11 were stable and 12 had known failure modes that the operations team had documented manually over the previous year.
The solution was a custom integration middleware (built in Python with FastAPI and deployed on the company's existing AWS UK region) that sat between the seven systems as a unified API and data layer. The middleware held the authoritative mapping between identifiers across all systems, intercepted every webhook event, applied retry logic with exponential back-off where appropriate, and wrote structured event logs that were queryable for both engineering debugging and compliance audit purposes.
The KYC provider integration was redesigned first because it was the most failure-prone in the existing setup. The previous flow had the KYC webhook posting directly to the risk engine, with a 14% silent failure rate. The new flow had the webhook posting to the middleware, which validated the payload, enriched it with the relevant HubSpot record, wrote it to the risk engine, and confirmed acknowledgement back from each downstream system before marking the event complete. Failed events were retried up to three times with increasing back-off, and final failures were posted to a Slack channel monitored by the operations team for manual resolution.
The banking-as-a-service integration was rebuilt to use the partner's webhook API rather than the previous polling approach. The middleware subscribed to every relevant event type (account creation, deposit confirmation, transaction posted, KYC status change) and translated them into the internal data model. The integration also included a daily reconciliation job that compared the middleware's view of the customer base against the BaaS partner's authoritative ledger, flagging any drift for engineering review.
The customer identifier consolidation was the most operationally important piece. The middleware introduced an internal customer ID that was generated at signup and mapped to the customer's record ID in each downstream system. All inter-system events used the internal ID as the canonical identifier, and the middleware handled translation to the system-specific ID at the point of API call. This eliminated the entire class of identifier-mismatch bugs that had been the source of much of the reconciliation work.
The compliance audit layer wrote every cross-system event into an immutable log stored in a write-once S3 bucket with retention configured to meet the FCA's record-keeping requirements. The compliance team gained, for the first time, the ability to produce a complete data-flow audit for any individual customer or any time window, which had previously required multi-system manual gathering. The audit layer also included structured tags for personal-data flows to support GDPR data subject access request handling.
The build was delivered in 9 weeks from kickoff. The first three weeks were discovery, design, and middleware foundation. Weeks four through seven were the seven integrations themselves, built in priority order: KYC, banking-as-a-service, risk engine, HubSpot, Intercom, Xero, Mixpanel. Weeks eight and nine were parallel-running with the legacy webhook setup, comparison testing, and the cutover itself.