Mexican merchants running Odoo hit a wall the moment checkout meets local reality: a large share of Mexican shoppers pay with OXXO cash or SPEI bank transfer, not international cards, and Odoo core ships no Conekta provider. Teams end up bolting a hosted Conekta link onto the side, then reconciling paid orders by hand in account.move because nothing tells Odoo when an OXXO voucher was actually settled hours or days after the order was placed. Native payment providers assume a synchronous card authorization; the asynchronous cash-and-transfer flow that dominates Mexican e-commerce simply has no home.

This build-to-order module adds Conekta as a first-class Odoo payment provider. We implement a payment.provider record extended for Conekta with its own credentials (public/private API keys, environment toggle) stored on the provider and never in code, plus a payment.transaction subclass that drives Conekta's Orders API. Card charges tokenize client-side and authorize inline; OXXO and SPEI create a pending charge and surface the voucher reference / CLABE back to the customer on the QWeb checkout confirmation. The provider registers payment methods (payment.method) for card, OXXO, and SPEI so Odoo's sale, website_sale, and invoicing flows treat them natively — no side channel.

The reconciliation core is a webhook controller (/payment/conekta/webhook) that validates Conekta's signature, maps order.paid, charge.paid, order.canceled and refund events to the matching payment.transaction via the stored provider reference, and moves the transaction and its sale.order / account.move to the correct state — so an OXXO payment that lands two days later posts and confirms itself with zero manual touch. Refunds are issued from the Odoo transaction (action_refund) straight to Conekta's refund endpoint, with partial-refund support and audit logging. MXN localization covers currency rounding, amount-in-cents conversion, and Meses Sin Intereses (MSI) installment configuration exposed as provider settings so eligible card BINs offer 3/6/9/12-month plans at checkout.

Security follows Odoo conventions throughout: access is governed by ir.model.access.csv plus record rules so only Billing/Accounting roles read raw provider credentials, the webhook endpoint is auth='public' but signature-gated, and all state changes are written server-side, never trusted from the browser. Everything is delivered as a clean installable module with a proper __manifest__.py declaring dependencies (payment, account, website_sale where relevant), pinned to your exact Odoo 17.0, 18.0, or 19.0 minor and Community/Enterprise edition.

Because this is build-to-order, nothing ships until we agree on scope. A short scoping call confirms your Odoo version and edition, which payment methods and MSI tiers you need, your Conekta account setup, and your reconciliation and refund rules. We then build against your requirements, test on a staging copy of your database, run UAT with your team, and deploy with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source and Git repository so you are never locked to us.