Recent content by ChadCLund

  1. ChadCLund

    Need a Payment System Add-On Developed

    My client has decided to use https://oneinfinite.gitbook.io/v1 (One.Lat) for their monthly forum subscriptions. They currently have over 23,000 active members. Due to the nature of this forum (adult discussion related), it has been difficult for them to find and keep merchant accounts. They...
  2. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    Happy Thanksgiving
  3. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    You might also want to check firewall settings in your hosting company. If there are no records in the Payment Provider logs, the IPN callback probably did not get through. Also check your Cloudflare firewall logs to see if an event was triggered. (just my two cents)
  4. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    yeah, I did that earlier this morning.
  5. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    Cloudflare expression: (ip.src eq 51.89.194.21) or (ip.src eq 51.75.77.69) or (ip.src eq 138.201.172.58) or (ip.src eq 65.21.158.36) or (http.user_agent wildcard r"NOWPayments")
  6. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    yes, and what PainBaker said before... not only whitelist their IPs in your firewall, but also set a inbound rule for their referrername.
  7. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    I have gotten alot of these over the past few days. It seems to be random. We get back 'Expired' transactions in the payment log, even though the customer can show us the receipt that the payment was completed. Doing a search in NowPayments shows the status of the transaction as expired. Crazy...
  8. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    well, that sucks...thanks for the heads up though
  9. ChadCLund

    [XB] Payment Provider: NOWPayments [Paid]

    I have an issue. I just purchased and installed (active NowPayments account). No matter which purchase option I select, I get an error saying that the amount is not enough to cover the payment...
  10. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    Awesomesauce, thank you!! Great work, by the way. I appreciate you.
  11. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    @Jeremy P Before I upgrade to 2.3.7, was this issue addresses? It was not mentioned in the announcement, and I don't want to remove my patch with the upgrade if it was not addressed.
  12. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    Awesome... thank you Jeremy. Saved our asses, and noted on the future Stripe API upgrade thing
  13. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    thank you... sure would like to see a fix, and rather quickly...
  14. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    well, we are screwed then and will lose all of our subscribers because even if we were to try to create a Stripe subaccount, those subscribers (and their stripe data (payment intents, invoices, ect)) would not be able to move over to another account.
  15. ChadCLund

    Fixed Tons of errors on backend in Payment Provider log after upgrading to 2.3.5

    I understand what you are saying, but I cannot set up a sub-account in Stripe for various reasons. However, having multiple websites served by my one Stripe account is not the issue. It would seem to me that it would be a simple fix on Xenforo's end.: Look at the code on your webhook, re-map...
Back
Top Bottom