XML Suscriptions Ready?

  • Resolved Hughsp

    (@rescaes)


    3 years, 4 months ago

    Hi there,

    I’m not sure but I think the plugin is not ready to deal with suscriptions:

    I’m using WC Subscriptions and let my customers buy recurrent products by SEPA direct debit. That way, they give their bank info and sign a single mandate (where it says it is a recurrent payment) only ONCE with this awesome plugin.

    The problem is that when the renovation arrives, a new order is created (for the new period). Then, when I export the xml file for all the “unpayed orders”, I get the xml, but the mandate number included in the xml is not correct… it provides the {id} of the newly created order instead of the original order’s (parent order) {id}.

    That makes me have to go one by one through all the xml files and change the mandate number.

    Truth is there is this option in Germanized Sepa payment options:

    “Mandate ID Format”

    “You may extend the Mandate ID format by adding a prefix and/or suffix. Use {id} as placeholder to insert the automatically generated ID.”

    I’m not sure if that options gives place to adjust it so it takes the numbering for the mandate differently, in which case that would be a solution.

    Any help will be much appreciated!

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author vendidero

    (@vendidero)

    Hi there,

    no, the direct debit gateway is not ready for subscriptions. Handling recurring subscriptions is a tough thing (you’ll need to regularly notify your customers based on the interval). We do only support one-time debits. To handle subscriptions you should use a payment service provider like Stripe or Mollie to handle your (recurring) SEPA payments.

    Cheers

    Thread Starter Hughsp

    (@rescaes)

    Hi again,

    Thanks for your detailed explanation. I’ve used Stripe too. In this case I work directly with customers, so they are perfectly aware of the recurring payments and don’t really need to sign a new mandate every time (recurrency is already specified in the mandate). The recurring subscriptions, notifications, etc. are already handled by the WC Subscriptions plugin (perfectly compatible with Germanized so far)… So I basically “manually” check for the pending suscriptions and use your xml exporting tools to create the direct debit…. it’s awesomely perfect!… But this final step is the only one missing according to my initial post.

    I already found a solutions with another plugin to easily correct the xml info, but still… another step in the process.

    I think it would be a good improvement for Germanized: recurring manual payments (basically correct xml export, the rest is there already!) for those cases where everything is already settled and probably where the relationship with the customer is very personal (freelancers, SMEs…). Specially considering the additional cost for intermediaries like Stripe or Mollie.

    Thanks again anyway for such an incredibly well done plugin!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘XML Suscriptions Ready?’ is closed to new replies.