---
title: "Integration checklist"
description: "Learn about the steps required to build a partner integration with Adyen."
url: "https://docs.adyen.com/partners/integration-checklist"
source_url: "https://docs.adyen.com/partners/integration-checklist.md"
canonical: "https://docs.adyen.com/partners/integration-checklist"
last_modified: "2026-06-01T15:33:16+02:00"
language: "en"
---

# Integration checklist

Learn about the steps required to build a partner integration with Adyen.

[View source](/partners/integration-checklist.md)

Follow the scoping checklist below to decide on the functionalities and features you will offer to your customers. After you have scoped your integration, start building an ecommerce, or point-of-sale integration with Adyen.

When building a partner integration, consider the ease of integration and implement all the features we offer that can be useful for your customers to offer the best integration and shopping experiences to their shoppers.

Building a partner integration with Adyen consists of the following steps:

1. [Scope the configuration and maintenance flows for your integration](#scope-the-configuration-and-maintenance-flows-for-your-integration).
2. [Explore the payment methods](#explore-payment-methods) that you can offer to your customers.
3. [Determine the account structure](#determine-adyen-account-structures) you need to meet your use case. For example, an in-person payments integration with multiple physical stores require a different account setup than an online payments integration for an ecommerce store.
4. [Review the integration requirements](#review-the-integration-requirements) to learn about the payment flows and features that are required to build a minimum viable partner integration with Adyen.
5. [Explore the features we offer](#explore-additional-features) to customize your integration according to your needs, and enable unique experiences for your shoppers.
6. [Choose the integration architecture](#choose-your-integration-architecture) that you will use to build your integration.
7. After you have scoped all the features and payment methods you will enable for your customers, and decided on an integration architecture, [build your integration](#build-your-integration).
8. [Document your integration](#document-your-integration) to make your integration accessible and easy to integrate with for your customers.
9. [Prepare to go live](#prepare-for-go-live) with your integration.

## Scope the configuration and maintenance flows for your integration

To onboard customers to your integration scalably and offer a seamless configuration experience, you can integrate with the Management API and OAuth. These additions let your customers integrate faster and more easily with your integration by automating configuration flows.

* **Management API**: reduce manual configuration work for your customers by integrating with our [Management API](https://docs.adyen.com/api-explorer/Management/latest/overview) to configure and manage account settings available in the Adyen Customer Area using HTTP calls.

  There are additional [API credential roles](/development-resources/api-credentials/roles/#management-api) you need to use the Management API.

* **OAuth**: integrate with [OAuth](/partners/oauth) to let your customers delegate API access to you, so you can authorize API requests on behalf of your customers.

## Explore payment methods

Adyen supports global and local payment methods. Use our payment methods documentation for [online payments](/payment-methods), and [in-person payments](/point-of-sale/what-we-support/payment-methods/) to find the payment methods that you need depending on the channels and locations you want to support. Take a look at our [payment method guides per region](https://www.adyen.com/payment-methods-guides) to understand global payment patterns.

## Determine Adyen account structures

You can have different account structures with Adyen. We require partner integrations to be able to support multi-store setups, meaning that the integration you build must be able to handle multiple merchant accounts under one company account.

Learn more about account structures for [online payments](/account/account-structure/) and [in-person payments](/point-of-sale/design-your-integration/determine-account-structure/).

## Review the integration requirements

As a partner, you are required to integrate with some features that Adyen offers to ensure that your integration can handle most common payment flows and handle happy and unhappy flows. There are different requirements for [online payments](/online-payments) and [in-person payments](/point-of-sale) integrations.

### Online payments

* Payment modifications: allow your customers to modify a payment's status and support shoppers in different payment scenarios. Modifications include [refunds](/online-payments/refund/), [cancellations](/online-payments/cancel/), [authorization adjustments](/online-payments/adjust-authorisation/), and delayed and separate [captures](/online-payments/capture/). Modifications also allow you to build additional logic, such as enabling a flow where a payment is only captured upon shipment.

* [3D Secure 2 Authentication](/online-payments/3d-secure/): allow customers to authenticate shoppers, where required.

* [Add application information in your requests](/partners/application-information): let Adyen identify the payments that are processed through your integration.

* [Webhooks](/development-resources/webhooks): inform customers of payment status changes, build logic to update other systems that are integrated with the payments flow.

* Response and error handling: when a customer makes a payment request to Adyen, they receive a response from Adyen. Your integration must be able to handle different responses.

  * Learn about the [HTTP status codes](/development-resources/response-handling/), and build logic to display them to shoppers.
  * Learn about [error codes and messages](/development-resources/error-codes/).

* [Result code mapping](/online-payments/build-your-integration/payment-result-codes): learn about the result codes that are returned in Adyen API responses and make sure your integration can handle all results.

Depending on the regions where your customers accept payments, there may be additional payment flows and features that are required to include in your integration, for example to comply with local regulations.

### In-person payments

* [Add application information in your requests](/partners/application-information): let Adyen identify the payments that are processed through your integration.
* [E2EE and P2PE PCI security](/development-resources/e2ee-p2pe-comparison/): the payment terminals provided by Adyen use the Adyen End-to-End Encryption (E2EE) solution to protect the whole payments value chain. If desired, you can opt-in to use our Point-to-Point Encryption (P2PE) solution. This is equally secure as E2EE and has the benefit of being PCI-certified. However, P2PE is only available for a limited set of terminal models.
* [Refunds](/point-of-sale/basic-tapi-integration/refund-payment/): issue refunds for point-of-sale transactions. We offer two types of refunds, [referenced](https://docs.adyen.com/point-of-sale/basic-tapi-integration/refund-payment/referenced/), and [unreferenced](/point-of-sale/basic-tapi-integration/refund-payment/unreferenced/).
* [Receipts](/point-of-sale/basic-tapi-integration/generate-receipts/): use the data you get in the API response from Adyen to generate receipts for your shoppers.
* [In-progress transaction cancellations](/point-of-sale/basic-tapi-integration/cancel-a-transaction/): support cancelling a transaction while in progress to support situations where a shopper changes their mind, or when your store staff needs to abort the transaction.
* [Transaction status verification](/point-of-sale/basic-tapi-integration/verify-transaction-status/): let your store staff verify the status of a transaction in cases of a communication or technical issue.
* Logging: Implement logging for your terminals to help troubleshooting.

## Explore additional features

Adyen supports a wide range of features that allows your customers to enable unique shopper experiences.

To find out about all the features that are relevant for the industry and markets you operate in, see [Industries and markets](/industries). You can use our [industry and sales channel selector](/industries/feature-packs) to get an overview of all features we recommend for you.

After you have decided on the features that you will integrate with, find out how to integrate with them in our documentation:

* [Online payments](/online-payments)
* [In-person payments](/point-of-sale)
* [Omnichannel](/unified-commerce)

## Choose your integration architecture

Adyen offers different implementation options to build [online payments](/online-payments) and [in-person payments](/point-of-sale) integrations.

### Online payments

Choose one of our [server-side flows](/online-payments/build-your-integration/#choose-your-server-side-implementation) depending on the [use cases that you want to support](/online-payments/build-your-integration/#supported-use-cases).\
You can connect your server-side implementation to our different client-side solutions:

* **Drop-in**: Render a list of available payment methods anywhere on your website, with the option to customize the styling of the payment methods list.
* **Components**: Render individual payment methods anywhere on your website, with the option to customize the styling of each payment method.
* **Custom UI**: Create your own UI and build an [API-only](/online-payments/build-your-integration/advanced-flow/?platform=Web\&integration=API%20only\&version=71) integration.

See [the Adyen demo store](https://www.mystoredemo.io/#/) to experience the checkout with our prebuilt UI. Using our Drop-in or Components decreases the integration effort required and ensures that you comply with [PCI DSS](/development-resources/pci-dss-compliance-guide/).

If you want to offer your customers the option to build headless integrations, where they use your integration to process payments in the back end and allow them to use their own UI, you must follow the API-only implementation.

### In-person payments

Learn about the integration choices available for in-person payments integrations in our [documentation](/point-of-sale/design-your-integration/). We offer:

* Payment terminals and mobile solutions:

  * Various [terminals](/point-of-sale/what-we-support/select-your-terminals/) to choose from depending on your needs. The terminals available to you depend on your selected [security solution](#in-person-payments).
  * [Mobile solutions](/point-of-sale/ipp-mobile/) to accept Tap to Pay or card reader payments using a mobile device like a smartphone, instead of a payment terminal.

* [Local or cloud communications](/point-of-sale/design-your-integration/choose-your-architecture/) to connect payment terminals to the Adyen payments platform. Use our [questionnaire](/point-of-sale/design-your-integration/choose-your-architecture/#choosing-between-cloud-and-local) to figure out which option suits your needs.

## Review security and compliance requirements

* See our [Integration Security Guide](/development-resources/integration-security-guide) to learn about the security measures that you have to implement.
* See our [PCI DSS compliance guide](/development-resources/pci-dss-compliance-guide) to learn about your responsibilities to comply with PCI DSS.
* To process payments in Europe, you need to comply with [PSD2 SCA](/online-payments/psd2-sca-compliance-and-implementation-guide/) regulations.

## Build your integration

After you have scoped your integration and decided on the features and payment methods you will enable for your customers, start building your integration.

Use our resources that outline the steps required to build an integration with Adyen:

* [Online payments integration checklist](/online-payments/integration-checklist/)
* [In-person payments integration checklist](/point-of-sale/get-started/tapi-checklist/)

While you are building your integration, we strongly recommend to document the integration journey that you can provide to your customers later. As an Adyen partner, it is your responsibility to provide the documentation for your integration.

## Document your integration

While you are building your integration, we recommend to document the integration so that you offer your customers complete and detailed documentation on how to integrate. We recommend to break down the documentation in two parts, to make a clear distinction between the steps your customers have to follow in your ecosystem, and in Adyen's Customer Area.

In your documentation, include:

* The features that you support.
* The regions that your integration is available in.
* Integration guides to configure and enable Adyen features.
* Testing documentation to let customers make end-to-end tests before going live with your integration.

## Prepare for go-live

### Test your integration

Follow our [testing guide for online payments](/development-resources/testing), and [in-person payments](/point-of-sale/testing-pos-payments) to make sure that your integration can handle different payment scenarios. After you have tested your integration, [take your integration live](/get-started-with-adyen/#apply-for-your-live-account) to start onboarding customers to your integration.

After you have tested your integration, you can start onboarding customers to your integration.

### Run a pilot

We strongly recommend to run a pilot with at least one customer, before you start onboarding more customers to your integration.

### Onboard customers

You are responsible to provide your customers with documentation and other relevant information to integrate with your integration. Before going live, make sure that they test the integration and have completed all the required integration steps.

Your customers must apply for a [live account](/get-started-with-adyen/#apply-for-your-live-account), and submit [the Attestation of Compliance (AOC), or the Self-Assessment Questionnaire (SAQ)](/development-resources/pci-dss-compliance-guide/#glossary). A contract must be signed between your customers and Adyen before you can process payments with your integration on behalf of them.
