Skip to main content
POST
Preauthorize an amount for a subscription without making the actual charge to the card. Preauthorization reserves funds and verifies that the card has sufficient availability.

Required Headers

string
required
Merchant authentication token
string
required
Basic authentication (Basic Auth)
string
required
Unique identifier of the merchant invoking Card Payment services
string
required
Unique tracking identifier for the request
string
required
Must be “application/json”

Request Body Parameters

string
required
Identifier of the subscription for which the payment is preauthorized
string
Unique transaction identifier provided by the client. If not provided, the system generates one automatically.
string
required
Currency code for transaction processing (e.g., “COP”, “PEN”, “USD”)
number
required
Amount to preauthorize. Must be a positive value.
number
required
Processing tax associated with the transaction. If no tax will be charged, send 0.

Validation Rules

Required Fields

Allowed Values

currency

  • COP - Colombian Peso

Common Validation Error Messages

The following are common validation error messages returned by the API (in Spanish):
  • :attribute es obligatorio. - Required field missing
  • :attribute debe ser una cadena de texto. - Invalid data type (expected string)
  • :attribute debe ser un número. - Invalid data type (expected numeric)
  • :attribute no puede tener más de :max caracteres. - Maximum length exceeded
  • :attribute debe ser mayor o igual a :min. - Minimum value not met
  • :attribute no es válido. - Invalid value

Response Fields

Success Response (200 OK)

string
required
Response code. Value: "AUTHORIZED" when authorization is successful
boolean
required
Operation status. true when successful, false when there is an error
string
required
Descriptive message about the authorization result
object
required

HTTP Status Codes

Response Codes

Transaction Types

Pre-Authorization (PRE_AUTH_TRANSACTION)

  • Type: PRE_AUTH_TRANSACTION
  • Status: APPROVED (success) or DECLINED/ERROR (failure)
  • Purpose: Reserve funds without capturing them
  • Next Step: Requires an additional capture step to charge the funds

Supported Currencies

The currency field must be one of the allowed values according to the Currency enum. Example:
  • COP: Colombian Peso

Headers

X-Merchant-ID
string
required

Unique identifier of the Merchant invoking Card Payment services. Should not be used to authenticate end users.

X-Request-ID
string
required

Tracking identifier associated with the request, used to establish a correlation_id between ecosystem components.

Token-Top
string
required

Token for authentication.

Authorization
string
required

Basic authentication.

Body

application/json
reference_id
string<uuid>
required
Example:

"ORDER-123456"

subscription_id
string<uuid>
required
Example:

"550e8400-e29b-41d4-a716-446655440000"

currency
string
required
Example:

"COP"

amount
number
required
Required range: x >= 0
Example:

1500

tax
number
required
Required range: x >= 0
Example:

0

Response

Successful authorization. A new transaction of type PRE_AUTH_TRANSACTION is created.

Preauthorization response. Creates a new transaction of type PRE_AUTH_TRANSACTION.

code
string
required

Response code. Value: 'AUTHORIZED' when authorization is successful

Example:

"AUTHORIZED"

status
boolean
required

Operation status. true when successful, false when there is an error

Example:

true

message
string
required

Descriptive message about the authorization result

Example:

"Pago autorizado exitosamente"

data
object
required