You can integrate Adyen's client-side libraries with different server-side flows. Sessions flow is the default integration that we recommend and that meets the requirements for most online payments integrations.
Choose how you integrate depending on the use cases that you want to support.
API-only integrations must use Advanced flow. Sessions flow only works with our client-side libraries.
The following diagrams show the differences between Sessions flow, Advanced flow, and Sessions flow with additional methods:
Sessions flow: a single API request
Your server makes a single Checkout API request to the /sessions endpoint. Adyen sends payment data from our server to your client-side application. You can optionally implement additional client-side methods to support some additional use cases.
Supported use cases
|Description||Sessions flow||Sessions flow with additional methods||Advanced flow|
|Make a payment with any available payment method.|
|Make a partial payment with a gift card and the rest with another payment method.|
|Confirm an additional action on your server.|
|Confirm a redirect on your server.|
|Implement checks on your server, like inventory checks, before making a payment.|
|Update the payment amount before making a payment, for example, when the shopper updates their shopping cart.|
|Implement an express payment method.|
|Change the order of payment methods for an individual transaction.|
|Insert a separate page for the shopper to agree to terms and conditions before making a payment.|
|Integration features||Sessions flow||Sessions flow with additional methods||Advanced flow|
|Number of endpoint requests from your server||1||2 or 3||3|
|Handling redirects||Client-side||Client-side and server-side||Client-side and server-side|
|Handling additional actions||Client-side||Client-side and server-side||Client-side and server-side|
Choose your integration guide
Choose the integration guide to see which platforms support the flow and learn how to integrate it.