Skip to Content

Connect Adyen and Kerridge

Connecting Adyen and Kerridge could allow a company to automate payment processing directly from its business management platform. This setup could support the transfer of transaction data between the two systems, helping to reduce manual entry, improve reconciliation accuracy, and enhance financial reporting by centralizing payment and sales information.

You can build this integration on the System2System platform. We design the connection between Adyen and Kerridge around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Adyen and Kerridge?

A company that operates both Adyen and Kerridge could benefit from connecting these systems to enable efficient data exchange. Without such a connection, staff may need to enter the same transaction or customer information separately into each system, which can lead to errors, wasted time, and inconsistencies. For example, payment data recorded in Adyen could become out of sync with sales or inventory records managed in Kerridge, resulting in discrepancies that make reconciliation difficult and may cause managers to make decisions based on outdated or incomplete data. If a connection were established, it could allow for the transfer of payment confirmations, transaction details, and customer identifiers from Adyen to Kerridge, as well as the movement of order or invoice data in the other direction. This could help ensure that financial records, stock levels, and customer accounts remain accurate and up to date across both platforms. The specific data that can be exchanged depends entirely on what each system makes available through its API and is determined on a case-by-case basis.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Adyen and Kerridge make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us