integrations.sh
← all integrations

adyen.com – PaymentService

OpenAPI apis-guru payment

A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.

To learn more about the API, visit .

Authentication

You need an to authenticate to the API.

If using an API key, add an X-API-Key header with the API key as the value, for example:

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

Alternatively, you can use the username and password to connect to the API using basic authentication, for example:

curl-U "ws@Company.YOUR_COMPANY_ACCOUNT":"YOUR_BASIC_AUTHENTICATION_PASSWORD" \-H "Content-Type: application/json" \...

Versioning

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

For example:

https://pal-test.adyen.com/pal/servlet/Payment/v25/authorise

Going live

To authenticate to the live endpoints, you need an from your live Customer Area.

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


https://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/Payment/v25/authorise

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

Homepage
https://api.apis.guru/v2/specs/adyen.com:PaymentService/25.json
Provider
adyen.com:PaymentService / PaymentService
OpenAPI version
3.1.0
Spec (JSON)
https://api.apis.guru/v2/specs/adyen.com/PaymentService/25/openapi.json
Spec (YAML)
https://api.apis.guru/v2/specs/adyen.com/PaymentService/25/openapi.yaml

Tools (9)

Extracted live via the executor SDK.

  • general.postAuthorise

    Creates a payment with a unique reference (pspReference) and attempts to obtain an authorisation hold. For cards, this amount can be captured or cancelled later. Non-card payment methods typically don't support this and will automatically capture as part of the authorisation.

    This endpoint is part of our . If using a , use the endpoint under Checkout API instead.

  • general.postAuthorise3d

    For an authenticated 3D Secure session, completes the payment authorisation. This endpoint must receive the md and paResponse parameters that you get from the card issuer after a shopper pays via 3D Secure.

    This endpoint is part of our . If using a , use the endpoint under Checkout API instead.

  • modifications.postCancel

    Cancels the authorisation hold on a payment, returning a unique reference for this request. You can cancel payments after authorisation only for payment methods that support distinct authorisations and captures.

    For more information, refer to .

    This endpoint is part of our . If using a , use the endpoint under Checkout API instead.

  • modifications.postCancelOrRefund

    Cancels a payment if it has not been captured yet, or refunds it if it has already been captured. This is useful when it is not certain if the payment has been captured or not (for example, when using auto-capture).

    Do not use this endpoint for payments that involve:

    • .
    • either at time of payment or capture for Adyen for Platforms.

    Instead, check if the payment has been captured and make a corresponding or call.

    For more information, refer to .

    This endpoint is part of our . If using a , use the endpoint under Checkout API instead.

  • modifications.postCapture

    Captures the authorisation hold on a payment, returning a unique reference for this request. Usually the full authorisation amount is captured, however it's also possible to capture a smaller amount, which results in cancelling the remaining authorisation balance.

    Payment methods that are captured automatically after authorisation don't need to be captured. However, submitting a capture request on these transactions will not result in double charges. If immediate or delayed auto-capture is enabled, calling the capture method is not neccessary.

    For more information refer to .

    This endpoint is part of our . If using a , use the endpoint on Checkout API instead.

  • modifications.postRefund

    Refunds a payment that has previously been captured, returning a unique reference for this request. Refunding can be done on the full captured amount or a partial amount. Multiple (partial) refunds will be accepted as long as their sum doesn't exceed the captured amount. Payments which have been authorised, but not captured, cannot be refunded, use the /cancel method instead.

    Some payment methods/gateways do not support partial/multiple refunds. A margin above the captured limit can be configured to cover shipping/handling costs.

    For more information, refer to .

    This endpoint is part of our . If using a , use the endpoint under Checkout API instead.

  • modifications.postVoidPendingRefund

    This endpoint allows you to cancel an unreferenced refund request before it has been completed.

    In your call, you can refer to the original refund request either by using the tenderReference, or the pspReference. We recommend implementing based on the tenderReference, as this is generated for both offline and online transactions.

    For more information, refer to .

  • openapi.previewSpec

    Preview an OpenAPI document before adding it as a source

  • openapi.addSource

    Add an OpenAPI source and register its operations as tools