FSA/HSA Balance API for Apps and Retailers
Show customers their FSA or HSA balance inside your app or site. Burst's API is for retailers, enterprises and platforms, and checkout stays as it is.
5 minute read

Short answer
Burst's balance API lets a retailer, enterprise or platform show customers their FSA or HSA balance. The customer connects their FSA/HSA account once. From then on, your app or site can show them how much they have, in the places where they decide what to buy.
The balance is the first of four jobs. Once a customer can see the money, Burst flags which items can be reimbursed and helps them request a Letter of Medical Necessity where one is needed. Burst files the claim, and the plan administrator pays the customer back to their bank account. Your checkout stays as it is.
To see it working, book a call with the Burst team.
Book a call with the Burst team →
What your customer sees
The customer connects their FSA/HSA account once. After that, the balance appears inside your product, next to the things it can pay for.
Before | With the balance in your app |
|---|---|
The customer opens their plan administrator's site to find out how much they have | The customer sees the number on your account page, in the cart or beside a product |
They shop without knowing the money is there | They know how much they have while they're choosing what to buy |
An FSA holder finds out about leftover money after the plan year ends | An FSA holder sees what's left while there is still time to use it |
The customer still pays you with the card or payment method they already use. The balance tells them what their FSA or HSA can pay back afterward.
Why a balance in your app matters
People spend what they can see. Most account holders see their FSA or HSA balance only on their plan administrator's site, which they rarely open while shopping. When the number sits in your cart, on your account page or on your home screen, the customer learns two facts while deciding what to buy. They have this money, and it can pay for things you sell.
FSA money also has a deadline. Under the rules in IRS Publication 969, a health FSA is use-it-or-lose-it: money left at the end of the plan year is generally forfeited, apart from a grace period or a limited carryover if the employer offers one. An HSA has no such deadline and its balance rolls over each year.
That difference shapes what you show. An FSA holder with money left in the last weeks of the plan year has a reason to buy now, and a balance beside a list of things it can pay for gives them a way to act on it. An HSA holder is under no such pressure, and for them the balance answers a different question, which is whether the account can cover a larger purchase they've been considering.
Where to show the balance
The balance does the most for a customer when it appears next to something they can do with it.
On the account page. The customer sees the balance each time they sign in, beside their orders and saved items.
In the cart. A retailer shows "Your HSA balance" above the items in the cart that can be reimbursed.
On the product page. Paired with the item-level eligibility flag, a product page can say that an item can be reimbursed and that the customer has the balance to cover it.
On a membership screen. A health or wellness app shows the balance beside the monthly fee, with a prompt to get the membership reimbursed.
In a benefits dashboard. A benefits platform shows FSA and HSA balances beside the employee's other benefits.
In reminders before the deadline. An email or a notification in the last weeks of the plan year tells an FSA holder there is money left and links to what it can pay for.
In your own assistant. If your product has a shopping or benefits assistant, it can answer "how much is in my FSA" from the same balance your app shows.
What comes after the balance
A balance on its own tells a customer they have money. The other three jobs get them paid back. Each item carries one of three flags: eligible outright, reimbursable with a letter, or not reimbursable. Where a letter is needed, Burst helps the customer request one for what they're buying, and a licensed clinician reviews and signs it. Burst files the claim with the plan administrator. If the claim is denied, Burst writes the appeal.
Through all of it, the customer pays at your existing checkout with the card they already use. Burst is free for merchants, and the customer pays a one-time letter fee when a letter is needed.
Burst is the only AI-native FSA/HSA company: a person can point their AI agent to Burst to request a Letter of Medical Necessity, and retailers, enterprises and platforms use Burst's API to show customers their balance, flag which items can be reimbursed, help them request letters and file their claims.
Frequently asked questions
Who is the balance API for?
Retailers, enterprises and platforms that want customers to see their FSA or HSA balance inside the company's own app or site.
Does the customer connect their account every time?
No. The customer connects their FSA/HSA account once, and from then on your app or site can show their balance.
Does showing a balance change our checkout?
No. Customers pay the way they already pay. The balance tells them how much their FSA or HSA can pay back after the purchase.
Is the balance more useful for an FSA or an HSA?
Both, for different reasons. An FSA balance has a deadline, so seeing it prompts a purchase before the plan year ends. An HSA balance rolls over, so seeing it helps a customer plan a larger purchase.
What does it cost?
Burst is free for merchants. The customer pays a one-time letter fee when a purchase needs a letter.
How do we get access to the balance API?
Access is by request. Book a call with the Burst team and tell them where in your product you'd show the balance.
More on AI and FSA/HSA: what an FSA/HSA API is, the FSA/HSA API for retailers, enterprises and platforms, and all the AI guides.
