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.

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 one working week 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.