Hi I am also trying to hit the hubspot serverless end point from cybersecure webhook but I am getting the same 415 error
Most of the payment methods have increased security, previously, we could get some parameters after payment success on redirection link but now they send the data via form post after the payment done but that form data is sent via webhook and hubspot is not listen to that webhook
https://developer.cybersource.com/library/documentation/dev_guides/Secure_Acceptance_Hosted_Checkout/Secure_Acceptance_Hosted_Checkout.pdf
https://developer.cybersource.com/library/documentation/dev_guides/Secure_Acceptance_Hosted_Checkout/Secure_Acceptance_Hosted_Checkout.pdf
Looks like t he content types for incoming requests with the provided JSON or XML are not meetiing the specifics as what Hubspot is trying to confirm which is causing
Also when HubSpot isn’t processing the webhook data kindly check the configurations one more time by referring the below guide
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
Thanks @Humashankar but this is not the issue the problem is cyber secure is sending the data in form-post and if we add our success page in cyber checkout settings where they provide the option to add the redirect link after checkout, but that link should be server-side page only then we will receive we can not simply add our hubspot page link
@Thanks for shedding some light on the workflow
let me also try to triage a bit on this accordingly.
Regards
The 415 unsupported media type error happens because Hubspot serverless functions expect a JSON payload (application/JSON), whereas payment gatways like CyberSource send webhook notifications as application/x-www-form-urlencoded POST data. To fix this, you’ll need an intermediary middleware or edge function (like AWS Lambda or Cloudflare Workers) to parse the form data and re-forward it to HubSpot as valid JSON.
When configuring external payment webhooks and custom endpoints, verifying overall network connectivity and payload headers is crucial to prevent silent failures. If you’re auditing your network layer alongside these integration setups, resources like Network Threat Detection provide helpful context on monitoring network-level traffic and threat behavior to keep your endpoint integrations secure.