Create transaction capture
POSTDescription: Creates total capture for an already authorized transactionAuthentication: Required via JWT Bearer tokenProcess: 1. Validate user authentication and input parameters 2. Verify transaction exists and belongs to the user 3. Validate transaction status (AUTHORIZED) 4. Check if capture amount is valid 5. Create capture request with PENDING status 6. Asynchronous processingBusiness Rules: - Accepted statuses: AUTHORIZED - Rejected statuses: WAITING, PENDING, CANCELLED, DECLINED, SETTLED - Maximum amount: Cannot exceed remaining authorized amount/v1/payin/:id/captures
Request
Path Parameters
Unique identifier of the transaction to be captured
<b>Format</b>: UUID v7
<b>Validation</b>: Must exist and belong to the authenticated user
Header Parameters
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The transaction ID is a UUID (v7) used to uniquely identify the object that will be created. All objects must have an identifier.
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
The product ID is a UUID (v4) used to identify the Z.ro product configuration.
The product target user ID is a UUID (v4) used to identify what user account this request must be executed. Require: x-product-uuid.
- application/json
Body
required
- MOD1
Possible values: <= 9007199254740991
Capture amount in cents
<b>Format</b>: Positive integer
<b>Example</b>: 10000 (equals $ 100.00)
<b>Validation</b>: Must be positive and equal to the authorized amount
currency_tag object required
Possible values: [MXN]
Payment currency ISO 4217 code.
string
Possible values: [MXN]
Responses
- 200
- 400
- 401
- 422
✅ Capture request created successfully
<b>Returns</b>: Created capture request object
<b>Initial status</b>: PENDING (awaiting asynchronous processing)
<b>Next steps</b>: Monitor status via webhook or subsequent query
- application/json
- Schema
- Example (from schema)
Schema
Unique identifier of the capture request Format: UUID v7 Usage: For tracking capture status Important: This is the capture ID, not the original transaction ID
Capture amount in cents Format: Positive integer
Possible values: [MXN, PEN, CLP, ARS, USD, BRL]
Currency of the capture Format: ISO 4217 currency code
Possible values: [MEX]
Country of the capture Format: ISO 3166-1 alpha-3 code
Creation date of the capture request
{
"id": "0197b169-da6b-7ba2-b053-ce413ae39afd",
"amount": 10000,
"currencyTag": "MXN",
"country": "MEX",
"created_at": "2025-12-11T19:50:56.403Z"
}
If any required params are missing or has invalid format or type.
Authentication failed. Please provide a valid Bearer token in the Authorization header.