Tilopay for developers

Everything you need to build with Tilopay: take payments, automate your banking operations and connect AI agents to your business.

Step 0 — get your sandbox credentials

There are no shared sandbox credentials: every developer registers and receives their own. Do this before any of the four paths.

Register as a developer

For developers

Tilopay gives you four ways to take payments. Start with the four integration paths and pick the one that fits how you build.

Four integration paths →

Tilopay Banking API

Restricted access

A separate product, not a fifth integration path: a Banking-as-a-Service platform with SINPE transfers, IBAN accounts and collections, available in Costa Rica only, on its own infrastructure and with its own credentials.

See the Banking API →

Machine-readable API definition

OpenAPI 3.1 definition of our API: the source of truth for endpoints, parameters and responses. Use it to generate a client or import the API into your tooling.

Tilopay AI tools

Tilopay has AI tools for two different audiences. For the developer who is integrating, the debugging agent. For other AI agents that consume or operate Tilopay, the MCP server and the machine-readable artifacts.

Debugging agent

Understand why a call failed, what a response code means, whether your request has the right shape according to our API definition, and where the answer is documented — without leaving the page you are reading. It cites the page behind every answer, never runs calls against the API and never accepts credentials.

Open it from the side panel of any portal page.

MCP server

Connect Claude, Cursor or your own assistant to your Tilopay account — sales, payment links, refunds — without ever pasting your API credentials.

MCP server →

Machine-readable documentation

llms.txt, the .md version of any URL, openapi.json and mcp.json, so an agent can read the portal without scraping HTML.

Machine-readable documentation →

Reference