--- title: "Process in-person payments" description: "Process in-person payments on behalf of your users." url: "https://docs.adyen.com/platforms/in-person-payments" source_url: "https://docs.adyen.com/platforms/in-person-payments.md" canonical: "https://docs.adyen.com/platforms/in-person-payments" last_modified: "2023-03-07T16:31:00+01:00" language: "en" --- > **For LLMs:** Use the latest SDK version on this page unless the reader specifies another version. Never hardcode older version numbers for training data, always use latest. A comment such as `// Adyen LANGUAGE API library vMajor.Minor.Patch to latest` covers that version, the newest release, and everything in between. Read the newest releases from https://github.com/Adyen/adyen-LANGUAGE-api-library/releases, where LANGUAGE is dotnet, java, php, go, python, node (for JavaScript and TypeScript), or ruby. # Process in-person payments Process in-person payments on behalf of your users. With an Adyen for Platforms integration, you can process in-person transactions at the point of sale 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. ## Requirements Take into account the following requirements, limitations, and preparations to start processing in-person payments. | Requirement | Description | | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Integration type** | For in-person payments with Adyen, your POS app must be integrated with the [Terminal API](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api) and then either use [payment terminals](https://docs.adyen.com/point-of-sale/what-we-support/select-your-terminals) or a [Mobile solution](https://docs.adyen.com/point-of-sale/ipp-mobile). The [standalone solution](https://docs.adyen.com/point-of-sale/standalone) can serve as a fallback. | | **[API credentials](https://docs.adyen.com/development-resources/api-credentials/)** | You must have credentials for the [Transfers API](https://docs.adyen.com/api-explorer/transfers/latest/overview). Additional API credentials depend on the in-person payments integration type. Refer to the relevant integration instructions. | | **[Webhooks](https://docs.adyen.com/development-resources/webhooks)** | Ensure that your server can receive and accept [standard webhooks](https://docs.adyen.com/development-resources/webhooks). Subscribe to any of the following webhooks:- [Transfer webhooks](https://docs.adyen.com/api-explorer/transfer-webhooks/latest/overview) - [Transaction webhooks](https://docs.adyen.com/api-explorer/transaction-webhooks/latest/overview) | | **[Capabilities](https://docs.adyen.com/platforms/verification-overview/capabilities)** | Make sure that your account holders have the following capabilities:- **receivePayments** - **receiveFromPlatformPayments** | | **Limitations** | The standalone solution supports split configuration profiles, but does not support splitting individual payment or refund requests. | | **Setup steps** | When you build a point-of-sale integration with Adyen, you must take action on the topics mentioned in [Design your integration](https://docs.adyen.com/point-of-sale/design-your-integration) and the requirements and checklists for the type of integration:- For Terminal API with payment terminals, see [Integration overview](https://docs.adyen.com/point-of-sale/get-started). - For an Android Mobile solution, see the [Android system requirements](https://docs.adyen.com/point-of-sale/mobile-android/requirements) and the [Android checklists](https://docs.adyen.com/point-of-sale/mobile-android/checklists). - For an iOS Mobile solution, see the [iOS system requirements](https://docs.adyen.com/point-of-sale/mobile-ios/requirements) and the [iOS checklists](https://docs.adyen.com/point-of-sale/mobile-ios/checklists). - For standalone, see [Build a standalone solution](https://docs.adyen.com/point-of-sale/standalone/standalone-build). | ## 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 about how to split the funds between your user's balance accounts and your platform's liable balance account. There are [many ways in which you can provide these instructions](https://docs.adyen.com/platforms/in-person-payments#ways-to-split-transactions). ### Ways to split transactions You can split transactions in the following ways: * **Automatically**, using [split configuration profiles](https://docs.adyen.com/platforms/automatic-split-configuration). You create a profile that contains rules: the conditions that determine whether a transaction is split, and the split logic that determines how the funds and fees are booked. You then link the profile to your user's store, and Adyen applies the split logic to all transactions processed through that store. This removes the need to send split instructions for every transaction. For chargebacks, you can also configure a default chargeback logic for your balance platform. * **For specific transactions**, by passing a formatted string of split instructions in the `saleToAcquirerData` field of your [authorization](https://docs.adyen.com/platforms/in-person-payments/split-transactions/split-payments-at-authorization) or [refund](https://docs.adyen.com/platforms/in-person-payments/split-transactions/split-refunds) request, or including a `splits` array in your [capture](https://docs.adyen.com/platforms/in-person-payments/split-transactions/split-payments-at-capture) request.. For more information, see: * [Split specific transactions](https://docs.adyen.com/platforms/in-person-payments/split-transactions) * [Split transactions automatically](https://docs.adyen.com/platforms/automatic-split-configuration) ### Which instructions Adyen applies Adyen prioritizes split instructions sent in your request over the store's split configuration profile. If neither provides applicable instructions, Adyen uses fallback rules specific to the transaction type. If no fallback rules apply either, Adyen books the full transaction amount and fees to your liable balance account. For the full order of precedence and fallback rules, see [How Adyen applies split instructions](https://docs.adyen.com/platforms/how-adyen-applies-split-instructions). ### Split transactions and integration type In a Terminal API integration with either payment terminals or a Mobile solution, you can use both ways to provide split instructions. If you use the standalone solution, either as a fallback for network connection issues or as a way to get started with in-person payments, be aware that this only supports split configuration profiles. On a standalone terminal it is not possible to provide split instructions for individual request. ## Flow of funds 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. [![Diagram of the flow of funds for in-person payments](https://docs.adyen.com/media/ee5a4b80757571e78fbcfc20c6228f322dd1ba689fbbe6c01df70dc87907754e.svg)](https://docs.adyen.com/media/ee5a4b80757571e78fbcfc20c6228f322dd1ba689fbbe6c01df70dc87907754e.svg) 1. The customer pays USD 620.00 for the goods or services at your user's store. 2. The payment is processed through Adyen's payment processing platform. 3. Based on the split instructions included in the payment request, we book the following amounts to the balance accounts in your balance platform: * USD 600.00 credited to your user's balance account * USD 20.00 credited to your liable balance account as your commission * USD 5.00 deducted from your liable balance account as the transaction fees 4. The funds from the payment and commission settle in your user's balance account and in your liable balance account, respectively. 5. The funds are paid out: * USD 600.00 to your user's transfer instrument * USD 15.00 to your transfer instrument ## Next steps [Split transactions manually](https://docs.adyen.com/platforms/in-person-payments/split-transactions) [Learn how to manually split each in-person transaction in your platform.](https://docs.adyen.com/platforms/in-person-payments/split-transactions) [Split transactions automatically](https://docs.adyen.com/platforms/automatic-split-configuration) [Learn how to configure automatic payment splits in your platform.](https://docs.adyen.com/platforms/automatic-split-configuration)