With an Adyen for Platforms integration, you can process online transactions on behalf of your users using Adyen's payment processing platform. For each transaction you process, you can split the funds between your users' balance accounts and your liable balance account, and deduct fees and costs as needed.
Prerequisites
Before you can start processing transactions on behalf of your users, you must:
-
Build an Adyen online payments integration and a checkout UI. When you build your integration:
-
Choose between the following server-side flows:
-
Sessions flow : Your server makes a single Checkout API request to the /sessions endpoint. Learn how to build a checkout UI with components.
-
Advanced flow : Your server makes three Checkout API requests, to the /paymentMethods, /payments, and /payments/details endpoints.
The advanced flow supports more use cases. However, sessions flow is the default integration that we recommend and that meets the requirements for most online payments integrations.
To ease the process of building your online payments integration, we recommend to integrate Adyen's client-side libraries or server-side libraries.
-
- Ensure that your server can receive and accept standard webhooks.
-
- Configure payment methods for the stores in your platform.
- Ensure that your server can receive and accept payment webhooks specific to your platform.
- Have API credentials for the Checkout API.
Split transactions
To make sure that the pay-in, settlement, and payout processes run smoothly for all users' transactions, you must book the funds and fees to the correct balance accounts.
This means that you must define instructions on how to split the funds between your user's balance accounts and your platform's liable balance account. You can either define these instructions in the following ways:
- Automatically split all transactions processed through a specific store by setting up split configuration profiles.
- Split specific transactions by defining instructions manually for each API request you send.
The instructions you provide in your API requests override the instructions you defined in your split configuration profiles.
If you do not provide any split instructions, the whole transaction is booked to your platform's liable balance account, including all associated fees.
For more information, see Split transactions.