#bigt-webhooks
1 messages · Page 1 of 1 (latest)
@deft python you'd have to ask Squarespace what URL they intend to be used — I doubt it's the home page or payment page, it would be something specific where they expect to recieve webhooks.
My guess is you probably don't need an endpoint and can delete it.
Squarespace don't mention it in their guide(https://support.squarespace.com/hc/en-us/articles/206540917), and if they use Stripe in a certain way, they can get events without you needing to do anything or set up a URL, so they probably do that
so if you know what your URL is and you know you are not using it, you could maybe just remove it from your Stripe dashboard.
Well what happened is, there was no way for us to automatically port the members over to Squarespace, so we created a "free" member area on Squarespace for them to sign up to without re-entering their card information, that way we could continue to charge the old members and not ask them to delete their subscription and then resubscribe.
So we can take new subscribers through the Squarespace site with no issue. But getting the charges to go through on the customers from the old, custom site seems to be the problem.
Just keeps getting this 301 ERR
yeah, sounds like your old custom site does not exist any more?
Right, it's still being hosted but we switched the domain to the new squarespace site
or if it does(like you moved ww.example.com to Squarespace but you created www.old.example.com) then you'd need to change the URL in Stripe to point at that
so you'd need to point Stripe at wherever it is currently hosted(with no redirect). Does that make sense?
if you don't have a domain name for where the old site is hosted you can use IP addresses, but it does have to have valid SSL certificates too(we won't send events to plain HTTP links, has to be secure), so it might be tricky unfortunately but that's the situation you're in .