tpay-com / tpay-woocommerce Goto Github PK

PHP 64.33% JavaScript 1.39% TypeScript 29.07% SCSS 4.65% Hack 0.57%

tpay-woocommerce's Introduction

Tpay.com Payment Gateway for WooCommerce

Contributors: tpay.com
Tags: tpay, tpay.com, payment, payment gateway, woocommerce
Tested up to: 6.2.2
Stable tag: 1.4
Requires PHP: 7.1 or higher
License: GPLv3
Tpay is payment gateway for WooCommerce.

Description

Tpay is payment gateway for WooCommerce. Accept online payments in a safe and fast way.

Requirements:

WordPress with a minimum PHP 7.1 version
Installed WooCommerce plugin version above 6.x.x
Shop with the Polish Zloty (PLN) currency set
Active account at Tpay
Open API account access enabled

The main advantages of the Tpay plugin:

Clear presentation of payment methods (on-site mode, BLIK LVL 0).
Various payment methods (Cards payment, electronic wallets, installments, etc.)
Management of returns from the WooCommerce panel.
Payment method limitation for delivery.
The ability to customize the order of bank logos.
Subscription card payments (additional extension required, e.g. WooCommerce Subscriptions).

The plugin offers the following payment methods:

Tpay banks list – payment shows a list of banks, depending on the selected type, the payer will be redirected to the bank.
Tpay BLIK – payer will be redirected to eBlik page or be able to type BLIK's code in the cart.
Tpay Credit Card Standard - a secure form for card data on Tpay panel.
Tpay Credit Card SF - a secure form for card data in the cart.
Tpay Google Pay - payer will be redirected to Google Pay payment.
Tpay Twisto – payer will be redirected to Twisto payment form.
Tpay Installments – payer will be redirected to installment payment form. Detailed information how to configure plugin you will find here.

Installation

Log in to your WordPress admin panel.
Go to WooCommerce and then click the Tpay settings tab. (using global settings means you don't have to re-enter the same configuration details for each payment method)
Select the environment you want to use.
Fill in the fields with data from the Merchant Account *.
Go to WooCommerce, select Settings, then click on the Payments tab.
Enable the payments you want to be visible on your website.

Production environment use data from the Merchant Panel. Use your Sandbox account details for Sandbox integration. If you have any questions, please contact our technical support.

Frequently Asked Questions

What do I need to use the plugin:

You need to have WooCommerce installed and activated on your WordPress site.
You need to open a Merchant account on Tpay.com

How can I accept subscription payments

You need to have WooCommerce installed and activated on your WordPress site.
You need a plugin which extends WooCommerce with this functionality. (Tested on the WooCommerce Subscriptions).
You need to open a Merchant account on Tpay.com

Where can I find configuration data?

Go to Merchant Panel -> Integration -> API -> Open API section.

How to enable BLIK in LVL 0 mode?

Go to the Tpay BLIK payment settings and select the "Enable Blik 0" option.

How to enable Card in on-site mode?

Go to the Tpay Credit Card SF payment settings and enter the RSA key in the "RSA Key" field.

Where can I find the RSA key?

Go to Merchant Panel -> Credit Card payment -> API. If you do not have such tab in your Merchant Panel, please contact us.

Screenshots

List of banks
Blik LVL 0
Card payment on-site
Global configuration
Payments configuration

Changelog

tpay-woocommerce's People

Contributors

Watchers

Forkers

s4ddly

tpay-woocommerce's Issues

Logged errors when using Blik

Hi,
I noticed that there were errors in the logs related to Blik payment directly on the checkout.
PHP Version: 8.0
Woo: 8.6.1
WP: 6.4.3
TPay payments: 1.4.2

Tpay Panel:
In the list of notifications in the tpay panel in the column "Opis błędu" it shows:
Notice: Funkcja is_internal_meta_key została wywołana nieprawidłowo. Do wewnętrzn

Error Log:
[26-Mar-2024 11:04:00 UTC] ID was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, Tpay\TpayBlik->process_payment, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[26-Mar-2024 11:05:44 UTC] ID was called incorrectly. Order properties should not be accessed directly. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, Tpay\TpayBlik->process_payment, Tpay\TpayGateways->set_payment_data, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[26-Mar-2024 11:05:46 UTC] is_internal_meta_key was called incorrectly. Do wewnętrznych metod meta nie należy używać ogólnych metod dodawania/aktualizacji/pobierania metadanych, w tym "_payment_method". Użyj getterów i setterów. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, Tpay\TpayBlik->process_payment, Tpay\TpayBlik->process_transaction, WC_Data->update_meta_data, WC_Data->is_internal_meta_key, wc_doing_it_wrong. This message was added in version 3.2.0.

[26-Mar-2024 11:06:02 UTC] is_internal_meta_key was called incorrectly. Do wewnętrznych metod meta nie należy używać ogólnych metod dodawania/aktualizacji/pobierania metadanych, w tym "_transaction_id". Użyj getterów i setterów. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, Tpay\TpayBlik->process_payment, WC_Data->update_meta_data, WC_Data->is_internal_meta_key, wc_doing_it_wrong. This message was added in version 3.2.0.

[26-Mar-2024 11:06:02 UTC] is_internal_meta_key was called incorrectly. Do wewnętrznych metod meta nie należy używać ogólnych metod dodawania/aktualizacji/pobierania metadanych, w tym "_payment_method". Użyj getterów i setterów. Backtrace: require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_action('template_redirect'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::do_wc_ajax, do_action('wc_ajax_checkout'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, Tpay\TpayBlik->process_payment, WC_Data->update_meta_data, WC_Data->is_internal_meta_key, wc_doing_it_wrong. This message was added in version 3.2.0.

Block checkout compatibility

Hello, is your plugin compatible with the newest WooCommerce using checkout blocks as a default checkout?

Custom paid statuses

Hello,

We started using the Woo Open API plugin and encountered few problems.
I would like to propose two changes that will make the plugin more elastic:

On the store we use non-standard statuses. After payment, the order waits for approval, only to be processed. In your plugin, there are hard coded two statuses 'completed' and 'processing' which makes it impossible to work with additional statuses. I suggest in the TPaySettings.php file in line 319 instead of wc_get_order_statuses() use wc_get_is_paid_statuses() and remove the check condition in line 323. This will allow developers to use additional statuses, which they marks as paid.
In the lpn/UpdateOrderStatus.php file, we again have hard-coded options, and you could take the value from the "get_option( 'tpay_settings_option_name')['global_default_on_hold_status']" field that the user selects in the panel.

Funkcja get_cart została wywołana nieprawidłowo

ver 1.6.4
PHP 8.1, WP 6.6.1, WC 8.9.3

PHP Notice: Funkcja get_cart została wywołana nieprawidłowo. Funkcja "Get cart" nie powinna być wywołana przed akcją wp_loaded. Backtrace: require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('init'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\BlockTypesController->register_blocks, Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->__construct, Automattic\WooCommerce\Blocks\BlockTypes\Cart->initialize, Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->initialize, Automattic\WooCommerce\Blocks\BlockTypes\Cart->register_block_type_assets, Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->register_block_type_assets, Automattic\WooCommerce\Blocks\Assets\Api->register_script, apply_filters('woocommerce_blocks_register_script_dependencies'), WP_Hook->apply_filters, Automattic\WooCommerce\Blocks\Payments\Api->add_payment_method_script_dependencies, Automattic\WooCommerce\Blocks\Payments\PaymentMethodRegistry->get_all_active_payment_method_script_dependencies, Automattic\WooCommerce\Blocks\Payments\PaymentMethodRegistry->get_all_active_registered, array_filter, Automattic\WooCommerce\Blocks\Payments\PaymentMethodRegistry->Automattic\WooCommerce\Blocks\Payments{closure}, Tpay\Blocks\TpayBlock->is_active, Tpay\TpayGateways->is_available, WC_Cart->get_cart, wc_doing_it_wrong Dowiedz się więcej: Debugowanie w WordPressie. (Ten komunikat został dodany w wersji 2.3.) in /home/public_html/wp-includes/functions.php on line 6085

plugin not available at wordpress.org

even though you decribe it here
https://support.tpay.com/sprzedawca/stworz-sklep-wordpressie-z-bramka-platnosci-tpay-com

the plugin is not available in wordpress repository
https://pl.wordpress.org/plugins/search/tpay/

Warning after installation

Hi, I have warning after fresh install on PHP 8.1 and latest version of Wordpress and Woocomerce.

Warning: Trying to access array offset on value of type bool in "\plugins\tpay-woocommerce\tpay.php on line 67"