Process in-person payments

When using the platform setup, you can onboard your users with point-of-sale integrations to accept in-person payments (IPP). You must send payment and refund requests on behalf of your users, as well as manual capture requests if desired. In your requests, you can specify how to split the resulting funds.

Before you begin

To process in-person payments for your user, you will need to:

• Set up a platform setup integration with:

  • Account holders (Users)
  • Balance accounts
  • Physical stores with configured payment methods.

• Ensure that your server can receive and accept webhooks.

• Have access to the API credentials for Management API.

• Design and set up your in-person payments integration:

  • Choose the payment terminal models you want to use.
  • Choose between cloud or local communications and build your cloud integration or local integration.
  • Configure the in-store network.
  • Implement the payment flow with Terminal API.
  • Order, assign, and configure payment terminals.

Split in-person transactions

Transactions often need to be split between the balance accounts in your platform. With every payment, capture, or refund request, you can choose how to split these funds between your platform's balance accounts, including your liable balance account.

You can split funds as many times as you need and into any number of balance accounts in your platform. For example, when a customer pays, you can split the funds into multiple parts:

• The sale amount that goes to your user's first balance account.
• Your platform's commission that goes to your liable account.
• The tip that goes to your user's first balance account.
• The transaction fees that are charged to your user's first balance account.

If you do not provide any split information, the entire transaction amount will be booked against your platform's liable balance account.

Validating split information

To split a transaction, you must provide the split information in your payment, capture, or refund request. The APIs that you use for these requests validate the format of the split data, but do not validate the balance accounts specified in the split data.

Payments, captures, and refunds may succeed, but the funds are not split if the balance account specified in the request does not exist or is linked to an account holder with a closed status. When this happens, the full amount of the transaction is sent to your platform's liable balance account.

To correct balances, you can transfer funds between balance accounts in your platform.

Reversed settlements

When using the Sales Day Settlement model, Adyen settles payments to the balance accounts in your platform, regardless of whether we have already received the funds from the card scheme or payment method. However, if we do not receive the funds within 30 days after the payment's capture, we reverse the settlement. The funds are deducted from your user's balance account and the payment then reaches a SettledReversed status in the Customer Area and the Payment Accounting Report.

By default, the reversed amount is deducted from the balance accounts in your platform according to the split data in the original payment or capture request. However, you can choose to deduct the entire reversed amount from your liable balance account instead. To do this, contact our Support Team.

In the Balance Platform Customer Area, reversed transfers have the status Capture reversed. In the Balance Platform Accounting Report, you can recognize reversed transfers by the following values:

• Type: captureReversal
• Status: reversed