pollame78

I am using the approach present below to enable the gateway only in certain countries. However, express gateways, such as Apple Pay and Google Pay, are still shown. Can you tell me the exact names of the gateway? Thank you.

add_filter( 'woocommerce_available_payment_gateways', 'filter_payment_methods' );

function filter_payment_methods( $gateways ) {
    $eu_countries = array(
        'AT', 'BE', 'BG', 'HR', 'CY', 'CZ', 'DK', 'EE', 'FI', 'FR', 'DE', 'GR', 'HU', 'IE',
        'IT', 'LV', 'LT', 'LU', 'MT', 'NL', 'PL', 'PT', 'RO', 'SK', 'SI', 'ES', 'SE', 'GB'
    );

    if ( WC()->customer ) {
        $billing_country = WC()->customer->get_billing_country();
        if ( $billing_country && ! in_array( $billing_country, $eu_countries ) ) {
            unset( $gateways['woocommerce_payments'] );
        }
    }

    return $gateways;
}

Ok, thank you!

Hello,

Thank you for your response.

Excluding all but the single events page doesn’t resolve the issue. The structured data still shows an error because the description is too long. I would like the schema to use an excerpt of the description instead of the full content.

How can I achieve this?

Thank you.

Salve, ma non c’è stato un problema con un documento. Chiedo come si abilita. Quali sono le impostazioni da configurare per poter permettere il reverse charge.

In my Stripe account under payments, I see my test. I encounter the following message: "The PaymentIntent requires a payment method." Here's the detailed event (I replaced the codes with XXXX for privacy.):



{
"id": "pi_XXXXXXXXXXXXXXXXXXXXXXX",
"object": "payment_intent",
"last_payment_error": null,
"livemode": true,
"next_action": null,
"status": "requires_payment_method",
"amount": 51,
"amount_capturable": 0,
"amount_details": {
"tip": {
}
},
"amount_received": 0,
"application": null,
"application_fee_amount": null,
"automatic_payment_methods": null,
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"charges": {
"object": "list",
"data": [
],
"has_more": false,
"total_count": 0,
"url": "/v1/charges?payment_intent=pi_XXXXXXXXXXXXXXXX"
},
"client_secret": "pi_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"confirmation_method": "automatic",
"created": XXXXXXXXXXX,
"currency": "eur",
"customer": null,
"description": null,
"invoice": null,
"latest_charge": null,
"metadata": {
},
"on_behalf_of": null,
"payment_method": null,
"payment_method_configuration_details": null,
"payment_method_options": {
"card": {
"installments": null,
"mandate_options": null,
"network": null,
"request_three_d_secure": "automatic"
}
},
"payment_method_types": [
"card"
],
"processing": null,
"receipt_email": null,
"review": null,
"setup_future_usage": null,
"shipping": null,
"source": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"transfer_data": null,
"transfer_group": null
}

• This reply was modified 9 months, 1 week ago by pollame78.

There is personal information, and I would prefer to avoid forwarding it here in public. Could the issue be that the WordPress installation is in a subdirectory, while the domain is classic? For example: https://domain.com/folder, while https://domain.com is the site link.

• This reply was modified 9 months, 2 weeks ago by pollame78.

Hello, I also have the same issue with Apple Pay payments; I receive the error “invalid payment method.” Payments with Stripe are working fine. I contacted Stripe support, and they informed me that, after checking, Apple Pay is correctly activated on the account. All plugins are up to date.

While updating, I encountered the same issue. Could you incorporate the fix before version 7? Thank you.

I sent the request through this support page on your website. Is it possible to receive support via email without explicitly stating the website?

I deactivated all plugins except WooCommerce and ezToc, I also changed the template, but the result is always the same: error 500.
As soon as I deactivate the exToc plugin, the checkout returns to work.

Hello,
sorry for the absence. No PHP errors are thrown. No error_log file is generated in the WordPress folder. The error is a classic 500 error that occurs after some time in loading. After inserting the products in the cart if you try to go to the checkout this error occurs.

Hi Steven,
when I opened the ticket I had version 2.0.16. I have now updated to version 2.0.17, but still nothing. When I go to the Checkout page, the site loads indefinitely before generating the 500 error.
Deactivating the plugin the site returns to work normally, and the checkout page opens without problems.

Yes, it is.
Now, I had to leave <!– –> in the body field. If I try to erase everything it doesn’t.