Conekta Mexico Payment Gateway API
Conekta Mexico payment gateway REST API for Mexican developers and businesses to accept cards, OXXO cash vouchers, SPEI bank transfers, and digital wallets with developer-friendly documentation and Banorte bank integration for modern Mexico e-commerce. Enables AI agents to manage card payment processing for Mexico e-commerce automation, handle OXXO cash voucher generation for Mexico offline payment automation, access SPEI bank transfer for Mexico instant transfer automation, retrieve payment status and webhook for Mexico order confirmation automation, manage subscription and recurring payment for Mexico subscription automation, handle refund processing for Mexico order management automation, access marketplace split payment for Mexico platform automation, retrieve anti-fraud scoring for Mexico payment security automation, manage customer and card tokenization for Mexico recurring automation, and integrate Conekta with Mexican startups, SaaS, and marketplace platforms for end-to-end Mexico developer payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Mexico payments. PCI-DSS, CNBV. Private/Public keys. MX. Card and payment data.
⚡ Reliability
Best When
A Mexican startup or developer wanting AI agents to automate OXXO, SPEI, and card payment acceptance through Conekta's developer-friendly Mexico payment API backed by Banorte banking infrastructure.
Avoid When
BANXICO AND CNBV REGULATORY COMPLIANCE: Conekta operates under Banco de México and CNBV regulations; automated payment operations must comply with Mexican payment regulations; automated high-value payment without required merchant verification creates regulatory issues. OXXO VOUCHER ASYNC PAYMENT: OXXO vouchers require customer to physically visit OXXO store to pay; automated order fulfillment must implement async confirmation; automated immediate order fulfillment after OXXO order creates orders with unconfirmed cash payment. CARD TOKEN SINGLE USE: Conekta card tokens are typically single-use unless customer object with card is created; automated recurring billing must create Conekta customer with saved card; automated single-charge-token reuse creates token already used error. WEBHOOK SIGNATURE VERIFICATION: Conekta webhooks include HMAC signature; automated webhook processing must verify signature before processing; automated unverified webhook creates spoofed payment notification vulnerability.
Use Cases
- • Processing OXXO cash payments from Mexico offline commerce agents
- • Accepting SPEI bank transfers from Mexico developer payment agents
- • Managing card subscriptions from Mexico SaaS billing agents
- • Generating payment plans from Mexico installment commerce agents
Not For
- • Pan-LatAm payments (Conekta is Mexico-only; use Kushki or EBANX for multi-country)
- • Enterprise Mexico payments at highest volume (use BBVA Mexico for enterprise banking)
- • Physical POS (Conekta is online-focused; use Clip for Mexico SMB in-person)
Interface
Authentication
Conekta uses private API key and public API key for authentication. REST API with JSON. Mexico City, Mexico HQ. Founded 2012 by Luis Curiel and Hector Ceja. Acquired by Banorte in 2023. Products: OXXO, SPEI, card processing, subscriptions, marketplace split, anti-fraud. SDKs: PHP, Python, Node.js, Ruby, Java, .NET, Go. CNBV regulated. PCI DSS. 15,000+ Mexican merchants. Competes with Clip and MercadoPago for Mexico developer payments.
Pricing
Mexico City MX. Banorte subsidiary. Per-transaction fees in MXN. RFC (Mexican tax ID) required.
Agent Metadata
Known Gotchas
- ⚠ PRIVATE KEY vs PUBLIC KEY API SCOPE: Conekta uses private key (sk_) for server-side charge operations and public key (pk_) for client-side tokenization; automated server-side payment must use private key; automated public key use for charge creates permission insufficient error
- ⚠ OXXO EXPIRY DATE REQUIRED: OXXO cash voucher requires explicit expiry date configuration; automated OXXO checkout must set appropriate expiry (recommended: 3-7 days); automated OXXO without expiry creates default expiry that may be too short or long for business model
- ⚠ CUSTOMER OBJECT REQUIRED FOR SUBSCRIPTION: Conekta subscription billing requires a Customer object with saved payment source; automated subscription must first create Customer with payment method; automated charge-token subscription without Customer object creates subscription creation error
- ⚠ IDEMPOTENCY KEY PREVENTS DUPLICATE CHARGES: Conekta supports idempotency key for charge creation; automated retry must include same idempotency key; automated retry without idempotency creates duplicate charge if original succeeded but response was lost
- ⚠ SPLIT PAYMENT ORDER ID UNIQUENESS: Conekta marketplace split requires unique external_id per split payment order; automated marketplace payment must generate unique order ID; automated same external_id for retry creates duplicate order conflict
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Conekta Mexico Payment Gateway API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.