• Resolved dotdoc

    (@dotdoc)


    In Europe SEPA Direct Debit is the standard for recurring payments (‘incasso’).
    In the Netherlands IDEAL is standard for one time payments.
    MOLLIE uses IDEAL (not creditcard) as a first time payment for SEPA. In this way IDEAL can handle one time payments and recurrent payments.

    Cartflows doesn’t support that, IDEAL through Stripe, is also not supported, so selling courses or memberships with recurring payments (SEPA) through IDEAL, can not be done with Cartflows? Will that change in the near future?

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter dotdoc

    (@dotdoc)

    The next link maybe helpful to understand the question better. It is a similar question, although for a different funnelbuilder, but a more clear explanation:

    https://wordpress.org/support/topic/ideal-bancontact-mandate-with-sepa-direct-debit-payments-for-subscriptions/

    Is there working solution for Cartflows?

    Thread Starter dotdoc

    (@dotdoc)

    FYI: https://docs.mollie.com/payments/recurring
    Not sure if Cartflows follows these steps or will or could.

    Plugin Support mmbsf

    (@mmbsf)

    Hello @dotdoc,

    Thank you for choosing our product and getting in touch!

    You can use iDEAL with Mollie’s official plugin.

    Here’s a list of our supported payment gateways:
    https://cartflows.com/docs/supported-payment-gateways-by-cartflows/

    Hope this helps.

    Let me know if you have any further queries.

    Thread Starter dotdoc

    (@dotdoc)

    Thank you, I’ve seen the supported gateways.
    Ideal is supported.
    Sepa is not supported.

    For recurrent payment Ideal payment can be used for Sepa (as explained in the other link). Are you confirming that Cartflows supports Mollie Sepa payments through one-time payment with Ideal?

    BTW I’m struggling with Ideal also, because testpayments fail with the following: “DEBUG Creating payment object: type Order, first try failed:” “Error executing API call (422: Unprocessable Entity): The following fields of the billingAddress are missing: streetAndNumber, postalCode, city, country.” While I would think email and name should be sufficient for one time payment.

    Thread Starter dotdoc

    (@dotdoc)

    I think I found the culprit. It is Cartflows Pro.
    Unless of course, it is intended behaviour without error handling.

    With Cartflows Free: Create a CF sequence with just email/firstname fields: optin -> checkout -> Thank you. This works with Mollie.

    With Cartflows Pro: at the moment you activate the plugin it breaks the Mollie connection/fallback mechanism.
    Once address fields are added to the CF Checkout it works again, afaik.

    Can you confirm this?

    Plugin Support mmbsf

    (@mmbsf)

    Hello @dotdoc,

    Thank you for your reply.

    Yes, SEPA is not supported for upsell and downsell currently.

    But you can use CartFlows’ global checkout, checkout, pre-checkout offer, and order bump with any payment gateway that is supported by WooCommerce including SEPA.

    Regarding the error you mentioned, that’s because you’ve disabled some fields and those fields are required by your payment gateway provider.

    So as you said, it seems like you’re a CartFlows Pro user and we can not provide support for Pro users on these forums as the guidelines suggest.

    Please open a ticket in our support center:

    https://cartflows.com/support

    Best,

    Thread Starter dotdoc

    (@dotdoc)

    “Regarding the error you mentioned, that’s because you’ve disabled some fields and those fields are required by your payment gateway provider.”

    IMO, that’s seems unlikely. The payment provider has a fallback mechanism. That is why Cartflows free works as expected.

    However, if Cartflow pro is enabled the mechanism breaks; that’s a WordPress plugin conflict. I hope you’ll bring it to the attention of your developers.

    For me (Mollie users) it seems better to stick with Cartflows free for now until Cartflows pro gets fixed.

    Thanks for all of your time.

    Plugin Support Sravan

    (@bhshravankumar)

    Hello @dotdoc,

    Sure, we will inform this issue to our developers.

    Best regards,

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.