The purpose of this guide is to help you submit card payments to the Adyen Payment System using an API and the card alias as card number, and to receive the full card number in a request to a separate URL.
Due to strict industry regulations the API is only available to merchants who have full Payment Card Industry Data Security Standard (PCI DSS) compliance and fall into either the Level 1 or Level 2 categories.
Read more about PCI DSS on our blog.
In the following sections we will cover how you can submit payments to our platform using either Adyen's SOAP or JSON APIs, and how this request is forwarded to your server.
This functionality is not enabled by default, and requires additional configuration at Adyen. Contact the Support Team if you would like to have this functionality enabled for you.
This document is an addendum to the Adyen API Manual and will reference, without citation, concepts explained there.
Adyen has code samples in various programming languages available for your reference. These can be viewed on the Adyen github.
For the SOAP messaging protocol, all test payment requests must be posted to the following endpoint:
The data schema for corresponding SOAP objects is available at:
JSON and FORM
This is an overview of the test URL endpoints to communicate with our API using JSON or FORM (key-value parameters passed in an HTTP POST URL).
After you are ready to go live, you should switch to either generic or custom live endpoints. For more information, refer to Live endpoints.