MPC
What is MPC
Multiple Partial Captures (MPC) is a functionality that allows you to authorize a total amount and capture it in multiple parts over time.
It serves business models that require capturing payments progressively.
For example: issuing tickets as they are confirmed or charging when items are back in inventory and ready to be shipped.
To use this functionality, integrate with Create Payments V2.
Use Cases
This functionality is especially useful for:
- Airlines: Authorize the total ticket amount and capture partially as seats are confirmed.
- Retail with partial shipments: Ideal for marketplaces where orders are dispatched by multiple sellers and items are shipped at different times.
- Staged service delivery: Capture payments as project phases are completed.
Offline Mode can be configured with any processor, even those that support MPC natively.
During integration, you will be informed if the processor supports MPC. Some processors may require specific credentials or additional configurations.
How MPC Works
An MPC flow works as follows:
- Authorization: The customer authorizes the total transaction amount.
- Multiple captures: The store captures parts of the authorized amount on different dates.
- Consolidation: The system manages multiple captures and sends them to the processor according to configured rules:
- Online processors: Captures are sent in real-time after authorization.
- Offline processors: Captures are sent after authorization, when any of the following conditions are met:
- The defined capture deadline is reached.
- The total authorized amount is captured.
- The merchant sends
"final_capture": true
in the API request.
Configuration and Requirements
The MPC functionality requires prior activation and the following configuration parameters:
Main Configuration
The following table documents the main configuration for MPC:
Parameter | Description | Allowed Values | Default Value |
---|---|---|---|
Status | Activates or deactivates MPC | on / off | off |
Operating Time Zone | Operating time zone to calculate business days | Valid time zone | UTC |
Capture Cutoff Days | Days allowed to capture after authorization | 0-45 | 7 |
Capture Cutoff via API | Allows indicating final capture using "final_capture": true in API | true / false | false |
Configure MPC in the Admin
Perform the following MPC tasks in the Admin:
- Configure MPC parameters.
- Monitor pending captures.
- Check the scheduled processing date.
- View the remaining amount available for capture.
To configure Multiple Partial Captures from the Admin:
- Access the Admin Portal.
- Go to the Commerce section.
- Select Payment Configurations.
- Enable the Enable multiple partial captures option.
- Define the capture window: From 1 to 45 days after the initial authorization.
This configuration applies only to Offline Mode.
The days configured for partial capture can be modified at any time.
However, changes do not apply to transactions that have already started partial captures.
The eligibility period is defined at the time of authorization and cannot be modified later.

In the order detail, the capture deadline will be displayed. On that date, all pending captures will be processed.

At the end of the eligibility period or when using the
final_capture
flag, the remaining amount will be canceled.
Operating Modes
Discover how to operate MPC with DEUNA.
Partial capture limits:*
- Offline Mode: No technical limit from the platform.
- Online Mode: Limits depend on each processor's rules.
Offline
Applies when the acquirer/processor does not handle multiple captures natively.
Captures are consolidated and sent to the processor when any of the following conditions are met:
- The capture deadline is reached.
- The total authorized amount is captured.
- The merchant sends
final_capture
with the valuetrue
in the request.
Example:
{
"amount": 100,
"final_capture": "true"
}
Status:
While pending captures exist, the status will be partial capturing
.
If the total amount is completed, the status will change to captured
.
If the deadline is reached without capturing the total, the status will be partial captured
.
Processors under settlement flow (Elavon, Amex, UATP, BBVA)
These processors always operate in offline mode.
The status remains partial capturing
until:
- The total is captured → status
capturing
→ post-settlement → statuscaptured
. - The total is not captured within the deadline → status
partial captured
.
Online
Captures are sent in real-time to the processor, if it supports MPC natively.
Some processors require specific credentials or enablements (for example: Stripe, Adyen).
Status
Partial captures generate status partial captured
.
When capturing the total, the status automatically changes to captured
.
Rules
- The sum of all captures cannot exceed the authorized amount.
- Captures are not allowed outside the eligibility period or after sending
"final_capture": true
.
Supported Processors:
Offline Flow:
- Stripe, Elavon, Worldpay
Updated 2 days ago