Processing online payments

With every payment, capture, or refund on Adyen for Platforms, you can split the funds between any number of accounts in your platform, including your liable account. For example, when a customer pays on your platform, you can split the funds so that a portion goes to your liable account as platform fee, and the sale amount goes to the account holder's account.

You can provide split information through API requests, or if your integration processes payments through stores, you can also create a split configuration to automatically split payments. If you don't provide split instructions, the payments and all associated fees are booked to your platform's liable account.

Supported payment methods

Adyen for Platforms supports a wide range of payment methods, such as major card brands (Visa, Mastercard, American Express, Discover/Diners), Apple Pay, Google Pay, SEPA, iDEAL, and more. Restrictions may apply where Adyen is not in the settlement flow. Reach out to your sales manager to confirm.

Providing split information through API requests

You can split an incoming or outgoing fund transfer into a maximum of 1000 split items, booked to different accounts in your platform, including your liable account.

You can provide split information:

• At the time of payment.
• When capturing a payment.
• When refunding a payment.

To split funds, you'll need to send the splits array. For each split object in the array, you need to specify the following fields:

• account: The accountCode of the account where the split amount will be sent.
• amount.value: The split amount.
• type: When sending the amount to any other account in your platform, set the type to MarketPlace. Other types such as Commission or VAT sends the split amount to your liable account.
• reference: Your unique identifier for the split. While this field is only required in the API if type is MarketPlace, we strongly recommend that you send a reference for all other types. You can use the reference to reconcile the split and the associated payment in the transaction overview and in the reports. Without a reference, the amounts are merged and you will be unable to reconcile the split.

For example, when a customer pays for goods on your platform for USD 400.00, you can split the payment such that:

• USD 300.00 goes to the seller's account as payment for the goods. You'll send the payment to the account of the seller account holder with accountCode 8516026831348764.
• USD 100.00 goes to your liable account as your platform's commission.

Validating split information

Adyen frontend systems only validate the format of the split data. The accounts provided in split data will not be validated by the frontend.

If you provide split data with an account that does not exist, or an account belonging to an account holder with a Closed status, the full amount of the transaction will be sent to the liable account regardless of the original split data.

You will receive a PAYMENT_FAILURE notification of the failed split. You can use Fund transfer to correct any account balances.

Split at payment

To split funds at the time of payment, provide split data in your POST /payments request. You can send split data regardless of your PCI compliance level.

If you do not know what the total split will look like for your account holders at the time of a payment, you can skip providing any split data at payment and instead provide split data at capture. Split data provided at capture overrides any split data provided with the initial payment request.

Below is an example of a /payments request with a split data. To make test payments, refer to Test card numbers.

Payment statuses

Once a payment has reached the SentForSettle state, the transaction will show up in the account as a PENDING_CREDIT transaction. Once Adyen has received the funds for the payment, the transaction will be updated to CREDITED and the funds will be available to pay out on the account.

You can always look at the transaction associated with all accounts on a account holder using the /accountHolderTransactionList call.

Split at capture

Some platforms do not know the final split at point of payment. In this case, you can provide split data with a /payments/{paymentPspReference}/captures request. Note that you can only split at capture for payment methods that support separate captures. For example, you cannot split at capture for iDEAL payments because iDEAL does not support separate captures.

Providing split data at capture overrules data from the original payment request. If you don't send split data in the capture request, then we'll use the split data from the payment authorization.

Partial captures require you to supply split data. If you don't provide split data, then all the funds to go to the liable account.

Split a refund

We recommend that you always provide split data in refunds so that you are always in control and can support different refund scenarios, such as partial and multiple partial refunds.

Chargeback and disputes

You are responsible for all disputes and dispute management. This includes providing first line support to your sub-merchants and the customers of your platform, clearly communicating your contact details on your website or app, and managing all disputes between your customers and your sub-merchants.

Split chargebacks

Chargebacks, by default, deduct according to original split data. Where a chargeback reversal amount does not match the payment amount, funds are deducted entirely from your liable account. You can transfer funds to correct any account balances.

If you want to configure your platform to deduct chargebacks entirely from your liable account instead, reach out to our Support Team. When your platform is liable for chargebacks, you can also book the full amount of chargebacks or chargeback reversals entirely from your liable account regardless of the split. To enable this functionality, contact our Support Team.