- 首页
- Apps
- SaaS Tools
- 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.
什么是 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.
核心功能
按需定制,全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线,并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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.
你得到什么
- 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
这是给谁的
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.
Wallee Payment Provider for Odoo 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Wallee space integration | Native provider built for your Space ID and API | Possible but built from scratch by your team | Generic connector, may not fit your space | No Wallee support at all |
| TWINT / PostFinance at checkout | Surfaced natively via your connected methods | Depends on your developers' effort | Varies; often card-only | Not available |
| Hosted + inline checkout | Both, configurable per store | Whatever you scope and maintain | Usually one mode only | Redirect-only generic flow |
| Refunds & manual capture | Full/partial refunds + authorize-then-capture from Odoo | Must be designed and tested in-house | Often refund-only, no capture control | Manual, outside Odoo |
| Missed-webhook recovery | Fallback status-sync `ir.cron` plus full logging | Only if you build it | Rarely included | None |
| Source ownership | Full source + git repo handover | You own it but bear all cost | Often licensed/closed | N/A |
| Delivery model | Build-to-order, one working week, staging UAT + rollback | Open-ended internal timeline | Instant download, integration on you | Included but incomplete |
| Support & Odoo 17/18/19 | Post-go-live window + version-targeted build | Self-supported | Vendor forum / paid tiers | Core support only |
关于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`.
相关模块
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



