A build-to-order Datatrans payment provider for Odoo that brings Swiss checkout methods — TWINT, cards, PostFinance, Apple Pay — into your Website, eCommerce and Sales flows. ECOSIRE builds, installs and supports it; it is not an off-the-shelf 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 Datatrans payment provider for Odoo that brings Swiss checkout methods — TWINT, cards, PostFinance, Apple Pay — into your Website, eCommerce and Sales flows. ECOSIRE builds, installs and supports it; it is not an off-the-shelf apps.odoo.com download.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Swiss shoppers expect TWINT, PostFinance and Apple Pay at checkout, and card payments that clear 3-D Secure 2 without friction. Odoo ships a payment framework with a handful of built-in providers, but Datatrans — the Swiss PSP most local acquirers route through — is not among them. The result is that merchants either bolt on a redirect to an external hosted page that breaks the Odoo order flow, or leave payments in a half-manual state where sale.order confirmation and account.move posting don't reconcile automatically against what Datatrans actually captured. That gap is exactly where a native provider integration earns its keep.
Native `payment.provider` and `payment.transaction` extension — Datatrans appears as a first-class acquirer in Website eCommerce, portal and Sales checkout
TWINT enabled as a selectable payment method through Datatrans method routing
Credit/debit card acceptance (Visa, Mastercard, and Swiss domestic schemes) via Datatrans
PostFinance Card and PostFinance E-Finance support for Swiss buyers
Apple Pay support through Datatrans' wallet integration
Datatrans Secure Fields for tokenised, on-page card entry (PCI-DSS SAQ-A friendly, buyer stays on your storefront)
ECOSIRE builds a first-class payment.provider integration for Datatrans as a proper Odoo module. We extend payment.provider and payment.transaction with Datatrans-specific fields (merchant ID, sign keys, environment) declared in models/, wire the acquirer into the standard checkout so it appears as a payment option in Website eCommerce, the customer portal and Sales, and implement both integration modes: Datatrans Redirect/Lightbox for hosted PCI-minimal flows and Secure Fields for a tokenised, on-page card entry that keeps the buyer on your storefront. Every card path runs 3DS2 / SCA so you stay inside PSD2 and Swiss regulatory expectations, and TWINT, PostFinance Card/E-Finance and Apple Pay are surfaced as selectable methods through Datatrans' payment-method routing.
Technically, the module is built the Odoo-native way. Authorisation and capture responses are verified against Datatrans' HMAC signature before any state transition, so a spoofed callback can never confirm an order. A dedicated controller receives the server-to-server webhook and drives payment.transaction through _set_pending, _set_done and _set_canceled, which in turn confirms the linked sale.order and lets Odoo post the account.move — giving you true reconciliation instead of guesswork. Refunds are supported from the Odoo backend (full and partial where the linked transaction allows), access is locked down with ir.model.access.csv plus record rules so only Sales/Accounting roles touch provider credentials, and configuration lives in standard settings views. Because it's a normal module, the same transactions are reachable over Odoo's XML-RPC / JSON-RPC API for downstream automation and reporting.
This is a build-to-order engagement, not an instant download. After a short scoping call we confirm your Odoo version (17.0, 18.0 or 19.0), Community vs Enterprise, your exact Datatrans method mix and acquirer setup, then build against your requirements. Typical delivery is 2-4 weeks from confirmed scope. You get the installable source for your version, UAT on a staging database against Datatrans' sandbox, a rollback plan, documentation, a training session, and a defined post-go-live support window. ECOSIRE writes it, installs it, and stands behind it.
Runs an Odoo Website/eCommerce store and already settles through Datatrans with an acquirer. Needs TWINT, cards and Apple Pay in-checkout with automatic order and invoice reconciliation, not a broken external redirect.
Owns `account.move` posting and month-end reconciliation. Wants every captured Datatrans payment to map cleanly to the right Odoo order and invoice, with refunds handled from the backend and a clear audit trail.
Maintains the Odoo instance and other integrations. Needs a clean, upgradable module with proper security rules and XML-RPC/JSON-RPC reachability so payments data feeds downstream reporting and automation.
Sells across several Odoo websites or companies and needs Datatrans configured per site with the correct method mix, environment separation and SCA enforcement on each.
Buy the license on ecosire.com and download the Datatrans Payment Gateway for Odoo (Switzerland) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Datatrans Payment Gateway for Odoo (Switzerland), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Datatrans method coverage | TWINT, cards, PostFinance, Apple Pay via Datatrans routing | Whatever you scope and build yourself | Often cards-only or limited method set | |
| 3DS2 / SCA compliance | Enforced on all card flows, tested in UAT | Depends on your team's expertise | Usually supported but rarely verified for you | |
| Webhook reconciliation | Signed callbacks drive order + `account.move` posting | You build and secure the controller | Varies; signature checks often weak or absent | |
| Odoo version fit | Built for your exact 17/18/19 + edition | Matches whatever you target | Generic build; may lag your version | |
| Refunds from backend | Full and partial against original transaction | Extra work to implement correctly | Sometimes; often full-only | |
| Support & ownership | Support window + Git repo handover | You own all maintenance | Vendor support, no source ownership | |
| Time to live | 2-4 weeks from confirmed scope | Months of in-house dev + testing | Fast install, slow to fit your flow |
This is build-to-order. After a short scoping call to confirm your Odoo version, Datatrans method mix and acquirer setup, typical delivery is 2-4 weeks from confirmed scope. Simpler single-website builds can land faster; complex multi-site or custom-method routing may extend it. We give you a firm timeline once scope is signed off.
No. ECOSIRE builds this module specifically for your Odoo version and Datatrans configuration, then installs and supports it. There is no instant download — the value is a tested, reconciled integration tailored to your acquirer and checkout, not a generic zip.
Odoo 17.0, 18.0 and 19.0, on both Community and Enterprise. We confirm your exact version and edition during scoping and build against it, since the `payment` framework differs across versions.
Yes. TWINT, PostFinance, cards and Apple Pay are surfaced through Datatrans' method routing, and all card flows run 3-D Secure 2 / SCA. We support both Datatrans Secure Fields (on-page, tokenised) and Redirect/Lightbox hosted modes depending on your PCI preference.
A server-to-server webhook controller verifies each Datatrans callback by HMAC signature, then moves the `payment.transaction` through the standard states, confirms the linked `sale.order` and lets Odoo post the `account.move`. That gives you automatic reconciliation rather than manual matching, plus a full audit trail.
Every engagement includes a defined post-go-live support window for fixes and adjustments. Beyond that, we offer ongoing support and version-upgrade work (for example migrating the module when you move to a newer Odoo release) as a separate arrangement. You also receive the Git repository so your own team can maintain it.
Yes. We run UAT on a staging database against the Datatrans sandbox using separate sandbox credentials, so you validate TWINT, cards, Apple Pay, 3DS2, refunds and webhook reconciliation before touching production. A rollback plan is part of the handover.
A build-to-order Datatrans payment provider for Odoo that brings Swiss checkout methods — TWINT, cards, PostFinance, Apple Pay — into your Website, eCommerce and Sales flows. ECOSIRE builds, installs and supports it; it is not an off-the-shelf apps.odoo.com download.