API · CoF · Charge

API v1

An MCP tool wraps this operation: Stored cards and bulk collections.

POST /api/v1/processRecurrentPayment

What it does#

Processes a charge with an already tokenized card, without a form.

Authentication#

Requires the API bearer token in the Authorization header — see authentication.

Parameters#

keystringrequired#

Key associated with the customer. Obtained in Admin panel · Platform integrations.

amountstringrequired#

Purchase amount.

currencystringrequired#

Purchase currency in ISO format, for example USD, CRC, GTQ.

orderNumberstringrequired#

Order number, it can be alphanumeric.

capturestringrequired#

Capture and authorize: 1 yes, 0 no.

emailstringrequired#

Cardholder email.

cardstringrequired#

Card token. It must be the v2 token.

hashVersionstring#

Only if you implement hash verification. Values V1 or V2; defaults to V1.

Request example#

The <...> values are placeholders: replace them with your own credentials and data.

{
  "key": "<api_key>",
  "amount": "10.00",
  "currency": "USD",
  "orderNumber": "1213",
  "capture": "1",
  "email": "myemail@exapmle.com",
  "card": "511111_00GOB1111"
}

Response#

{
  "type": "200",
  "response": "1",
  "description": "Transacción aprobada",
  "auth": "123456",
  "tpt": 734329,
  "order_id": "12135",
  "tilopayTransaction": 734329,
  "orderHash": "f3ad85046d249bc7a781eed5285a5ded92045a2e11108063504deec72ec9b338"
}

Error responses#

HTTP 300:

{
  "type": "300",
  "result": "Message error"
}

HTTP 400:

{
  "type": "400",
  "result": "Message error"
}

To interpret a response that is not a success, see how to read an error response.

Last verified: 2026-10-20

View as raw Markdown