← Back to portfolio Carla Gulbis, Designer

Product UX/UI · Web + public page + app

Payments: from the clinic's invoice to the receipt on the patient's phone

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.

Authorization: These projects are published with permission from Darwin Saúde, granted by the company’s CTO. That is why the Darwin brand appears on the screens.
RoleUX/UI designer
SurfacesWeb, public page, app
MethodsPIX, card and bank slip
Year2025–2026
Generate payment link dialog over the invoice details

One payment, four ends

1The clinic gets readyIt subscribes to the service, submits company, account holder and bank details for review, and sets installments, interest and link expiration.
2Creates and sends the chargeOn the patient's invoice: picks the accepted methods, generates the link and sends it via WhatsApp, with a reminder before it expires.
3The patient paysOn a public page, no login: PIX with QR code, card in installments or bank slip.
4Everyone follows upThe clinic sees the status and can refund; the patient sees open and paid invoices and downloads the receipt in the app.
Process

Where the decisions came from

Before becoming a screen, every request went through three steps.

01Sources of evidence
  • Heatmaps in Hotjar
  • Support conversations and tickets
  • Feedback from the support team
  • The Jira backlog, with each ticket classified as a bug, a new feature or a usability fix
02Biweekly sprint vote

Every 15 days, the team voted on five criteria, each with 5 levels (from 1 to 5):

CompetencyEffortImpactAutonomyCollaboration
03Complexity

Each ticket got a complexity rating, also on 5 levels:

  1. 1Far below expectations
  2. 2Below expectations
  3. 3Meets expectations
  4. 4Above expectations
  5. 5Far above expectations
The voting scaleSprint Competency & Impact Assessment

The sprint vote followed the Sprint Competency & Impact Assessment, a framework for evaluating the team during technology sprints on a 5-point Likert scale.

  • CompetencyTechnical knowledge and execution skills.
  • EffortDedication and commitment.
  • ImpactValue delivered to the team and the business.
  • AutonomyAbility to work independently and make decisions.
  • CollaborationCommunication and teamwork.

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.

Design decisions

State as the protagonist

The link has a life — and it stays visible

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.

Invoice details with the link awaiting payment and the Expires in 2 days notice
Public page with the payment methods
Generated PIX with QR code and copy-paste code
Payment completed with download receipt
Pay without an account

A public page that asks for no sign-up

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.

Refunds with safeguards

Giving money back safely

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.

Partial refund dialog with the amount to return
Darwin Pay activation with all three blocks complete Consolidated report of payment links by state
Before and after the charge

Activate in blocks, track in one place

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.

App: open invoices with tab selector, status and Pay on the card App: payment receipt in dark theme
The patient's side

Invoices and receipts in the app

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.

The button states the amount

Pay — or understand why you can't

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.

Open invoice details with Pay and the amount Invoice with an expired link and guidance to contact the clinic Receipt with access to the tax invoice

Outcome

Before

A single payment went through four touchpoints — clinic, link, public page and app — and each had to tell the same story.

What changed
  • Same status and same language across the four touchpoints
  • PIX, card or bank slip on a public page, no login
  • Invoices and receipts in the patient app
After

Feedback came through support after the release:

DroppedComplaints about billing and payment
Started coming inPraise for the flow, straight to support

Qualitative feedback, reported by the support team.

← See all cases