Within Valpay, Adyen is used as the underlying payment service provider responsible for processing transactions across online and in-person channels. Valpay does not abstract or replace Adyen, instead, it integrates with it directly, meaning you will work with Adyen’s APIs, flows, and concepts as part of your implementation.
Integration Model
In a Valpay-based system, your application communicates with Adyen to:
Create and manage payments
Handle customer interactions (e.g., redirects, authentication)
Receive payment status updates via webhooks
Valpay provides the environment, configuration, and merchant context in which these integrations operate, but the payment logic itself follows Adyen’s standard patterns.
What This Means for Developers
As a developer, you should think of your integration as:
Your application ↔ Adyen APIs (within a Valpay context)
You are responsible for:
Making API calls to Adyen (e.g.,
/payments,/sessions)Integrating frontend components (Drop-in, Components, etc.)
Handling redirects and additional actions (e.g., 3D Secure)
Processing webhook notifications
Credentials and Configuration
All communication with Adyen requires credentials that are provisioned for your Valpay environment, including:
API Key → used for authenticating server-side requests
Client Key → used for frontend integrations
Merchant Account → identifies your account within Adyen
These credentials are environment-specific (test vs live) and must be configured correctly in your application.
Payment Lifecycle Ownership
Adyen is the system of record for payment state.
This means:
Initial responses from API calls may not represent the final outcome
Webhooks must be used to confirm payment status
Your system should update internal state based on Adyen events
Example Interaction
A typical flow in a Valpay integration:
Your backend creates a payment or session using Adyen APIs
Your frontend handles user interaction (card entry, wallet, etc.)
Adyen processes the payment and returns an initial result
Adyen sends webhook events with the final status
Your system updates order/payment state accordingly
No Abstraction Layer
Unlike some platforms, Valpay does not introduce a custom payment abstraction layer on top of Adyen. This means:
You have full access to Adyen features
You follow Adyen’s official integration patterns
Adyen documentation remains directly relevant
Where necessary, this documentation will reference Adyen’s official guides, while providing additional context specific to using it within Valpay.
Additional Valpay APIs
In addition to payment processing through Adyen, Valpay provides its own set of APIs that offer additional services and capabilities outside of the core payment flow.
These APIs can be used for extended functionality such as platform-specific features, configuration, and other operational capabilities that complement your payment integration.
You can learn more in the Valpay API Developer Guide:
https://intercom.help/valpay-partner/en/collections/18909884-valpay-api-developer-guide
Key Takeaway
When building payments in Valpay, you are effectively building a direct Adyen integration, operating within a configured environment. Understanding Adyen’s APIs, flows, and event model is essential for a successful implementation.