A build-to-order Odoo payment provider that accepts Mexican cards, OXXO cash vouchers, and SPEI bank transfers through Conekta, with webhook reconciliation and MXN localization. ECOSIRE builds, installs, and supports it after a scoping call — it is not an instant apps.odoo.com download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo payment provider that accepts Mexican cards, OXXO cash vouchers, and SPEI bank transfers through Conekta, with webhook reconciliation and MXN localization. ECOSIRE builds, installs, and supports it after a scoping call — it is not an instant apps.odoo.com download.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
Conekta registered as a native `payment.provider` with per-record public/private API keys and a test/production environment toggle stored on the provider, not in source
`payment.transaction` subclass driving Conekta's Orders API for card, OXXO, and SPEI in a single unified flow
Client-side card tokenization with inline authorization; the raw PAN never touches the Odoo server or database
OXXO cash voucher generation with the reference and expiry surfaced on the QWeb checkout confirmation and order email
SPEI transfer support that issues a per-order CLABE and holds the transaction pending until the transfer settles
Signature-validated webhook controller at `/payment/conekta/webhook` (`auth='public'`) mapping `order.paid`, `charge.paid`, `order.canceled`, and refund events to the matching transaction
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.
An online or omnichannel retailer already processing with Conekta who needs OXXO, SPEI, and card payments to reconcile automatically inside Odoo instead of being matched by hand in accounting.
Owns month-end close and cash reconciliation. Needs late-settling OXXO and SPEI payments to post to the correct `account.move` automatically, with refunds traceable and auditable from Odoo.
Runs the `website_sale` storefront and wants a native Mexican checkout with OXXO cash, SPEI, and Meses Sin Intereses offered on eligible cards to lift conversion, not a clunky hosted redirect.
Responsible for the deployment. Wants a clean module with a proper `__manifest__.py`, sane `ir.model.access.csv` security, staging UAT, and the source in Git so the business is never locked to a single vendor.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Conekta Payment Gateway for Odoo (Mexico) 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Conekta Payment Gateway for Odoo (Mexico),然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Conekta cards + OXXO + SPEI | All three as native Odoo payment methods | Possible but you build and test each flow | Often card-only or partial coverage | |
| Late OXXO/SPEI reconciliation | Signature-gated webhook auto-posts the move | You must design the async settlement logic | Varies; async handling often weak | |
| Odoo version/edition fit | Pinned to your 17/18/19 + Community/Enterprise | Whatever you build it for | Generic build, may lag your minor | |
| Refunds | Full and partial from the transaction, logged | Build and audit the refund path yourself | Basic refund, partials not guaranteed | |
| MSI installments | Configurable 3/6/9/12 for eligible BINs | Extra engineering to model tiers | Rarely configurable | |
| Security of credentials | Provider record + ir.model.access + record rules | Depends on your discipline | Varies by vendor | |
| Source ownership | Full source + Git repo handover | You own it but carry all the effort | Often obfuscated or license-locked | |
| Support after launch | Post-go-live window + scoped upgrades | Your team maintains it | Ticket queue, variable SLA |
No. This is a build-to-order module. ECOSIRE builds it against your confirmed scope, Odoo version, and edition, then installs and supports it. There is no instant apps.odoo.com download.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call and requirements sign-off we build, test on a staging copy of your database, run UAT with your team, and then deploy with a rollback plan.
Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. We pin the module to your exact minor version and edition so it installs cleanly and upgrades predictably.
A signature-validated Conekta webhook maps the late settlement event to the pending `payment.transaction`, then auto-confirms the `sale.order` and posts the `account.move`. No one has to match late cash or transfer payments by hand.
Yes. Full and partial refunds are issued from the Odoo transaction to Conekta's refund endpoint with audit logging. MSI tiers (3/6/9/12 months) are configurable and offered to eligible card BINs at checkout.
Keys are stored on the `payment.provider` record and access-restricted via `ir.model.access.csv` and record rules — never hardcoded. Cards are tokenized client-side, so the raw PAN never reaches your Odoo server or database.
You get a post-go-live support window for defect fixes and configuration changes, plus the full Git repository so you own the code. Version upgrades and enhancements can be scoped as follow-on work.
A build-to-order Odoo payment provider that accepts Mexican cards, OXXO cash vouchers, and SPEI bank transfers through Conekta, with webhook reconciliation and MXN localization. ECOSIRE builds, installs, and supports it after a scoping call — it is not an instant apps.odoo.com download.