Process payments on the Lite account type

Last updated: November 19, 2025

After your sub-entity has passed onboarding checks and has payment capabilities enabled, you can start processing payments on their behalf.

If you're on the Lite account type, the following payment methods are available in the United Kingdom (UK) and European Economic Area (EEA):

Call the Request a payment or payout endpoint. In the request body, provide the following:

amount
currency
description
capture – The default value is true, which indicates that the payment is to be captured.
source – The source of payment.
processing_channel_id
amount_allocations.id – The sub-entity ID to link the payment with the sub-entity.
amount_allocations.amount – The amount to be credited to your sub-entity's currency account, in minor currency unit.

post

https://api.checkout.com/payments


1{
2  "amount": 1000,
3  "currency": "USD",
4  "reference": "ORD-5023",
5  "description": "Three chocolate donuts",
6  "capture": true,
7  "source": {
8    "type": "card",
9    "number": "4242424242424242",
10    "expiry_month": 11,
11    "expiry_year": 2024,
12    "cvv": "100"
13  },
14  "processing_channel_id": "pc_yghfzjebuiwelerjsk3atodrey",
15  "amount_allocations": [
16    {
17      "id": "ent_125673kjsdhfksjdhf",
18      "amount": 1000
19    }
20  ]
21}

Requesting a payment with commission does not affect how funds are settled between your platform and the sub-entity. In a Lite account type, all funds are settled to your platform.

You can apply commission for reporting purposes by including the amount in the amount_allocations.commission.amount field. It appears in the Financial Actions by Payout ID Report as an additional row.

If you reconcile your platform’s commission outside of Checkout.com’s reporting, you don't have to include the commission amount in the amount_allocations.commission.amount field.

There are three types of commission you can apply on your sub-entities' payments:

A fixed commission
A variable commission calculated as a percentage of the payment
A compound commission which is a fixed commission, with an additional variable commission as a percentage of the payment

Call the Request a payment or payout endpoint. In the request body, provide the following:

amount
currency
reference
description
capture – Default value is true
source – The source of payment.
processing_channel_id – The ID of the processing channel for which you are requesting the payment.
amount_allocations.id – The sub-entity ID to link the payment with the sub-entity
amount_allocations.amount – The amount to be credited to your sub-entity's currency account, in minor currency unit.
amount_allocations.commission.amount – Fixed amount of commission in minor currency unit, if applicable.
amount_allocation.commission.percentage – The percentage of commission, if applicable.

In the following example, the request charges a fixed commission of 2 USD.

post

https://api.checkout.com/payments


1{
2  "source": {
3    "type": "token",
4    "token": "tok_4gzeau5o2uqubbk6fufs3m7p54"
5  },
6  "amount": 1000,
7  "currency": "USD",
8  "reference": "ORD-5023-4E89",
9  "description": "Purchase basket",
10  "processing_channel_id": "pc_hpswyyx23geezflc2ocz3exn4y",
11  "amount_allocations": [
12    {
13      "id": "ent_125673kjsdhfksjdhf",
14      "amount": 1000,
15      "commission": {
16        "amount": 200
17      }
18    }
19  ]
20}

You can link full and partial captures and refunds to the respective sub-entity by always including the amount_allocations object. If you do not include it, we apply the following default logic.

For full captures and refunds without the amount_allocations object, we apply the amount_allocations object provided in the original authorization request, including the commission if provided.

Funds are credited to or debited from your platform’s currency account balance.

For partial captures without the amount_allocations object, we apply the new amount specified to the sub-entity ID from the original capture request. The amount and commission of the original request are not considered. For example:

You request an authorization for 100 USD on behalf of your sub-entity, and provide their id in the amount_allocations object.
You submit a partial capture for 50 USD, and omit the amount_allocations object from your request.
50 USD is captured to your platform's account. The id and amount fields in the amount_allocations object are automatically set to the sub-entity ID and capture amount, respectively.

The split information included in an authorization request is overwritten if split information is also supplied in any subsequent requests. For example, if split information is submitted in both the authorization request and a partial capture request, the information in the partial capture request determines how the funds are split.

For partial refunds without the amount_allocations object, we apply the new amount specified to the sub-entity ID from the original refund request. The amount and commission of the original request are not considered. For example:

You request an authorization for 100 USD on behalf of your sub-entity, and provide their id in the amount_allocations object.
You request a capture for 100 USD with the same amount_allocations object as in the authorization.
You submit a partial refund for 50 USD, and omit the amount_allocations object from your request.
50 USD is debited from your platform's account. The id and amount fields in the amount_allocations object are automatically set to the sub-entity ID and refund amount, respectively.

Incremental authorization is not supported by the amount_allocations object. While it's possible to extend a split payment's authorization validity period, any increase to the amount is ignored when the payment is captured.

Process payments on the Lite account type

Request a payment without commission

Request example

Request a payment with commission

Request example

Captures and refunds

Full captures and refunds

Partial captures

Partial refunds

Incremental authorization