How it works
Watch the engine work on one swipe.
Pick a merchant. The software checks eligibility, order, and balance, then leaves a record the member, support, and partner can all read.
Watch the engine
One swipe. Watch the software decide.
Balances stay live across scenarios. Run the guided story, or pick a merchant. The split charge and the explained decline are the ones to watch.
Merchant scenarios
Suggested next:
Decision trace
Press Run the story for the full six-swipe arc, or pick a merchant. Keyboard: Tab to a scenario, Enter to run.
What the engine checks
One swipe. Six things happen.
Members do not see this sequence. Support and partners can. That is the difference between a black box and a usable answer.
01
Inputs
Merchant category, merchant identity, amount, and item data when the merchant sends it.
02
Eligibility
Which wallets may legally pay this merchant. Regulation first. Preference later.
03
Order
Some orderings are required. The rest follow the plan you set.
04
Priority
A good default spends money that expires before money that does not. FSA before HSA.
05
Balance and split
If the first wallet is short, the next eligible wallet can finish the charge. Each leg posts to its own ledger.
06
The record
What was considered, what was excluded and why, what paid, and how it substantiated.
After the swipe
A transaction should leave an answer behind.
When a member has a question, the transaction should not disappear into a black box. Phase 3 is designed to preserve usable context around what happened so member support and partners can respond with better information.
How we sit
Upgrade the card experience. Not the entire benefits stack.
Your administration stays yours. Phase 3 sits at the card and the moment members actually feel.
Your existing stack
- Payroll / HCM
- Eligibility
- Existing TPA
- Plan administration
- Documents and testing
- Broker relationships
Phase 3 Benefits
The modern card layer
- Card and credential
- Member experience
- Transaction context
- Supported program configuration
- Substantiation and support
- Partner surfaces and events
The member moment
- Checkout
- Mobile wallet
- Card
- App
- Transaction answer
- Support
Frequently asked questions
What does a member see after a swipe?
What happened, what amount was approved, which supported benefit paid, and whether anything was not covered. If documentation is needed, that is visible too.
What does support see?
The same transaction context the member sees, plus enough operational detail to answer the question without guessing.
What can a partner receive?
An event with amount, status, sources used, uncovered amount, and substantiation status. Enough to run operations.
See this on your program mix
A clean approval is easy. The useful part is the context that remains when a member or a partner has a question.