README

Introduction

Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).

This API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit online payments documentation.

Authentication

Each request to Checkout API must be signed with an API key. For this, get your API key from your Customer Area, and set this key to the X-API-Key header value, for example:

curl
-H "Content-Type: application/json" \
-H "X-API-Key: YOUR_API_KEY" \
...

Versioning

Checkout API supports versioning using a version suffix in the endpoint URL. This suffix has the following format: "vXX", where XX is the version number.

For example:

https://checkout-test.adyen.com/v71/payments

Server-side API libraries

We provide open-source server-side API libraries in several languages:

• PHP
• Java
• Node.js
• .NET
• Go
• Python
• Ruby
• Apex (beta)

See our integration examples for example uses of the libraries.

Developer resources

Checkout API is available through a Postman collection. Click the button below to create a fork, then set the environment variables at Environments > Adyen APIs.

Going live

To access the live endpoints, you need an API key from your live Customer Area.

The live endpoint URLs contain a prefix which is unique to your company account, for example:

https://{PREFIX}-checkout-live.adyenpayments.com/checkout/v71/payments

Get your {PREFIX} from your live Customer Area under Developers > API URLs > Prefix.

When preparing to do live transactions with Checkout API, follow the go-live checklist to make sure you've got all the required configuration in place.

Release notes

Have a look at the release notes to find out what changed in this version!, Configure and manage your Adyen company and merchant accounts, stores, and payment terminals.

Authentication

Each request to the Management API must be signed with an API key. Generate your API key in the Customer Area and then set this key to the X-API-Key header value.

To access the live endpoints, you need to generate a new API key in your live Customer Area.

Versioning

Management API handles versioning as part of the endpoint URL. For example, to send a request to this version of the /companies/{companyId}/webhooks endpoint, use:

https://management-test.adyen.com/v3/companies/{companyId}/webhooks

Going live

To access the live endpoints, you need an API key from your live Customer Area. Use this API key to make requests to:

https://management-live.adyen.com/v3

Release notes

Have a look at the release notes to find out what changed in this version!

Install the Package

Run the following command to install the package and automatically add the dependency to your composer.json file:

composer require "apimatic-adyen/adyen-apimatic-sdk:1.0.1"

Or add it to the composer.json file manually as given below:

"require": {
    "apimatic-adyen/adyen-apimatic-sdk": "1.0.1"
}

You can also view the package at: https://packagist.org/packages/apimatic-adyen/adyen-apimatic-sdk#1.0.1

Initialize the API Client

Note: Documentation for the client can be found here.

The following parameters are configurable for the API Client:

The API client can be initialized as follows:

use AdyenApIsLib\Logging\LoggingConfigurationBuilder;
use AdyenApIsLib\Logging\RequestLoggingConfigurationBuilder;
use AdyenApIsLib\Logging\ResponseLoggingConfigurationBuilder;
use Psr\Log\LogLevel;
use AdyenApIsLib\Environment;
use AdyenApIsLib\Authentication\ApiKeyAuthCredentialsBuilder;
use AdyenApIsLib\Authentication\BasicAuthCredentialsBuilder;
use AdyenApIsLib\AdyenApIsClientBuilder;

$client = AdyenApIsClientBuilder::init()
    ->apiKeyAuthCredentials(
        ApiKeyAuthCredentialsBuilder::init(
            'X-API-Key'
        )
    )
    ->basicAuthCredentials(
        BasicAuthCredentialsBuilder::init(
            'Username',
            'Password'
        )
    )
    ->environment(Environment::PRODUCTION)
    ->loggingConfiguration(
        LoggingConfigurationBuilder::init()
            ->level(LogLevel::INFO)
            ->requestConfiguration(RequestLoggingConfigurationBuilder::init()->body(true))
            ->responseConfiguration(ResponseLoggingConfigurationBuilder::init()->headers(true))
    )
    ->build();

Environments

The SDK can be configured to use a different environment for making API calls. Available environments are:

Fields

Authorization

This API uses the following authentication schemes.

• ApiKeyAuth (Custom Header Signature)
• BasicAuth (Basic Authentication)

List of APIs

• Paymentlinks
• Account-Companylevel
• Account-Merchantlevel
• Account-Storelevel
• Payoutsettings-Merchantlevel
• Users-Companylevel
• Users-Merchantlevel
• My AP Icredential
• AP Icredentials-Companylevel
• AP Icredentials-Merchantlevel
• AP Ikey-Companylevel
• AP Ikey-Merchantlevel
• Clientkey-Companylevel
• Clientkey-Merchantlevel
• Allowedorigins-Companylevel
• Allowedorigins-Merchantlevel
• Webhooks-Companylevel
• Webhooks-Merchantlevel
• Paymentmethods-Merchantlevel
• Terminals-Terminallevel
• Terminalactions-Companylevel
• Terminalactions-Terminallevel
• Terminalorders-Companylevel
• Terminalorders-Merchantlevel
• Terminalsettings-Companylevel
• Terminalsettings-Merchantlevel
• Terminalsettings-Storelevel
• Terminalsettings-Terminallevel
• Androidfiles-Companylevel
• Splitconfiguration-Merchantlevel
• Payments
• Donations
• Modifications
• Recurring
• Orders
• Utility

SDK Infrastructure

Configuration

• ProxyConfigurationBuilder
• LoggingConfigurationBuilder
• RequestLoggingConfigurationBuilder
• ResponseLoggingConfigurationBuilder

HTTP

• HttpRequest

Utilities

• ApiResponse