Published
9 MIN READ
Fintech UI UX: what Pix already requires from the screen
Fintech UI UX is the interface and experience design of financial products, such as payment apps, digital accounts and wallets. In Brazil, part of that screen arrives already decided: the Central Bank publishes minimum user experience requirements for Pix, Brazil's instant payment system, with mandatory names, messages with minimum content and rules for the receipt.
The fintech UX guides I read in September 2026 are from abroad, and none of them mentions that here the interface of Pix participants follows a regulator's document, which has just reached version 7.4, effective March 1, 2027.
At Wama, this comes from delivered work: in 2025 the studio designed and developed the app for Cappta, a payment institution offering payment acquiring and white-label digital accounts, with the interfaces designed in Figma. This text is the design slice within the guide on what the rules require from a fintech's website.
What changes in fintech UI UX?
The cost of a mistake changes, and so does who defines part of the screen. In a financial product, an ambiguous button can send money to the wrong person, so trust, clarity about amounts and confirmation before paying weigh more than in any other digital product.
Short flows, clear hierarchy and the moments that define a SaaS experience also apply to a digital account. The difference is the perimeter: beyond app store and security rules, which are what the Central Bank requires from whoever builds the app, there is an interface layer written by the regulator itself.
Stric, which lets companies operate as white-label digital banks, received branding, SaaS platform design and a website from Wama in 2026, and its clients need to know which screens are free and which follow the rules.
Which part of the screen has the Central Bank already decided?
The entire Pix experience in apps for individuals has a floor set by the Central Bank. The document Minimum Requirements for the User Experience, version 7.3 from December 2025, declares itself an integral part of the Pix regulation, and the obligations apply to the scheme's participants.
Some mandatory items in the current version:
The Pix area is accessible in the main app, on the login screen or right after it, with prominence no smaller than that of other payment methods.
The names are fixed: "Pix", "Chave Pix", "Minhas chaves", "Pix Copia e Cola", "Meus Limites", "Pix Agendado" and "Pix Automático", among others.
Success, error and guidance messages have minimum content, which the brand can rewrite in its own voice but not remove.
Pix security checks cannot ask the user for more actions than the institution's other payment methods do.
The Pix area's home screen has a direct shortcut to the complaints channel, with a notice that the user can file a complaint on the Central Bank's website.
The Description field, up to 140 characters, is shown literally: the app does not render links or dynamic content there.
The last item is design serving security: a clickable link in a transfer message is an open door to fraud. Whoever designs without knowing the manual discovers these rules after the screen is approved, when redoing it costs more.
What does version 7.4 of the Pix manual change by March 2027?
Version 7.4 of the Pix experience requirements, dated September 2026 and effective March 1, 2027, tightens three fronts: receipts, fraud and contact memory. Anyone redoing an app now should design for the new version and put that in writing, as part of what the contract with the developer needs to say.
Change in 7.4 | What happens on screen | Effect for the user |
|---|---|---|
Receipt with an exclusive purpose | Ads, advertising, commercial offers or hyperlinks are prohibited | The receipt only proves the transaction |
Payee's trade name | Shown on the receipt when the payee is a legal entity and has a trade name | The payer recognizes the company |
Favorite contacts | The app stores the Pix key used and alerts the payer if the payee's identification changes | A saved contact stops being a blind shortcut |
Suspected transactional fraud | Mandatory message when the Pix cannot go through because it was flagged as suspected fraud | The refusal comes with a reason |
Standardized statement | Plus and minus signs and the terms Pagamento (payment) and Recebimento (receipt) | Money in and money out without ambiguity |
Pix Automático | The Payment purpose field shown clearly and prominently | The user knows what they authorized to be charged |
MED self-service | Redesigned dispute journey, with screening of what is eligible | Fewer disputes opened through the wrong path |
The direction repeats itself: 7.1, from February 2025, created self-service for the Special Refund Mechanism (MED), and 7.2, from October 2025, began requiring an error message for keys of accounts restricted due to fraud.
Trust, errors and friction: where design still decides
The rules set the floor, and trust is still design work. Guides from UX agencies published in 2026 converge on three ideas: trust is decided by visual precision, legibility is worth more than aggressive simplification, and well-placed friction protects.
The Pix manual confirms the third idea. When the institution needs extra time to analyze a suspicious transaction, the mandatory message states the additional time and offers to cancel, and the document's examples mention 30 and 60 minutes. Design decides whether that wait feels like a failure or protection.
In Wama's projects, that decision weighs on the tracking screens. At Milhas Pix, an airline miles marketplace with payment via Pix, the studio designed in 2025 everything from the acquisition page to the offer management and transaction tracking screens, where the user decides whether to trust the product.
Three practices apply to any financial product:
Error messages with a reason and a next step. Without a reason, the error becomes a support ticket.
Designed waiting states. Pending, under review, declined and refunded deserve their own screen, not a loading icon.
Accessibility from the first draft. The manual recommends larger touch areas, active descriptions for screen readers and videos in Libras (Brazilian Sign Language).
The first contact follows the logic of how to design a product's first use, with one detail: on first access, the manual requires the app to present Pix (speed, availability, cost and ways to pay), and that has to fit into the flow without becoming a terms screen.
What about Open Finance?
Open Finance also evaluates experience. In the optimized journey pilot, regulated by BCB Normative Instruction No. 740 of May 29, 2026, the UX validation of participating brands uses a questionnaire that, according to the pilot's general guidelines, is entirely based on the latest version of the ecosystem's User Experience Guide.
For designers, that is one more interface document on the table: a fintech that will initiate payments or share data through that path checks its journeys against that guide, in addition to the Pix manual.
How to hire design for a financial product
Ask for what the rules require in writing, in the scope, before discussing aesthetics. A well-contracted fintech UI UX project delivers the map of what is regulated and proof that each screen follows the right version of the manual.
Inventory of regulated screens: Pix area, receipt, statement, limits, disputes and favorites.
Error and waiting messages as a deliverable, with the manual's minimum content and the brand's voice.
Receipt and statement prototypes already following version 7.4.
Review against the current and the upcoming manual, with the cutoff date on the schedule.
Design files and access in the fintech's name, because it is worth knowing what changes when the product needs its own code.
At Wama, a single person runs the project from brief to deploy, with no account management layer between whoever decides and whoever designs. Revisions are unlimited within scope, so adjusting an error message until it is clear does not use up a round.
AI comes into the studio's workflow in code and automation, with human review of every output. It speeds up building, not deciding: knowing which screen the regulator has already decided is still people's work.
Common mistakes in fintech UI UX
Designing for the version of the manual that is about to expire. An app redesigned now under 7.3 will have to change its receipt, favorites and statement by March 2027.
Using the receipt as a storefront. Credit banners or offers on the receipt are prohibited by 7.4.
Treating errors as exceptions. In a financial product, refusal, review and refund are main flows and deserve the same care as the success screen.
Frequently asked questions
Does the Pix UX manual apply to every fintech?
The obligations apply to Pix participants, in apps for individuals. A white-label fintech, running on a partner's license, usually designs its own screens, and in Wama's reading the partner tends to require it to follow the manual, because the obligation is the partner's.
When does version 7.4 take effect?
From March 1, 2027, according to the Central Bank, which published the document in September 2026 among the future versions of the Pix regulation. Until then, 7.3 from December 2025 applies, and an app that spans the date needs to meet both.
Can a Pix receipt include a product offer?
Under version 7.4, no. The receipt's sole purpose becomes recording and demonstrating the transaction, and including ads, advertising, commercial offers, hyperlinks or content unrelated to the operation is prohibited. The offer can go on another screen, never on the document that proves the payment.
Is fintech UI UX different from SaaS UI UX?
The craft is the same: research, flow, hierarchy and testing. In fintech, however, a mistake costs the user money, anti-fraud review is part of the flow and the regulator sets names, messages and receipts that a regular SaaS chooses freely.
How much does a digital product project for a fintech cost?
It depends on the number of flows and how much of the product is regulated. As a reference, Wama's general range for SaaS and custom software goes from US$ 4,000 to US$ 20,000, and can reach US$ 40,000 depending on complexity. What moves that number is in how much the first version of a product costs.
If your fintech is going to design or redo its app before March 2027, start with the inventory of regulated screens. Talk to Wama and bring the current flow to the first meeting.
