canonical: https://jentic.com/apis/conekta.com/conekta

# Conekta API

Conekta is a Mexican payment processor and the API supports the local payment methods that matter in Mexico, including cards, OXXO cash vouchers, SPEI bank transfers, and digital wallets. The surface covers orders and charges, customers and saved payment methods, subscription billing with plans and pause or resume, payment links and hosted checkouts, payouts and transfers, antifraud blacklist rules, balances and transactions, and webhooks for downstream eventing. It is the standard integration for Latin American merchants who need OXXO and SPEI alongside cards.

## For AI agents

Process card, OXXO, SPEI, and wallet payments in Mexico through Conekta: create orders, manage subscriptions and customers, issue refunds and payouts, and listen on webhooks.

## Scope

Does not handle accounting, tax filing, or payroll - use for payment processing, subscriptions, and payouts in Mexico only.

## Capabilities

- Create an order with one or more line items and a charge against a customer
- Tokenize a card and store it as a payment method on a customer
- Generate an OXXO cash voucher or SPEI reference for a Mexican shopper
- Run a subscription against a plan, including pause and resume operations
- Issue a refund or capture against an existing order
- Send a payout to a beneficiary bank account
- Subscribe to webhooks for order, charge, and subscription events

## Use cases

### Cross-Method Mexican Checkout

Accept card, OXXO cash voucher, and SPEI bank transfer payments from Mexican shoppers in a single checkout. POST /orders creates the order, /tokens turns card data into a token, and the order's charges are configured to the chosen method. Mexican e-commerce merchants integrate this to reach the large segment of buyers who pay in cash at OXXO or via SPEI rather than by card.

Example prompt: Create an order for MXN 1499.00 for customer cus_44 with method oxxo_cash and return the OXXO reference and barcode URL

### Subscription Billing for Latin American SaaS

Run recurring billing against Mexican customers using Conekta plans and subscriptions. POST /plans creates a billing plan, POST /subscriptions enrols a customer on it, and the pause and resume endpoints handle dunning and retention scenarios. SaaS and digital-services companies use this to localize their billing for the LATAM market.

Example prompt: Create a monthly plan 'Pro 299' priced at 29900 MXN cents, then subscribe customer cus_77 to it with a card token from /tokens

### Payouts and Marketplace Disbursements

Pay out balances to suppliers, contractors, or marketplace sellers in Mexico. POST /payout_orders or POST /transfers moves funds to a beneficiary's CLABE bank account, and the balance and transactions endpoints reconcile what was paid. Marketplaces and gig platforms use this to keep funds in Mexico for both collection and disbursement without crossing borders.

Example prompt: Send a payout of MXN 1200.00 to beneficiary CLABE 012180001234567890 with reason 'June marketplace earnings'

### Antifraud and Webhook-Driven Operations

Reduce fraud and keep downstream systems synchronized with payment state. /antifraud/blacklist/rules lets agents add risky cards or emails, and /webhooks subscribes to charge.paid, order.paid, and subscription.canceled events. Operations teams use this to push events into a CRM and tighten antifraud rules in real time as charge-back patterns emerge.

Example prompt: Subscribe a webhook with URL https://app.example.com/hooks for charge.paid events and add fraud@example.com to the antifraud blacklist

### Agent-Driven Payment Operations via Jentic

Let an AI assistant resolve customer payment issues by issuing refunds, generating vouchers, or pausing subscriptions in chat. Through Jentic the agent searches by intent, loads the schema for the relevant Conekta operation, and executes the call without the developer wiring auth or pagination. This is suited to bilingual support bots covering Mexican customers.

Example prompt: On the prompt 'reembolsa el pedido o-9911', call POST /orders/{id}/refunds for that order and confirm the refund id in Spanish

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /orders | Create an order with charges |
| POST | /orders/{id}/refunds | Refund an order |
| POST | /customers | Create a customer |
| POST | /tokens | Tokenize a card |
| POST | /subscriptions | Create a subscription |
| POST | /subscriptions/{id}/pause | Pause a subscription |
| POST | /payout_orders | Send a payout to a beneficiary |
| POST | /webhooks | Register a webhook subscription |

## Key resources

- **Orders** — Order creation, capture, refund, and cancellation
- **Charges** — Charges associated with an order
- **Customers and Payment Methods** — Stored customers and tokenized payment methods
- **Plans and Subscriptions** — Recurring billing plans, subscriptions, pause and resume
- **Tokens and Checkouts** — Card tokenization and hosted checkout sessions
- **Payouts and Transfers** — Send funds to beneficiary bank accounts
- **Webhooks and Events** — Outbound event subscriptions and event log
- **Antifraud** — Blacklist rules for cards, emails, and devices
- **Balance and Transactions** — Account balance and transaction ledger

## Why Jentic

- **Setup:** Wiring Conekta by hand means learning its bearer auth, building order, subscription, and payout calls for the Mexican market, and handling payment tokens and webhooks yourself. Through Jentic you install once, import Conekta from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Conekta puts the order and subscription ids in the URL path (/orders/{id}/refunds, /subscriptions/{id}/pause), so a rule can pin your agent to acting on a specific order or subscription. You choose the operations it may call, so you can allow order and customer creation while leaving refunds or subscription pauses out unless you add them.
- **Credential handling:** Your Conekta bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a payment order' or 'start a subscription', and Jentic returns the matching Conekta operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Global payment platform with Latin American support including OXXO
- **Adyen Account Service** — Global acquirer with broad local-method coverage
- **Braintree** — PayPal-owned processor with cards and digital wallets

## FAQ

### What authentication does the Conekta API use?

The API uses HTTP bearer authentication. Pass your Conekta private API key (issued in the Conekta Panel) in the Authorization header as 'Bearer {key}'. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt or logs.

### Can I generate OXXO and SPEI references with the Conekta API?

Yes. When creating an order via POST /orders, set the charge's payment-method type to oxxo_cash or spei_recurrent. The response returns the OXXO reference and barcode for cash payment, or the SPEI CLABE reference for bank transfer.

### What are the rate limits for the Conekta API?

Conekta applies tenant-specific rate limits, typically a few hundred requests per minute per private key, with bulk operations throttled separately. Agents should add backoff on HTTP 429 responses; Jentic surfaces these as structured errors rather than retrying silently.

### How do I create a subscription through Jentic?

Run the Jentic search query 'create a Conekta subscription on a plan', load the returned operation (POST /subscriptions), and execute it with the customer id, plan id, and a card token. Use POST /subscriptions/{id}/pause and /resume to manage the subscription lifecycle.

### Is the Conekta API free to use?

The API itself is free; Conekta charges per processed transaction at rates set in your merchant contract. There are typically no separate API fees beyond the per-transaction processing cost.

### Can I send payouts to Mexican bank accounts?

Yes. POST /payout_orders sends funds from your Conekta balance to a beneficiary's CLABE account via SPEI. POST /transfers moves funds between accounts you control. Both are reflected in the balance and transactions endpoints for reconciliation.

### Can I limit what my agent is allowed to do with the Conekta API?

Yes. Because you run Jentic One yourself, your own rules decide which Conekta operations the agent may call, so you can allow order and customer creation while leaving refunds or subscription pauses out unless you add them. Conekta puts the order and subscription ids in the URL path, such as /orders/{id}/refunds and /subscriptions/{id}/pause, so a rule can pin the agent to acting on a specific order or subscription. Your Conekta bearer token is stored encrypted by your own instance and injected only at execution time, so it never enters the agent's prompt or logs.