Introduction

For many merchants, the most obvious path to unlocking FSA/HSA dollars seems simple:
Just integrate it directly into checkout.

In theory, this makes sense. If shoppers can use their FSA/HSA card like any other payment method, the problem is solved. But in practice, merchants—whether they're Shopify stores, regional grocers, or national retailers—quickly discover the same reality: direct integrations break.

They break in different ways, but the pattern is consistent: split carts, disabled wallets like Shop Pay, confusing consumer experiences, and, ultimately, lost revenue.

This guide explains why the checkout-first approach fails—and how a reimbursement-first model, powered by Burst, makes it seamless for both merchants and consumers.

How Checkout Integrations Work Today

To understand the problem, let's start with the mechanics. When a shopper tries to pay with an FSA or HSA card:

1. The checkout system needs to identify which items in the cart are eligible.

2. It must apply the FSA/HSA payment to those items only.

3. The shopper must use a second form of payment for the rest.

This flow requires precise cart parsing, dual-payment routing, and compliance with IIAS rules maintained by SIGIS. On paper, it's straightforward. In practice, it introduces friction at nearly every step.

The Split Cart Problem

Imagine a shopper buying sunscreen (eligible) and snacks (ineligible) in the same order.

• With a direct integration, the checkout system has to split the order.

• The shopper is forced to pay for sunscreen with their FSA/HSA card, then switch to a second payment method for snacks.

• If they abandon halfway, the merchant loses the sale.

This problem is universal. Whether you're running on Shopify, WooCommerce, or a custom POS, mixed carts create complexity that most merchants can't solve cleanly.

Consumers don't expect checkout to feel like a puzzle. Every added step increases abandonment.

The Wallet Tradeoff

For many merchants, digital wallets like Shop Pay, Apple Pay, and Google Pay drive higher conversion. They're fast, familiar, and trusted by shoppers.

But here's the catch: FSA/HSA acceptance often conflicts with these wallets. Because wallets don't expose item-level cart data, they can't comply with IIAS rules. That means:

• Merchants are forced to disable wallets when offering FSA/HSA acceptance.

• Conversion drops, because shoppers lose their preferred checkout option.

In other words, enabling FSA/HSA directly at checkout often means turning off the very tools that drive your highest-performing conversions.

False Declines at Checkout

Even when a merchant navigates split carts and wallet conflicts, false declines remain a major issue.

• A cart containing eligible products can still be rejected due to MCC mismatches or system errors.

• Shoppers don't know why their payment failed; they just see a decline.

• The perception is that the merchant “doesn't take” FSA/HSA—even if they technically do.

For consumers, one bad experience is often enough to stop trying again. For merchants, that translates into ongoing lost revenue and diminished trust.

The Developer Burden

Checkout-first integrations also create a heavy lift for merchant engineering teams:

• Complex builds: Cart-level parsing and dual-routing logic isn't trivial, especially on platforms with limited customization.

• Ongoing maintenance: Eligibility lists must be kept current. A single misclassified SKU can cause widespread declines.

• Certification overhead: Every change requires validation against SIGIS/IIAS standards.

This can be manageable for enterprise retailers with dedicated payments teams. But for most merchants, it's a drain on resources—and often not worth the incremental revenue captured.

Why Merchants Abandon Direct Integrations

Over time, the pattern repeats:

1. Merchants invest in direct checkout integration.

2. They encounter split-cart friction, disabled wallets, and ongoing compliance challenges.

3. Consumers experience declines and give up.

4. Merchants quietly disable the feature or accept that uptake is minimal.

The result? Billions in FSA/HSA dollars remain unspent, and merchants see only marginal benefit despite significant investment.

How Burst Solves This with Reimbursements

Instead of forcing complexity into checkout, Burst moves the process post-purchase.

Here's how it works:

1. Shoppers pay however they want—credit card, debit, Shop Pay, Apple Pay.

2. Burst confirms eligibility of relevant items pre- and post-transaction.

3. Consumers connect their FSA/HSA accounts to Burst once, and reimbursements are automatically filed on their behalf.

This model does three things:

• Eliminates false declines. Checkout always clears, no matter what's in the cart.

• Protects conversion rates. Merchants keep Shop Pay, Apple Pay, and other high-performing wallets turned on.

• Future-proofs acceptance. As IRS guidance and eligibility evolve, Burst adapts without requiring merchants to rebuild their checkout stack.

The result: a frictionless experience for consumers, and higher captured revenue for merchants.

Examples Across Merchant Types

• An online allergy relief brand. Their shoppers often buy FSA-eligible items alongside non-eligible accessories. With Burst, the full cart clears at once, and the eligible portion is automatically reimbursed.

• A grocery chain with curbside pickup. Mixed baskets are unavoidable. Burst ensures the entire order is captured, and eligible items are reimbursed after purchase.

• A national retailer. Even with sophisticated checkout integrations, edge-case declines cost millions in lost sales. Burst smooths out inconsistencies by filing reimbursements automatically through account connections.

The Bigger Picture

The “checkout trap” is less about technology and more about expectations. Consumers expect checkout to be seamless. They don't care about IIAS, MCCs, or compliance standards—they just want to pay quickly and easily.

Direct integrations force consumers into complexity they don't understand. Burst, by contrast, respects consumer behavior and removes friction.

For merchants, the difference is clear: one approach creates ongoing engineering and compliance headaches; the other captures revenue with minimal disruption.

Conclusion

Direct checkout integrations for FSA/HSA spend look good on paper but consistently fall short in practice. Split carts, wallet conflicts, false declines, and heavy maintenance loads leave merchants frustrated and consumers disappointed.

Burst flips the equation: it preserves the simplicity of checkout, ensures compliance, and unlocks FSA/HSA spend without compromise. By enabling consumers to connect accounts once and automating reimbursements thereafter, Burst makes it possible for merchants to finally capture the dollars they've been missing.

For merchants serious about FSA/HSA, the future isn't about forcing benefits into checkout. It's about embracing the reimbursement model that scales.