01 · Service design across systems

Bringing a Veteran’s payments into one place

I was the primary designer for the Payments page in My VA, the signed-in part of VA.gov, and helped build it. The page brings together medical copays, VA overpayments, benefit payment history, and travel reimbursements from separate systems. I worked out how to show what Veterans need to do, explain when payment information may be late, and keep other information visible if one system is down.

Situation
Combining payments from 3 systems
My role
Primary designer; front-end contributor
Team
Product, research, content; 2 partner teams
Outcome
Launch planned for Nov 11, 2026
VA.gov Payments page shown on desktop and phone, with Action required tasks above the Updates section.

The problem

Medical copays, VA overpayments, benefit payment history, and travel reimbursements came from separate systems. An overpayment can happen when someone receives more benefits than they were eligible for. Overpayments alone had 13 status labels, but those labels didn’t say what to do next. Monthly statements can also show a copay for days after it’s paid, while aging out an unresolved overpayment could hide a needed action.

What I did

Organized debts around the next step

Debts Veterans could act on stay under “Action required”; informational ones go under “Updates.” Unrecognized statuses aren’t shown. If a debt has gone to the U.S. Treasury for collection, the Veteran must contact the Treasury, so it appears as an update instead.

Made room for delayed or missing data

I explained that a paid copay may still appear, and used a warning to ask people to check an item without incorrectly calling it overdue. I also designed for 8 situations, including system outages, so one failure won’t hide other payment information.

Made travel reimbursement tasks specific

Each task names the appointment date and time, so people can tell which trip they’re claiming. In-progress claims are labeled “Saved” or “Incomplete.” Testing with payment records caught claims in the wrong section before launch.

Table mapping overpayment statuses to Action required, Updates, or hidden, and showing whether a due date appears.
Overpayment status routing
Payments empty state beside a partial-error state, where available items remain visible while travel pay data fails to load.
Empty and partial-error states

The result

13 debt labels, 3 clear outcomes

Debts Veterans can act on stay visible, even when old. Informational and unrecognized statuses are handled separately.

Payment information stays available

Across 8 situations, an outage affects its own section. The rest of the page remains available.

Designed, built and tested

I designed and built the page through 6 releases. Testing with actual payment records helped us fix travel reimbursement tasks before launch.

What I learned

The hard part wasn’t putting the records together. It was deciding what to show when systems were late or disagreed.