Skip to Content

Turkey Payments: PayTR, iyzico & Param

by
Odoo

$ 79.05

v 18.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Lines of code 1107
Technical Name tr_payment_paytr_iyzico_param
LicenseOPL-1
Websitehttps://gencbaris.com/odoo_plugins/
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Discuss (mail)
Lines of code 1107
Technical Name tr_payment_paytr_iyzico_param
LicenseOPL-1
Websitehttps://gencbaris.com/odoo_plugins/
Versions 18.0 19.0
Turkey Payments for Odoo — PayTR, iyzico & Param

Turkey Payments: PayTR, iyzico & Param

The Odoo Turkey payment gateway bundle — accept card payments natively in the Odoo Payment framework

Take online card payments through Turkey's three leading payment gateways — PayTR, iyzico and Param — directly inside Odoo. This is a real payment.provider / payment.transaction integration, not a bolt-on redirect form: every provider returns and webhook is cryptographically verified before an order is ever marked paid. Bring your own merchant keys (BYOK), flip a provider to Test or Enabled, and it shows up at checkout.

Who it's for & the problem it solves

Turkish merchants and Türkiye-facing webshops on Odoo need local payment gateways that customers actually trust — with Turkish-lira pricing, 3-D Secure and installments. Odoo ships no native PayTR, iyzico or Param provider, so most stores fall back to a third-party SaaS bridge or a fragile copy-paste payment form. This module closes that gap: one Odoo app that wires all three gateways straight into the standard Payment Providers screen, signing and verifying every transaction the way each gateway's own documentation requires.

PayTR Odoo

PayTR iFrame API. The get-token request is signed with an HMAC-SHA256 token over the exact published field order, and the server-to-server callback hash is re-computed and constant-time compared before the order is paid. Seamless embedded checkout; TRY and major currencies.

iyzico Odoo

iyzico Checkout Form over REST with IYZWSv2 (HmacSHA256) authorization and 3-D Secure. The result is never trusted from the redirect alone — it is confirmed by a signed server-side Retrieve call, and the paid amount is matched back to the order.

Param Odoo

Param (TurkPos) TP_WMD_UCD / TP_WMD_Pay 3-D Secure flow with the SHA2B64 transaction hash. The bank ACS challenge HTML is rendered to the shopper, and the payment is completed server-side after the ACS return.

Key features

  • Three Turkish gateways in one module — PayTR, iyzico and Param, all as first-class Odoo payment providers.
  • Signature / hash verification on every callback — PayTR HMAC-SHA256 callback hash, iyzico signed Retrieve, Param Sonuc check. No payment status is ever trusted unsigned.
  • 3-D Secure on iyzico (Checkout Form) and Param (TP_WMD ACS challenge).
  • iFrame / redirect checkout — embedded PayTR iframe, hosted iyzico payment page, Param bank ACS challenge.
  • Replay & amount checks — the paid amount and currency are re-matched to the Odoo transaction before it is marked done; mismatches are rejected.
  • BYOK merchant credentials — your own keys (PayTR Merchant ID/Key/Salt, iyzico API/Secret, Param Client Code/Username/Password/GUID), stored on the provider record and restricted to system administrators.
  • Sandbox / test mode — set any provider to the Test state to hit that gateway's sandbox endpoints; no code change to go live.
  • Native Payment framework — extends payment.provider and payment.transaction, so it works with eCommerce, invoices and the customer portal out of the box.

How it works

  1. Install the module.
  2. Open Invoicing › Configuration › Payment Providers.
  3. Pick PayTR, iyzico or Param.
  4. Enter your own (BYOK) merchant credentials on the provider record.
  5. Switch the provider to Test (sandbox) or Enabled (production).
  6. The provider then appears at checkout — eCommerce, invoices and the portal.

Param note: PayTR and iyzico request signing are verified against the providers' published examples. For Param (TurkPos), confirm the SHA2B64 hash against your live Param panel before switching to production.

Why this module

It is the only listing that bundles all three of Turkey's leading gateways — PayTR, iyzico and Param — into a single, signature-verified Odoo payment app. iyzico and PayTR sometimes appear as standalone connectors, but Param has no standalone competitor on the App Store; here you get it alongside the other two. No third-party SaaS bridge, no monthly middleware fee: your keys talk straight to the gateway, and the crypto for each provider is implemented exactly as that gateway documents it.

Screenshots

Turkey Payments — Payment Providers list in Odoo

PayTR, iyzico and Param appear as native Odoo payment providers alongside the standard gateways.

Turkey Payments — PayTR provider credentials form in Odoo

PayTR provider: enter your BYOK Merchant ID, Merchant Key and Merchant Salt, then switch to Test or Enabled.

Turkey Payments — iyzico provider credentials form in Odoo

iyzico provider: your API Key and Secret Key drive the IYZWSv2-signed Checkout Form with 3-D Secure.

Turkey Payments — Param provider credentials form in Odoo

Param (TurkPos) provider: Client Code, Username, Password and GUID power the TP_WMD 3-D Secure flow.

Technical

  • Compatible: Odoo 18 & 19
  • License: OPL-1
  • Credentials: BYOK (your own merchant keys)
  • Depends: payment, account
  • Providers: PayTR (iFrame), iyzico (Checkout Form / 3DS), Param (TP_WMD 3DS)
  • Support: odoo@gencbaris.com

Odoo 18 & 19 · OPL-1 · BYOK

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.