• Resolved MDC2957

    (@mdc2957)


    This can be deleted; it wasn’t an issue with BTCPay.

    • This topic was modified 5 months, 3 weeks ago by MDC2957. Reason: resolved, not a BTCPay issue
Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter MDC2957

    (@mdc2957)

    Coming back to this again.. Is it at all possible to make it so that the order doesn’t get created until payment is received? The way it works now is when I check out, the order gets created under the “pending payment” status and although that’s unpaid, if you’re using an “order created” webhook for some other automation that depends on a payment actually being received, it creates a problem. So is there a setting or some way to change the process of this plugin so that the order doesn’t even get created in Woo until the payment is actually received?

    Plugin Author ndeet

    (@ndeet)

    It sounds like you want to trigger your make.com stuff only after the payment has been completed and not when the order is created to ensure make.com only gets triggered in that case.

    How does your current setup look like? You trigger make.com stuff with a webhook from Woo or BTCPay? Maybe there is a Woo make.com plugin that fixes your issue?

    Thread Starter MDC2957

    (@mdc2957)

    Yes, that’s correct. The way it is now, as soon as someone clicks BTCPay, the “pending payment” order gets created, and that triggers the “order created” webhook, which triggers the Make scenario.

    The scenario is triggered by the Woo webhook “order created” Unfortunately, I don’t see a “payment received” webhook. I’m not sure if any plugin exists, but I will check.

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