# Process payments on the Lite account type 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): - Visa - Mastercard - [Apple Pay](https://www.checkout.com/docs/payments/payment-methods/apple-pay.md) - [Cartes Bancaires](https://www.checkout.com/docs/payments/payment-methods/cartes-bancaires.md) - [Google Pay](https://www.checkout.com/docs/payments/payment-methods/google-pay.md) --- ## Request a payment without commission Call the [Request a payment or payout](https://api-reference.checkout.com/tag/Payments/#operation/requestAPaymentOrPayout) 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](https://www.checkout.com/docs/payments/accept-payments/format-the-amount-value.md). > **Information** > > Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md). **Production** `POST` `https://{prefix}.api.checkout.com/payments` **Sandbox** `POST` `https://{prefix}.api.sandbox.checkout.com/payments` ### Request example ```json { "amount": 1000, "currency": "USD", "reference": "ORD-5023", "description": "Three chocolate donuts", "capture": true, "source": { "type": "card", "number": "4242424242424242", "expiry_month": 11, "expiry_year": 2024, "cvv": "100" }, "processing_channel_id": "pc_yghfzjebuiwelerjsk3atodrey", "amount_allocations": [ { "id": "ent_125673kjsdhfksjdhf", "amount": 1000 } ] } ``` --- ## Request a payment with commission 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](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/settlement-reports/financial-actions-by-payout-id-report.md) 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](https://api-reference.checkout.com/tag/Payments/#operation/requestAPaymentOrPayout) 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](https://www.checkout.com/docs/payments/accept-payments/format-the-amount-value.md). - `amount_allocations.commission.amount` – Fixed amount of commission in [minor currency unit](https://www.checkout.com/docs/payments/accept-payments/format-the-amount-value.md), 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. > **Information** > > Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md). **Production** `POST` `https://{prefix}.api.checkout.com/payments` **Sandbox** `POST` `https://{prefix}.api.sandbox.checkout.com/payments` ### Request example ```json { "source": { "type": "token", "token": "tok_4gzeau5o2uqubbk6fufs3m7p54" }, "amount": 1000, "currency": "USD", "reference": "ORD-5023-4E89", "description": "Purchase basket", "processing_channel_id": "pc_hpswyyx23geezflc2ocz3exn4y", "amount_allocations": [ { "id": "ent_125673kjsdhfksjdhf", "amount": 1000, "commission": { "amount": 200 } } ] } ``` --- ## Captures and refunds 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. ### Full captures and refunds 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. ### Partial captures 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: 1. You request an authorization for 100 USD on behalf of your sub-entity, and provide their `id` in the `amount_allocations` object. 2. You submit a partial capture for 50 USD, and omit the `amount_allocations` object from your request. 3. 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. ### Partial refunds 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: 1. You request an authorization for 100 USD on behalf of your sub-entity, and provide their `id` in the `amount_allocations` object. 2. You request a capture for 100 USD with the same `amount_allocations` object as in the authorization. 3. You submit a partial refund for 50 USD, and omit the `amount_allocations` object from your request. 4. 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 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.