Skip to main content
Wallee Payment Provider for Odoo — A made-to-order Odoo payment provider that connects your Wallee space to native checkout,  — 1/1Illustrative preview

A made-to-order Odoo payment provider that connects your Wallee space to native checkout,

with hosted or inline card entry, TWINT and PostFinance support, tokenization, refunds and automatic reconciliation.

ECOSIRE builds, installs and supports it after a scoping call.

What is Wallee Payment Provider for Odoo?

A made-to-order Odoo payment provider that connects your Wallee space to native checkout, with hosted or inline card entry, TWINT and PostFinance support, tokenization, refunds and automatic reconciliation. ECOSIRE builds, installs and supports it after a scoping call. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.

Key Features

Dedicated `payment.provider` subtype storing Wallee Space ID, application user ID and secret key in separate test and live credential sets
Hosted checkout via the Wallee Transaction Payment Page API with redirect and return-URL handling mapped to `payment.transaction` states
Optional inline/iframe payment page for on-site card entry without leaving the storefront
Webhook listener for authorized, fulfill, voided and declined events with signature/payload verification before any state change
Tokenization and saved payment methods so returning `website_sale` customers can one-click reorder
Full and partial refunds triggered directly from the Odoo invoice or sale order, posted back to the Wallee transaction
Manual capture (authorize-then-capture) with void support for authorize-on-order, charge-on-ship flows
Automatic reconciliation creating `account.payment` and registering payment against the invoice on fulfillment
Support for Wallee-connected methods including TWINT, PostFinance and the major card schemes surfaced at checkout
Multi-currency and multi-space configuration, with per-company scoping via record rules
Fallback status-sync `ir.cron` that polls transaction state to recover any missed webhook
Full request/response transaction logging with correlation IDs for audit, dispute and support workflows
Configurable capture, refund and error-handling behavior exposed on the provider form (no code edits to change policy)
Odoo 17.0 / 18.0 / 19.0 support on Community and Enterprise, packaged as a clean installable module

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

  1. 1

    You order

    Start with a one-time build price. We scope it with you at kickoff.

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your Odoo.

  3. 3

    Go live + support

    You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.

Technical Specifications

Odoo Compatibility
Odoo 17, Odoo 18, Odoo 19
Editions
Enterprise & Community
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
PostgreSQL 12+

About this Product

Swiss and DACH merchants running a whitelabel Wallee space usually end up bridging Odoo to their gateway by hand: exporting orders, reconciling settlements in a spreadsheet, and manually marking invoices paid. Odoo's payment framework ships generic providers, but nothing that speaks to your Wallee Space over its Transaction and Payment Page APIs, and nothing that natively surfaces the Swiss methods your customers expect at checkout — TWINT and PostFinance alongside the major card schemes. The result is a checkout that either sends buyers off-platform or leaves finance chasing statuses after the fact. That is where Odoo native runs out of road, and where we build a purpose-fit provider.

We build a dedicated payment.provider record type for your Wallee integration. It stores your Space ID, application user ID and secret key in separate test and live sets, so you can validate on sandbox before going live without touching production credentials. On top of that we implement a hosted checkout that redirects the buyer to a Wallee Transaction Payment Page, plus an optional inline/iframe payment page for on-site card entry when you want customers to stay on your storefront. Every transaction the provider creates is mirrored to a payment.transaction in Odoo, so sale, account_payment and website_sale all see a consistent state.

Technically, the module is a clean __manifest__.py depending on payment, account_payment, sale and website_sale, with models/ extending payment.provider and payment.transaction (models.Model, typed fields, @api.depends computes for derived state), access controlled by ir.model.access.csv and record rules so credentials and logs stay scoped to the right company. A webhook listener consumes Wallee transaction state changes — authorized, fulfill, voided, declined — and verifies each payload before acting on it, never trusting an unauthenticated callback. We wire tokenization and saved payment methods for returning customers, full and partial refunds triggered from the Odoo invoice or sale order, and manual capture (authorize-then-capture) with void support for merchants who ship before charging. A scheduled action (ir.cron) polls transaction status as a fallback so a missed webhook can never strand an order, and every request/response is written to a transaction log for audit and dispute handling. The build supports multi-currency and multi-space configuration and targets Odoo 17.0, 18.0 and 19.0, Community or Enterprise.

Because this is build-to-order, delivery follows a defined path: a scoping call to confirm your Wallee methods, capture mode and reconciliation rules; a fixed quote; then development on a staging clone, UAT against your sandbox space, and a supervised go-live with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source, so nothing is a black box you cannot maintain.

Pricing starts from $999 (indicative, single-company base scope); additional Wallee spaces, multi-company deployment, extra connected payment methods, and deeper reconciliation or localization requirements increase the quoted scope.

What you get

  • Installable source code for your version of the Wallee payment provider module (Odoo 17.0/18.0/19.0)
  • Installation and configuration on your staging and production environments, including credential and webhook setup
  • Technical documentation: model reference, webhook contract, cron behavior and configuration guide
  • End-user guide plus a live training session for finance and store-admin staff
  • UAT on a staging clone against your Wallee sandbox space, with a documented rollback plan
  • Post-go-live support window for defect fixes and configuration assistance
  • Git repository handover with full commit history and tagged release
  • Test-vs-live credential switchover checklist and go-live runbook

Who this is for

Swiss/DACH online merchant

Runs a Wallee whitelabel space and wants TWINT, PostFinance and cards live inside native Odoo `website_sale` checkout instead of redirecting buyers to a manual bridge.

Finance / accounting lead

Needs every payment to reconcile automatically to `account.payment` and register against the invoice, with full and partial refunds handled from Odoo and a clean audit log for disputes.

Operations manager using authorize-then-capture

Ships before charging and needs manual capture with void support, plus a status-sync cron so no order is stranded by a missed webhook.

Odoo partner or in-house IT lead

Wants source-code ownership, a documented webhook and cron contract, and multi-company/multi-space scoping via record rules so the integration is maintainable across brands.

How Wallee Payment Provider for Odoo Compares

CriterionECOSIRECustom BuildCompetitorOdoo Native
Wallee space integrationNative provider built for your Space ID and APIPossible but built from scratch by your teamGeneric connector, may not fit your spaceNo Wallee support at all
TWINT / PostFinance at checkoutSurfaced natively via your connected methodsDepends on your developers' effortVaries; often card-onlyNot available
Hosted + inline checkoutBoth, configurable per storeWhatever you scope and maintainUsually one mode onlyRedirect-only generic flow
Refunds & manual captureFull/partial refunds + authorize-then-capture from OdooMust be designed and tested in-houseOften refund-only, no capture controlManual, outside Odoo
Missed-webhook recoveryFallback status-sync `ir.cron` plus full loggingOnly if you build itRarely includedNone
Source ownershipFull source + git repo handoverYou own it but bear all costOften licensed/closedN/A
Delivery modelBuild-to-order, one working week, staging UAT + rollbackOpen-ended internal timelineInstant download, integration on youIncluded but incomplete
Support & Odoo 17/18/19Post-go-live window + version-targeted buildSelf-supportedVendor forum / paid tiersCore support only

Frequently Asked Questions about Wallee Payment Provider

Is this an existing app I can download and install today?

No. This is a build-to-order module that ECOSIRE develops for your specific Wallee space and Odoo version. After a scoping call we produce a fixed quote, build on a staging clone, run UAT against your sandbox, and hand over installable source. It is not an off-the-shelf apps.odoo.com download.

How long does delivery take?

Typical delivery is one working week from confirmed scope. The exact timeline is set in your fixed quote and depends on the number of Wallee spaces, payment methods, capture mode and reconciliation rules involved. Straightforward single-space builds land at the shorter end.

Which payment methods and Odoo versions are supported?

Any method connected in your Wallee space can be surfaced at checkout, including TWINT, PostFinance and the major card schemes. We target Odoo 17.0, 18.0 and 19.0 on both Community and Enterprise, and confirm your exact edition during scoping.

How does pricing and scoping work?

Pricing starts from an indicative $999 for a single-company base scope. After a short scoping call we issue a fixed, firm quote. Drivers such as additional Wallee spaces, multi-company deployment, extra connected methods and deeper reconciliation or localization needs adjust the final figure.

What happens if a Wallee webhook is missed?

The module includes a fallback status-sync `ir.cron` that polls transaction state on a schedule, so a dropped or delayed webhook is reconciled automatically. Every request and response is also logged, so finance can always trace a transaction's full history.

Do we own the code, and how are support and updates handled?

Yes. You receive full source and a git repository handover, so nothing is locked. Every engagement includes a post-go-live support window for defect fixes and configuration help; ongoing maintenance and version upgrades (for example to a future Odoo release) can be arranged as a separate support agreement.

Can you support manual capture and partial refunds?

Yes. We build authorize-then-capture with void support for ship-before-charge flows, and both full and partial refunds are triggered directly from the Odoo invoice or sale order and posted back to the Wallee transaction, with the result reconciled to `account.payment`.

Request a quote

Wallee Payment Provider

A made-to-order Odoo payment provider that connects your Wallee space to native checkout, with hosted or inline card entry, TWINT and PostFinance support, tokenization, refunds and automatic reconciliation. ECOSIRE builds, installs and supports it after a scoping call.

  • Dedicated `payment.provider` subtype storing Wallee Space ID, application user ID and secret key in separate test and live credential sets
  • Hosted checkout via the Wallee Transaction Payment Page API with redirect and return-URL handling mapped to `payment.transaction` states
  • Optional inline/iframe payment page for on-site card entry without leaving the storefront
  • Webhook listener for authorized, fulfill, voided and declined events with signature/payload verification before any state change

Request a Quotation

Tell us about your Wallee Payment Provider requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.