| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Sales (sale_management) • Invoicing (account) • Website (website) |
| Lines of code | 5036 |
| Technical Name |
payment_powertranz |
| License | OPL-1 |
| Website | https://www.vedtechsolutions.com |
Connect your Odoo 19 store to the PowerTranz payment gateway and accept credit and debit card payments securely. Cards are collected by the merchant's inline form and forwarded server-to-server to PowerTranz over TLS within a single request â they are never persisted by Odoo. 3-D Secure challenges run inside a PowerTranz-hosted iframe, and saved-card tokens enable fast repeat checkout and recurring billing.
Key Features
- Secure server-to-server card processing (FPI)
- 3-D Secure authentication (hosted iframe)
- Tokenization â save cards for faster checkout
- eCommerce & customer-portal checkout
- Recurring payments (merchant & PowerTranz managed)
- Refunds â full & partial, credit-note aware
- Test mode for safe configuration
- Detailed transaction logging
Checkout Experience
Customers enter their card details in a clean inline form on the storefront and can opt in to recurring billing â no redirect to an external page.
Security & Compliance
Card data is forwarded directly to PowerTranz over TLS and is never stored in your Odoo database. 3-D Secure challenges are handled in a PowerTranz-hosted iframe via the standard merchant-response callback. The module ships with a PCI compliance report describing the SAQ D scope of the integration, and webhook callbacks are authenticated with HMAC signatures to reject tampered or replayed notifications.
Recurring & Tokenized Payments
Let customers save a card and re-use it for subsequent purchases. Subscription-style recurring billing is supported in both merchant-managed mode (Odoo schedules and charges saved tokens via a cron, with retry handling) and PowerTranz-managed mode.
Easy Configuration
Add the provider under Accounting → Configuration → Payment Providers (or Website settings). Enter your PowerTranz credentials (Merchant ID, Password, Gateway Key), enable 3-D Secure and recurring payments, customise the customer-facing status messages, and set the mode to Test while verifying, then Enabled to go live. Full setup steps are covered in the included Admin and User guides.
Support
Maintained by VedTech Solutions. For configuration help or issues, contact us through our Odoo Apps publisher page.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Sales (sale_management) • Invoicing (account) • Website (website) |
| Lines of code | 5036 |
| Technical Name |
payment_powertranz |
| License | OPL-1 |
| Website | https://www.vedtechsolutions.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module