API · processTokenize

API v1

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

POST /api/v1/processTokenize

What it does#

Tokenizes a card: returns the URL of the tokenization form.

Authentication#

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

Parameters#

redirectstringrequired#

Site where you wait for the transaction response.

keystringrequired#

Key associated with the merchant.

emailstringrequired#

Cardholder email.

languagestringrequired#

Language [es, en].

firstnamestringrequired#

Cardholder first name.

lastnamestringrequired#

Cardholder last name.

token_versionstring#

Send as value "v2".

Request example#

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

{
  "redirect": "https://urlToRedirect.com",
  "key": "<api_key>",
  "email": "email@user.com",
  "language": "es",
  "firstname": "name",
  "lastname": "lastname",
  "token_version": "v2"
}

Response#

{
  "type": "100",
  "url": "https://secure.tilopay.com/htmls/TOK-5063-740506121440_1648145457file.html"
}

Error responses#

Redirect parameters#

token, code, description, auth, crd, order, tpt, brand, last-digits, tilopay-transaction, OrderHash, returnData.

The card token travels in token and crd; store it with the customer email. Use brand and last-digits to display the saved card. crd only has a value when the card was saved with code = 1.

HTTP 300:

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

HTTP 402:

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

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

Last verified: 2026-10-22

View as raw Markdown