Allow Payment Links with All-Optional Line Items (Default Total $0) to Still Support Card/ACH Once B

We use HubSpot Payment Links to sell the same product across multiple calendar years (e.g., 2023, 2024, 2025 versions of the same offering). Our buyers often want to purchase just one year, or multiple years at once.

To make this easy, we’ve historically set up a single Payment Link with multiple line items representing each year of the product, and configured all of those line items as optional. The buyer lands on one checkout page and simply selects the year(s) that apply to them. This has worked great for us for years and is a very clean buyer experience.

Recently, we started running into a new limitation: when all line items in a Payment Link are optional, the default total is $0.00. HubSpot now blocks us from editing or creating these links because the “default” purchase amount is below the $0.50 minimum required for credit card or ACH payments.

We fully understand and agree with the rule that there must be at least $0.50 due at checkout for a payment to process via card/ACH. The issue is when this rule is enforced:

  • Previously, we could create a Payment Link where the initial total was $0.00, and card/ACH were valid as soon as the buyer selected one or more optional items.
  • Now, the system appears to enforce the $0.50 minimum at link configuration time, based on the default (all-optional) state, which blocks a valid buyer flow.

From a buyer’s perspective, this is a very common and reasonable pattern: “Select one or more options from this list and pay.” Forcing us to add a “fake” mandatory base fee—just to satisfy the configuration-time minimum—creates confusion for customers and doesn’t reflect our real pricing model.

Request

Please allow Payment Links where:

  • All line items can be optional (so the default total is $0.00), and
  • The $0.50 minimum is enforced at the actual checkout/submit step, based on what the buyer has selected.

In other words, the system should only require ≥ $0.50 at the time of payment, not at link configuration time when no optional items have been selected yet.

This change would:

  • Restore a previously working pattern that we and likely many others rely on.
  • Support very common use cases like multi-year products, event options, add-ons, or bundles where the buyer chooses one or more items on a single checkout page.
  • Maintain the important $0.50 minimum at the moment of actual payment, which we agree is necessary for card/ACH processing.

Thank you for considering this request. This behavior is currently a blocker for us and impacts how we sell our multi-year offerings through HubSpot Payments.

HubSpot enforcing that base-fee validation at the configuration stage rather than the checkout stage is completely breaking custom B2B bundles right now.

While waiting for their dev team to roll this back, the cleanest workaround is to bypass the native payment link entirely. We’ve been using a custom webhook to pass the HubSpot line-item array into a Stripe Checkout session where you can bypass the $0.50 config minimum, and then POST the payment success back to the HubSpot Deal.

Happy to drop the payload structure here if you need an immediate fix.

Hi @JFrey12 and @SamuelOliver - Thanks for the flag! We have fixed this issue. Can you take a look and confirm?

I have this same issue and just sat on with HubSpot Tech for an hour for them to tell me Stripe is making the minimum charge and there is nothing they can do about it. I would think with HubSpot’s customer base power they could get Stripe to change this and allow $0 payment links or quotes still.

@StephanieHong - Thanks Stephanie! Just tested the config validation on our end and the $0.00 default is clearing correctly on the payment links now. Appreciate the fast rollout from the product team.

@JFrey12 - Looks like your native HubSpot payment links are unblocked! Let me know if your team still needs the Stripe webhook bypass for any of your more complex multi-year bundles in the meantime.

Hello! Is your issue that you want to have a $0 checkout through something like a 100% off discount code?

I believe that the original issue has been fixed, so I want to double check if it’s broken for you or if it’s a separate issue.

Hello,

About an hour after your post, the issue did get resolved on my end. This was after spending hours with the Tech support team that didn’t know about the issue or how to resolve it or that it was being resolved. Thank you very much for your follow up but I believe all is good now. My issue wasn’t with a discount code although that was one of the suggestions used to try to get around a $0 payment link for a promotional time and that didn’t work either.

Looks like it’s back to working! Thank you much!!