Support » Plugin: Mollie Payments for WooCommerce » Failed SEPA direct debit: customer ID missing

  • Resolved coffeewebshop


    I’m trying to use SEPA direct debit to charge my client’s bank accounts for the recurring coffee subscriptions I’m selling. I tested it and everything worked fine, but now that I’m live some direct debit payments are failing. This shows up in the Mollie log:

    2021-03-31T02:49:53+00:00 DEBUG mollie_wc_gateway_ideal: Try to get all mandates for renewal order 16371 with customer ID
    2021-03-31T02:49:53+00:00 DEBUG mollie_wc_gateway_ideal: Failed to create payment for order 16371: [2021-03-31T02:49:53+0000] The customer () could not be used or found. [2021-03-31T02:49:53+0000] Invalid resource id.

    Clearly, the customer ID is missing. Strangely, it does work for some customers where it does state the customer ID after “order XXXX with customer ID XXXX”. So for some reason Mollie is not able to retrieve client’s customer ID’s in some cases. I can’t figure out why… can anyone help out, I really need this to work and I’m pretty desperate.

Viewing 16 replies (of 16 total)
  • Plugin Support Inpsyde Niklas


    We have just released the update 6.2.2 which resolves the issue with newly created subscriptions. This means any new subscription created with this version will work fine.
    But all subscriptions that were created while version 6.2 and 6.2.1 were installed still need to be rectified with the SQL query I linked in the previous message.
    Our next regular update 6.3.0 will likely include an auto repair function to recreate eventually missing meta keys, so that it would not be needed to execute the SQL query to repair previously created subscriptions.
    But this update will still take a moment before it’s released so the query is required to fix eventual renewals that would trigger in the meantime.

    The query seemed to have worked fine for OP and we are in contact in an internal support ticket. So I will mark this thread resolved for now.

    Kind regards,

Viewing 16 replies (of 16 total)
  • You must be logged in to reply to this topic.