Conekta

Conekta is Mexico's payment gateway: one integration to take cards, SPEI bank transfers and cash payments in Mexican pesos. Its own pitch is "una sola integración para todo México" — a single integration for all of Mexico. The official connector is a hosted MCP server (https://mcp.conekta.com/mcp), published by Conekta, that connects your agent to your account's payment operation — the official docs introduce it as a server for "cualquier agente de AI o LLM" (any AI agent or LLM) to work against the Conekta API.

Ask "Show me today's orders" — an example straight from the docs — and the agent pulls your orders and summarizes their status. "What's my available balance?" comes from your account's balance, no dashboard digging. It also works for you: "Create a 500-peso payment link" generates the checkout link, and "Refund Ana Gómez's latest charge" processes the refund. The docs' own pitch: use it to "crear clientes, órdenes y links de pago sin salir de tu flujo de trabajo" (create customers, orders and payment links without leaving your workflow).

What you can ask

• "Show me today's orders and tell me which ones have been paid."
• "What's my available balance in Conekta?"
• "Create a 500-peso payment link and email it to the customer."
• "Refund Ana Gómez's latest charge."
• "Pause Ana Gómez's subscription."
• "Which subscriptions do I have active, and on what plan?"

Whenever a request writes to your account — creating an order, refunding a charge, pausing a subscription — the AI shows you what it's about to do and waits for your confirmation before running it.

What token you need

You need a Conekta private API key — the credential that lets software operate on your account. Don't confuse it with the public key: that one only tokenizes cards in the customer's browser and won't work here.

1. Sign in to the Conekta panel and open the Developers section (left-hand menu) → Ver API Keys → Consultar API Keys de producción (view production API keys).
2. If this is your first integration, click Crear nueva llave privada (create a new private key) and give it an alias. The key is displayed only once — copy it right then and keep it somewhere safe. Conekta allows up to 10 private keys in production and another 10 in test.
3. Paste it when TerminalSync asks for CONEKTA_API_KEY. It's stored encrypted in the app's Secrets and sent to the server as the Authorization: Bearer … header Conekta expects.

Official notes on the key: only Administrator and Developer roles can manage API keys, and if you lose one or suspect it leaked, Conekta recommends generating a new key and reconfiguring the integration (deleted keys can't be recovered).

Honest disclosure: this is a server hosted by Conekta (https://mcp.conekta.com), not something running on your computer — your requests travel to Conekta's server, which answers with data from your account. It reads and writes: it can create orders, customers, plans and payment links, refund charges, and pause, cancel or resume subscriptions. What the agent can do is bounded by your private key — the same access your account has through the API — and the MCP docs describe no server-side confirmation step (that confirmation is requested by TerminalSync before every write). The data comes from your Conekta account, and verifying it is your responsibility.

Why it shows as Coming soon: while preparing this card (2026-10-15), the server's documented address (mcp.conekta.com) was not published in Conekta's DNS, so it can't be connected to yet. The card ships with the official documented configuration and will be enabled once the endpoint answers and we've re-verified it.