- Checkout API<\/a><\/li>
- Transfers API<\/a><\/li><\/ul><\/td>\n<\/tr>\n
\n Webhooks<\/a><\/strong><\/td>\n Ensure that your server can receive and accept standard webhooks<\/a>.
Subscribe to any of the following webhooks:- Transfer webhooks<\/a><\/li>
- Transaction webhooks<\/a><\/li><\/ul><\/td>\n<\/tr>\n
\n Capabilities<\/a><\/strong><\/td>\n Make sure that your account holders have the following capabilities: - receivePayments<\/strong><\/li>
- receiveFromPlatformPayments<\/strong><\/li>
- sendToTransferInstrument<\/strong><\/li><\/ul><\/td>\n<\/tr>\n
\n Limitations<\/strong><\/td>\n If an account holder does not have the receiveFromPlatformPayments<\/strong> capability in a valid<\/strong> state, the funds cannot be allocated to their balance account. The full amount is booked to your liable balance account.<\/td>\n<\/tr>\n \n Setup steps<\/strong><\/td>\n When you build your online payments integration, choose between the following server-side flows: - [Sessions flow]<\/strong> (\/online-payments\/build-your-integration\/sessions-flow): your server makes a single Checkout API request to the \/sessions<\/a> endpoint.<\/li>
- [Advanced flow]<\/strong> (\/online-payments\/build-your-integration\/advanced-flow): your server makes three Checkout API requests to the \/paymentMethods<\/a>, \/payments<\/a>, and \/payments\/details<\/a> endpoints.<\/li><\/ul>The advanced flow supports more use cases. However, sessions is the default integration that we recommend and that meets the requirements of most online payments integrations.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Split transactions<\/h2>\n
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.<\/p>\n
This means that you must define instructions about how to split the funds between your user's balance accounts and your platform's liable balance account. You can define these instructions in the following ways:<\/p>\n
- \n
- Automatically split all transactions processed through your user's store by setting up split configuration profiles<\/a>.<\/li>\n
- Split transactions by defining instructions for each API request. The instructions you provide in your API requests override the instructions you defined in your split configuration profiles.<\/li>\n<\/ul>\n
If you do not provide any split instructions in a split configuration profile or through an API request, the whole transaction amount and fees are booked to your liable balance account.<\/p>\n
For more information, see Split transactions<\/a>.<\/p>\n
Flow of funds<\/h2>\n
The following diagram shows the flow of funds from the moment your user's customer pays to when your user's and your platform's funds are paid out.<\/p>\n
- Split transactions by defining instructions for each API request. The instructions you provide in your API requests override the instructions you defined in your split configuration profiles.<\/li>\n<\/ul>\n
- [Advanced flow]<\/strong> (\/online-payments\/build-your-integration\/advanced-flow): your server makes three Checkout API requests to the \/paymentMethods<\/a>, \/payments<\/a>, and \/payments\/details<\/a> endpoints.<\/li><\/ul>The advanced flow supports more use cases. However, sessions is the default integration that we recommend and that meets the requirements of most online payments integrations.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
- receiveFromPlatformPayments<\/strong><\/li>
- Transaction webhooks<\/a><\/li><\/ul><\/td>\n<\/tr>\n
- Transfers API<\/a><\/li><\/ul><\/td>\n<\/tr>\n
![\"\"](\"\/user\/pages\/docs\/05.platforms\/23.online-payments\/platform_ecom.svg\")
\n<\/a><\/p>\n![\"\"](\"https:\/\/docs.adyen.com\/user\/pages\/docs\/05.platforms\/23.online-payments\/platform_ecom.svg\")
"}}