1 ) Right now HubSpot’s payment links have no public‑write API: they must be created in the Commerce → Payment Links UI (or cloned there). HubSpot’s Payments API is read‑only and can’t create, update, or manage payment links, so you can’t “auto‑generate” links directly from your product library HubSpot Community.
2 ) You can speed things up a bit inside the app: when you click Create payment link, choose the product from the line‑item picker and save a template—next time it’s two clicks to clone and swap the SKU HubSpot Knowledge Base. If you need true bulk creation, you’d have to script against Stripe’s Payment Links API and store those URLs back in HubSpot (or use an iPaaS like StackSync to sync Stripe ↔ HubSpot).
3 ) Export options are also UI‑only: Commerce → Payment Links lists the link name, amount, status, and a Copy URL action, but there’s no “Export CSV/XLSX” button and the Payments API doesn’t return the link URL—only the resulting payments once a link is used HubSpot Developers
4 ) Work‑arounds for reporting/export: a) create a custom property on the Product object called payment_link_url, paste the link as you create it, then use Products › Export to get an XLSX with name, price, and URL; b) build a small Chrome scrape (or Zapier/Make scenario) that reads the table and writes rows to Google Sheets;
5 ) Bottom line: in‑app creation is mandatory and bulk export as far as I know isn’t released yet, so the cleanest “spreadsheet‑friendly” workflow is to drop the link back onto the Product record as you go and export the product library when Finance needs an update.
1 ) Right now HubSpot’s payment links have no public‑write API: they must be created in the Commerce → Payment Links UI (or cloned there). HubSpot’s Payments API is read‑only and can’t create, update, or manage payment links, so you can’t “auto‑generate” links directly from your product library HubSpot Community.
2 ) You can speed things up a bit inside the app: when you click Create payment link, choose the product from the line‑item picker and save a template—next time it’s two clicks to clone and swap the SKU HubSpot Knowledge Base. If you need true bulk creation, you’d have to script against Stripe’s Payment Links API and store those URLs back in HubSpot (or use an iPaaS like StackSync to sync Stripe ↔ HubSpot).
3 ) Export options are also UI‑only: Commerce → Payment Links lists the link name, amount, status, and a Copy URL action, but there’s no “Export CSV/XLSX” button and the Payments API doesn’t return the link URL—only the resulting payments once a link is used HubSpot Developers
4 ) Work‑arounds for reporting/export: a) create a custom property on the Product object called payment_link_url, paste the link as you create it, then use Products › Export to get an XLSX with name, price, and URL; b) build a small Chrome scrape (or Zapier/Make scenario) that reads the table and writes rows to Google Sheets;
5 ) Bottom line: in‑app creation is mandatory and bulk export as far as I know isn’t released yet, so the cleanest “spreadsheet‑friendly” workflow is to drop the link back onto the Product record as you go and export the product library when Finance needs an update.
I'm using the lowest cost HubSpot plan at the moment, so am unable to generate reports.
I approach my work from two perspectives:
Somebody who has studied both business management, and Information Studies, so am constantly thinking of what information is needed, why, when, and the quickest way to get / use it
A person who has cerebral palsy affecting use of my arms, so constantly thinking about getting as much done, as efficiently as possible
I therefore find it very frustrating (and strange) that neither HubSpot or Stripe allow the export of payment link names, prices, and URLs...
To me, this means that both HubSpot and us merchants have to wait longer to achieve sales. That makes no sense whatsoever and definitely would never be an aim listed in a mission statement!