Command Palette

Search for a command to run...

Getting Started with T-Kassa Payment for Medusa (legacy v1)

In this document, you’ll learn how to install and configure the T-Kassa payment provider by T-Bank for Medusa.

Warning: 

This guide covers configuring the legacy 1.x version, where you set the plugin options in . The current version 2 keeps these settings in the Integration Module, so a store admin edits them in Admin without changing configuration files or redeploying. For a new installation, follow Getting Started with T-Kassa Payment for Medusa.

Requirements

  • Medusa v2.14.0 or later
  • Node.js v20 or later
  • A T-Business account with T-Kassa internet acquiring – sign in or create one

Installation

yarn add @gorgo/medusa-payment-tkassa@1

Configuration

Add the provider configuration in your file of the Medusa admin application:

medusa-config.js
1# ...
2module.exports = defineConfig({
3 # ...
4 modules: [
5 {
6 resolve: "@medusajs/medusa/payment",
7 options: {
8 providers: [
9 {
10 resolve: "@gorgo/medusa-payment-tkassa/providers/payment-tkassa",
11 id: "tkassa",
12 options: {
13 terminalKey: process.env.TKASSA_TERMINAL_KEY,
14 password: process.env.TKASSA_PASSWORD,
15 capture: true,
16 useReceipt: true,
17 ffdVersion: "1.05",
18 taxation: "osn",
19 taxItemDefault: "none",
20 taxShippingDefault: "none"
21 },
22 }
23 ]
24 }
25 }
26 ]
27})

Add environment variables with your shop identifier and secret from your T-Business account:

.env
1TKASSA_TERMINAL_KEY=123456789
2TKASSA_PASSWORD=supersecret

Provider Options

Loading...

Webhook Setup

To properly handle payment notifications from T-Kassa, configure webhooks in your T-Business account as following:

  1. Navigate to → Choose your shop → → Choose or Terminal → Click to open the setting window

  2. Choose to send Notifications

  3. Add a URL like:

    Change with your medusa store domain.

Warning: T-Kassa expects an response message to confirm successful webhook processing and to prevent duplicate notifications. Currently, Medusa does not natively support custom webhook response messages, but webhooks are still processed correctly without this. For more details, check out the related discussion.
Edited Sep 23, 2026·Edit this page