Product UX/UI · Web + public page + app
A single payment goes through four hands: the clinic that activates the account and creates the charge, the link sent over WhatsApp, the page where the patient pays and the app where they follow up. The challenge was keeping the same state — and the same language — at all four ends.
Before becoming a screen, every request went through three steps.
Every 15 days, the team voted on five criteria, each with 5 levels (from 1 to 5):
Each ticket got a complexity rating, also on 5 levels:
The sprint vote followed the Sprint Competency & Impact Assessment, a framework for evaluating the team during technology sprints on a 5-point Likert scale.
Each dimension is rated from 1 to 5, helping identify strengths, development opportunities and areas for continuous improvement.
Goal: promote transparency, encourage professional growth and support data-informed team development.
Awaiting payment, about to expire, paid, refunded, expired, canceled: each state has its own reading and the right next action, like "generate a new link" when the previous one expires.
The patient opens the link and pays. If the card is declined, the filled-in data stays; if the charge was already paid, canceled or expired, the page says so instead of charging again.
Full or partial refund, blocked above the paid amount and confirmed before it runs. With no balance in the account, the refund stays pending with two ways out: top up the balance via PIX or cancel.
Activation splits the sign-up into three blocks — company, account holder and bank details — and only allows submitting for review once all three are complete. Afterwards, the report gathers every link by state, with each total at the top.
Open and paid in a tab selector, from more than one clinic. Each invoice shows its status, whether it already has a tax invoice and, when there is a link, a Pay button with the amount. One receipt per payment, to save or share — and an invoice settled outside the platform also shows as paid. All in light and dark themes.
With an active link, the button already shows how much will be paid. With no link, or an expired or canceled one, the button disappears and an explanation takes its place, saying what to do. The receipt warns it is not a tax invoice — and, when one exists, links to it.
A single payment went through four touchpoints — clinic, link, public page and app — and each had to tell the same story.
Feedback came through support after the release:
Qualitative feedback, reported by the support team.
← See all cases