Tilopay Banking API

API 1.0.0

With our Banking API you can initiate payments (PIN and SINPE Móvil), check their status, manage your accounts and receive payment event webhooks from your own systems, always limited to the accounts your access token authorizes.

It is a separate product from the payment gateway. It runs on its own infrastructure, with its own host, credentials and authentication. If you already integrate our acquiring API, access to this one is enabled separately.

Here you will find the official endpoints, models and flows for version 1.0.0 of the Banking API.

What it can do#

Payments. Create a payment, fetch it by identifier, list it by account and search it by payment_id, public_id or client_reference; the available methods are PIN and SINPE_MOVIL, in OUT or IN direction. See payment operations.

Accounts. Validate a destination account before transferring, list your accounts with or without balances, check an account balance and request statements asynchronously. See account operations.

Webhooks. Register your encrypted HTTPS destination, see the events you can subscribe to per payment method and the data structure we send in each one. See webhook operations.

Catalogs. Customer identification person types per country. See catalogs.

We also provide GET /api/public/v1/healthz for health checks, plus GET /openapi.yaml and GET /docs with the OpenAPI definition and interactive documentation right on the API host.

Environments#

There are two environments, with the same routes and contracts. The sandbox one:

https://api-baas-sandbox.tilopay.com

Production is the same host without the -sandbox suffix:

https://api-baas.tilopay.com

You can start in sandbox and, when you are ready, we hand over your production credentials as we enable your access.

Machine-readable artifacts#

We publish the full Banking API OpenAPI definition, with open CORS, in two formats:

It is independent from our acquiring API definition (/developers/openapi.json): they are two separate products.

How to get access#

Access is restricted and granted on request, for operations in Costa Rica. To learn about the product and request it, visit baas.tilopay.com, stating estimated monthly volume, use case and systems to integrate.

Where to go next#

  1. Authentication — login, token exchange and Bearer.
  2. Conventions — envelope, correlation, safe retries, pagination and dates.
  3. Response codes — full response_code catalog.

Last verified: 2026-10-09 · Owner: equipo-integraciones

View as raw Markdown