Automated FSA/HSA Claim Filing API
For retailers, enterprises and platforms: after the purchase, Burst files your customer's FSA/HSA claim and writes the appeal if the administrator says no.
5 minute read

Short answer
Claim filing is the last of the four jobs Burst's API does for retailers, enterprises and platforms. After your customer buys from you, Burst files the claim with their FSA, HSA or HRA plan administrator, and the administrator pays the customer out of their account. The money comes back to the customer's bank account. If the administrator says no, Burst writes the appeal.
It suits a company that wants its customers reimbursed and doesn't want to run a claims desk. Your checkout stays as it is. Burst is free for merchants, and the customer pays a one-time letter fee.
To see it working, book a call with the Burst team.
Book a call with the Burst team →
What happens after the purchase
A Letter of Medical Necessity on its own doesn't move money. Someone still has to put a claim in front of the plan administrator. Burst does that, in this order:
Your customer requests a letter for what they're buying. A licensed clinician reviews the request and signs the letter. It arrives within 24 hours.
Your customer buys from you and pays the way they already pay. Your checkout and billing stay as they are.
Burst files the claim with the customer's plan administrator.
The administrator reviews the claim and pays the customer out of their FSA, HSA or HRA. The money comes back to the customer's bank account.
The letter has to be dated on or before the purchase, so the moment to begin the letter request is when the customer is deciding to buy. The Letter of Medical Necessity API covers that step.
What your customer does and what Burst does
From the customer's side, a filed claim means there is no paperwork after the purchase.
Step | Without Burst | With Burst |
|---|---|---|
Find the right claim form | The customer | Burst |
Prepare the claim for that administrator | The customer | Burst |
File it with the administrator | The customer | Burst |
Follow up until it's decided | The customer | Burst |
Appeal a denial | The customer, often with help from your support team | Burst |
Receive the money | The customer | The customer, to their bank account |
A customer left to file on their own has to do every step in the middle column. For an FSA holder, money that is never claimed can be forfeited at the end of the plan year.
What your team doesn't build
Filing claims in-house means taking on three pieces of work. Each one stays with Burst.
Forms for each administrator
Every plan administrator has its own claim form, its own required fields and its own way of receiving a claim. A customer base of any size is spread across many of them. Burst prepares each claim for the administrator it's going to, so your team never maintains a library of forms.
Document handling
A claim needs its paperwork matched to the right person and the right purchase. Burst handles that paperwork when it files the claim. Your team doesn't collect, match or resend documents.
Follow-up
Claims take follow-up. An administrator may ask for something more, or deny a claim the first time. Burst handles that correspondence, so your support team isn't writing to administrators on a customer's behalf.
When the administrator says no
If the administrator denies the claim, Burst writes the appeal. Your customer doesn't draft anything and your support team doesn't coach them through it. Burst also refunds the customer's letter fee on a denied claim. The terms your customer sees are short: no letter, no charge; claim denied, money back.
Where claim filing sits among the four jobs
Burst's API does four jobs for the customers of retailers, enterprises and platforms, and claim filing is the one that finishes the reimbursement.
Balance. Your customer sees their FSA/HSA balance in your app or site. See the balance API.
Item-level eligibility. Each item carries a flag: eligible outright, reimbursable with a letter, or not reimbursable. See the item-level eligibility API.
Letters. Your customer requests a letter for what they're buying, and a licensed clinician reviews and signs it.
Claims. Burst files the claim, and the money comes back to the customer's bank account.
The first two jobs tell a customer what they could get back. The letter and the filed claim are how they get it.
For a subscription or a membership, one letter covers 12 months of the recurring charge. A customer on a monthly plan requests the letter once.
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
Does the customer fill out a claim form?
No. Burst files the claim with the customer's plan administrator. The customer's part is requesting the letter, which takes about two minutes.
Who pays the customer?
The plan administrator pays the customer out of their FSA, HSA or HRA. The money comes back to the customer's bank account.
What happens when a claim is denied?
Burst writes the appeal and refunds the customer's letter fee. Your team doesn't write to the administrator and neither does your customer.
Does this change our checkout or billing?
No. The customer pays the way they already pay, by credit card, debit card or buy now pay later. The reimbursement happens after the purchase.
Who is the claim filing API for?
Retailers, enterprises and platforms whose customers buy things an FSA or HSA can pay for.
How do we get access?
Access is by request. Book an intro call with the Burst team.
More on AI and FSA/HSA: what an FSA/HSA API is, the FSA/HSA API for retailers, enterprises and platforms, how FSA/HSA reimbursement works, and all the AI guides.
