I developed this feature to hide some gateways conditionally if the shipping country chosen by the user is “IT”.
The Satispay Gateway is not removed, yet the gateway name is correct.

Suggestions? I read that other users have similar problems.

function blocca_metodi_pagamento_checkout($available_gateways) {
	if (is_checkout()) {
	    $country = WC()->customer->get_shipping_country();

	    if ($country !== 'IT') {
	        $metodi_da_bloccare = array('satispay', 'paypal', 'bacs', 'stripe');

	        foreach ($metodi_da_bloccare as $metodo) {
	            if (isset($available_gateways[$metodo])) {
	                unset($available_gateways[$metodo]);
	            }
	        }

	    } else {
	        if (isset($available_gateways['cheque'])) {
	            unset($available_gateways['cheque']);
	        }
	    }
	}
	return $available_gateways;
}
add_filter('woocommerce_available_payment_gateways', 'blocca_metodi_pagamento_checkout');

Se annullo il pagamento con Satispay (click sulla X in alto a destra dalla pagina https://online.satispay.com/pay/…… ), il browser ritorna alla pagina di Checkout, ma con il carrello svuotato.

Woocommerce 9.3.3 – WP 6.6.2 – Satispay 2.2.6

Su un sito di un cliente è stato effettuato un rimborso di un ordine ma viene visualizzato questo errore
Errore durante la transizione di stato. {
“error”: {
“errors”: [
{
“domain”: “global”,
“reason”: “notFound”,
“message”: “Not Found”
}
],
“code”: 404,
“message”: “Not Found”
}
}
L’ordine risulta rimborsato su woocommerce ma l’acquirente ha confermato che non c’è stato rimborso. A cosa si riferisce l’error 404?

Grazie

My custom theme has a filter to deactivate all payment gateways except Bank Transfer (BACS) on a specific condition, it works perfectly with all available methods (we have Stripe, PayPal and several others) but not with Satispay. Consider the following code:

add_filter('woocommerce_available_payment_gateways','umm_filter_gateways',1);
function umm_filter_gateways($gateways){
    if ( ! is_admin() ) {//front-end only
        $session = WC()->session;
        if ($session){//null check
            if ( $session->get( 'my_custom_condition_trigger' ) ){
                foreach ($gateways as $key => $value) {
                    if ($key != "bacs"){//if not BACS
                        unset($gateways[$key]);//remove gateway from array
                    }
                }
            }
        }
    }
    return $gateways;
}

Unfortunately all other methods are successfully removed under that condition, while Satispay remains available. I’ve also tried saving a custom debug option in the DB with

update_option('MY_DEBUG_LOG', json_encode($gateways));

before returning the $gateways array at the end of the function, and the array only contains the ‘bacs’ gateway, so my function works as expected. Why does the plugin show Satispay as an available payment gateway when it shouldn’t?

hi.. there is still the issue with logo size..

Dopo aggiornamento si presenta il logo di Satispay gigante nel pagamento di elementor.

Grazie

after the update to version 2.2.3 i am experiencing problems with the wocommerce shopping cart. it is not possible to select the different payment methods.

Hi, we are experiencing this bug when my users pay with satispay.
the payment method label changes once you reach the order confirmation page.
and the same label is also incorrect in the email confirmation.
from “satispay” to “credit card”.

Hi,

I’m writing to report an issue with the new Order management behaviour with the last update to v2.2.1.

For context, before this update this is what happened to new orders:

1. Users on checkout click to submit order and they are redirected to Satispay pay page -> order is created with “Pending payment” status;
2. Users complete payment -> order goes to “Processing” status.

After last release, step 1 changed:

1. Users on checkout click to submit order and they are redirected to Satispay pay page -> order is created with “Pending payment” status but it immediately goes to “On hold” status;

Well, I think this new behaviour is very dangerous, because the “On hold” status is used in a improper way: this status should be used for deferred payment methods. For example, BACS is a payment method where users make payment, but it needs 1-2 days for the Shop Manager to receive the funds: in this case it is right to confirm the order and therefore to reserve the products reducing the stock, because the payment has been done. When funds will be received, the order will go to “Processing” status and so the shop manager will then prepare the order for the shipment.

But as you know, this is not the way Satispay works: Satispay payments are instantaneous, so there is no need to reserve stock (indeed, to do so would be dangerous, see next paragraph) or confirm order because funds are immediately received from Shop Manager that will prepare the order right after the user creates it.

Adding the “On hold” status will generate the following bug:

1. User creates order and tries to pay with Satispay;
2. For any reason, user doesn’t complete payment;
3. User comes back to checkout but sees only a notice saying the order couldn’t be canceled;
4. User goes to their Profile page -> Orders and sees the order, but cannot do anything with it (he can’t cancel it or pay for it);
5. Shop Manager has an “On hold” order, without a real reason because there is no payment to await for, and has products stock reserved for no reason (what if they were the last in stock… other users nor the same user himself wouldn’t be able to buy those… very bad).

As you can see from the last point, this update could generate also an important economic damage to the store.

Please, give a look at the definitions WooCommerce itself give for all the Order statuses: https://woo.com/document/managing-orders/

Summary:

• Pending payment?— Order received, no payment initiated. Awaiting payment (unpaid).
• On hold?— Awaiting payment – stock is reduced, but you need to confirm payment.

Hi, is it possible to pay with telephone top-ups like in this page:

https://pannello-operatori.it/payments/checkout.php?c=o8lThSQbEUFC

Thank you

Ciao,

dall’ultima versione (credo in realtà so che funziona per certo fino alla versione 2.1.6), la descrizione del metodo di pagamento e il titolo del pulsante d’acquisto, nel checkout, non sono più tradotti in Italiano, se si usa il “vecchio” checkout di WooCommerce (non a blocchi).

Risulta anche a voi?

Grazie

After the last update, I also tried deleting and redownloading the plugin. but it does not work

Warning: require_once(includes/blocks/wc-satispay-blocks.php): failed to open stream: No such file or directory in /wp-content/plugins/woo-satispay/woo-satispay.php on line 40

Fatal error: require_once(): Failed opening required ‘includes/blocks/wc-satispay-blocks.php’ (include_path=’.:/usr/local/php74/pear’) in /wp-content/plugins/woo-satispay/woo-satispay.php on line 40

Thanks

Salve,

E’ stata rilasciato un nuovo aggiornamento che risolve il problema.
Qualora non sia possibile aggiornare o usare il sito, cancellate la folder in: /wordpress-folder/wp-content/plugins/woo-satispay/ dopodiché aggiornate scaricate e installate il plugin.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Hello,

a new update has been released and it solves the crash of the latest release.
If you cannot access your website, please manually delete this folder and try to download our plugin again:
/wordpress-folder/wp-content/plugins/woo-satispay/ then download and install the newest version.

Ho disattivato il plugin WooCommerce Satispay (versione 2.2.0) perché dopo il nuovo aggiornamento la pagina va in errore critico con il plugin attivo. 


Dettagli dell'errore:

====================

Un errore di E_ERROR è stato causato nella linea 40 del file /var/www/clients/client0/web14/web/wp-content/plugins/woo-satispay/woo-satispay.php. Messaggio di errore: Uncaught Error: Failed opening required 'includes/blocks/wc-satispay-blocks.php' (include_path='.:/usr/share/php') in /var/www/clients/client0/web14/web/wp-content/plugins/woo-satispay/woo-satispay.php:40

Stack trace:

#0 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(324): woocommerce_gateway_satispay_woocommerce_block_support()

#1 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#2 /var/www/clients/client0/web14/web/wp-includes/plugin.php(517): WP_Hook->do_action()

#3 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Domain/Bootstrap.php(94): do_action()

#4 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Package.php(125): Automattic\WooCommerce\Blocks\Domain\Bootstrap->__construct()

#5 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/AbstractDependencyType.php(42): Automattic\WooCommerce\Blocks\Package::Automattic\WooCommerce\Blocks\{closure}()

#6 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/SharedType.php(28): Automattic\WooCommerce\Blocks\Registry\AbstractDependencyType->resolve_value()

#7 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Registry/Container.php(96): Automattic\WooCommerce\Blocks\Registry\SharedType->get()

#8 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Blocks/Package.php(44): Automattic\WooCommerce\Blocks\Registry\Container->get()

#9 [internal function]: Automattic\WooCommerce\Blocks\Package::init()

#10 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Packages.php(128): call_user_func()

#11 /var/www/clients/client0/web14/web/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Packages::initialize_packages()

#12 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Packages::on_init()

#13 /var/www/clients/client0/web14/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#14 /var/www/clients/client0/web14/web/wp-includes/plugin.php(517): WP_Hook->do_action()

#15 /var/www/clients/client0/web14/web/wp-settings.php(506): do_action()

#16 /var/www/clients/client0/web14/web/wp-config.php(99): require_once('...')

#17 /var/www/clients/client0/web14/web/wp-load.php(50): require_once('...')

#18 /var/www/clients/client0/web14/web/wp-login.php(12): require('...')

#19 {main}

thrown

mi è andato in errore critico tutto il sito e ho dovuto disintallare il plugin dal c-panel

Salve,
comunico che avendo appena aggiornato il vostro plugin all’ultima versione 2.2.0 in una installazione WordPress si è bloccato tutto ed è apparso questo messaggio:

Un errore di E_ERROR è stato causato nella linea 40 del file /#####/public_html/wp-content/plugins/woo-satispay/woo-satispay.php. Messaggio di errore: Uncaught Error: Failed opening required 'includes/blocks/wc-satispay-blocks.php'

Sembra che manchi tutta la cartella /include

Potreste per favore verificare?

Grazie

The plugin is not compatible with the new order storage system (HPOS).

So we can’t use the HPOS at the moment.

Any solution? Will the plugin be updated or we will have to active HPOS and disable Satispay plugin?
Thank you

Purtroppo al checkout non si vede più la modalità di Satispay con il checkout a blocchi.

HI, with WordPress 6.4.2, enabling the plugin give us this error, forcing to disable the plugin and it’s not possible to accept payment with satispay anymore

? Questo plugin è incompatibile con la funzionalità WooCommerce abilitata “High-Performance order storage”, non dovrebbe essere attivato.?Gestisci funzionalità di WooCommerce

Do you have any plan to make the plugin compatible with the wordpress functionality?

Hello, I installed Satispay plugin to handle those payments, but when I try to save settings I get this error:

Warning: Cannot modify header information – headers already sent by (output started at /home/customer/www/atmosphere.it/public_html/wp-content/plugins/woo-satispay/wc-satispay.php:188) in /home/customer/www/atmosphere.it/public_html/wp-admin/includes/misc.php on line 1431

I already tried to reinstall the plugin but no change. Can anyone please help? Thank you in advance.

I pagamenti non funzionano. Ho inserito il codice di 6 cifre nelle impostazioni e sembra tutto impostato correttamente, eppure al momento del pagamento, viene fuori questo errore: Forbidden. request ID: XXX

Avrei la necessità di avere il pacchetto di traduzione del plugin in italiano, ho visto che lo avete qui https://translate.www.ads-software.com/projects/wp-plugins/woo-satispay/language-packs/ ma non è presente sul plugin, quando lo metterete online? Grazie!

Dopo aver aggiornato il plugin alla versione 2.1.1 nella pagina del pagamento compare un logo grande quasi come tutta la pagina: https://www.dropbox.com/s/ah703qnhux2dm4n/Schermata%202022-12-18%20alle%2014.41.07.png?dl=0

Ho reinstallato la versione 2.1.0 e tutto è tornato nella norma. Spero possiate risolvere questo problema.

Grazie mille e buon lavoro a tutti

Hi,
the payments are made on my Satispay account but in the WooCommerce back-end the status of the order is “Order Cancelled”.
After I updated from version 2.0.0 to 2.1.0 it seems happens on all orders.
How can I fix this?
Thanks.

settings show link to business.satispay.com to obtain the Activation Code.

is it possible to get the code with a personal account?

and if so, how?

Hi,

when completing the order from **mobile** (e.g. Safari on iOS), you are directly switched to **Satispay App** (while on desktop you are redirected to Satispay site with QR-code and phone number input).

After paying, you are not automatically redirected on Safari.
You have to click the back link (iOS default) on top left to switch back to Safari.

Then, in Safari, **you are not redirected to Thank-you page** (Order Completed page, e.g. /checkout/order-received/{id}/?key=wc_order_{key}), but you are still in checkout with the AJAX loading spinner.

This is a problem for the user, since he doesn’t understand if the order has been successfully completed/processed or not and can’t do anything to understand (by going back he’s redirected to empty cart).

It’s like the redirect action:
[header('Location: '.$this->get_return_url($order));](https://github.com/satispay/woocommerce-plugin/blob/master/wc-satispay.php#L163)
doesn’t fire when completing purchases on mobile browser.

Could you please check?

Further details:
iOS 15.4
Safari 15.4
Satispay 3.19.0

Thanks

Hi,
I noticed that even if the payment is made on my Satispay account, in the Woocommerce back-end the status of the order is “Order Canceled”.
How can I fix this?
Thanks.

Segnalo che, nonostante il metodo di pagamento sia disabilitato nella pagina delle impostazioni di WooCommerce (WooCommerce > Impostazioni > Pagamenti), rimane sempre visibile nella pagina di pagamento dell’ordine. Lo stesso vale nel caso in cui Satispay non sia configurato correttamente (ovvero nel caso in cui non sia stato inserito il codice identificativo).

Hello, you should provide a way to change the payment method description. The italian translation of the string is not totally correct but i can’t change it in the backend. All others method give an option in the backend.
Thanks

Hello,

no matter what I do, when I try to pay, I receive error (with sandbox enabled)
34: Unauthorized, request id: CAGhT0fA

With sandbox disabled, I receive error:
0: HTTP status is not 2xx

I tried to contact custom service at [email protected] or [email protected], but all I received was an automated message requesting details for sandbox “activation??”.
When I provided with the requested detail, they sent me a sandbox activation code, which was not working.

The codes I generate on https://business.satispay.com/onlineshop are working for the activation, but not for payment.

Any help would be appreciated.