sander80
Forum Replies Created
-
Hi,
Ok, thanks for the reply and clarification. However my original question is still not answered. I am not asking about compatibility of the 2 payment methods (iDeal and Bancontact) with WooCommerce Subscriptions and Payments. I was asking when using both of your products if it works in the following way:
I am looking for a payment solution that will enable me to use Woocommerce Subscriptions with an iDeal or Bancontact initial payment and then uses this iDeal/Bancontact mandate for monthly SEPA Direct Debit payments. This is how competing solutions work. Eg Mollie (Woocommerce based) or Plug & Pay (not Woocommerce based). Stripe also has documentation on this on their website: https://stripe.com/docs/payments/ideal/save-during-payment
So to be clear this initial payment via iDeal or Bancontact to use for the subscription could be a product or the first month of the subscription itself. Or it could just be 0.01 euro to just create the mandate for SEPA Direct Debit
Could you please be so kind to clarify the exact way of working of your products and if it is the same as what i am looking for?\
Thanks!
Hi Con a11n,
Ok thanks for the reply. But now i’m totally confused.
On your own salespage: https://woocommerce.com/woocommerce-payments-ideal/ it literally says:Accept Recurring Payments
iDEAL supports recurring payments through WooCommerce Subscriptions and SEPA Direct Debit, allowing you to capture a steady revenue stream. For customers, it means value and convenience without setting reminders or forgetting to pay.Also your bancontact salespage says the same thing: https://woocommerce.com/woocommerce-payments-bancontact/
This totally conflicts with what you are saying about only creditcards being supported. Which is why a created my post in the first place. Please clarify.
Thanks!
Sander
Hi Hristo,
Thanks for the reply.
All I know that with the current http header lines put in the htaccess, browsers will cache the page locally for 6 months and will not even attempt to contact anything externally until this max-age value expires. I use chrome webdeveloper tools to inspect the headers and I can see that after webpage updates the http header values are unchanged incomparison with the first visit. And also the date-modified http header is not being set at all.
This corresponds with my tests. After making some text changes to a wordpress page that has SG browser caching enabled and opening the webpage again in the browser of a returning visitor (without refresh) does not show the updated version. Updated version is only shown to new vistors or returning visitors that manually refresh local cache. Browsers can’t be forced to update their local cache as far as I know.
Thanks for looking into this!
Hi,
Thanks for the quick reply. However i’m a bit confused by it.
I interpret it as a response to get rid of me. Not sure if you meant it that way.What do you mean with “consider it”?
I’m reporting a major problem not a feature request. If you think it’s not a problem then could you please elaborate why?
Thanks!