One account.
Many ways
of operate.
Create your financial product.
Connect the experience to operations.
Experiences, each with its own job.
The bank shows up in channels.
Context runs through all of them.
Create your own financial experience or modernize your current one. Define brand, channels, and operating rules; the composition depends on scope and validated integrations.
The same foundation.
Different jobs.
Switch the context to explore
how each interface takes part.
The bank keeps track
the person's pace.
Balance, statement, Pix and tracking on mobile. The experience shows the next step and what still needs confirmation.
- Arrive with context
- Device binding is part of access.
- Understand the position
- What is available and what is on hold are kept separate.
- Know what happened
- Operation states help people keep going.
A POINT OF CONTINUITY.
More room for
look at the account.
An experience designed for reading, viewing, and preparation. The desktop design keeps the mobile device in the authorization journey.
- Read the statement
- Transactions and receipts in a spacious workspace.
- Prepare an operation
- The person reviews the information before continuing.
- Authorize on the device
- The prototype separates preparation on the computer from confirmation on the phone.
of the account's transactions.
Those who operate need
see the context.
Accounts and blocks have interfaces implemented in the console. The guide also presents the design for orders, access and analysis.
- Monitor accounts
- An operational view, with position and status.
- Understand reserves
- Amounts, reasons and references help explain what is available.
- Separate responsibilities
- The console shows the work and the responses from the foundation.
Between tapping
and happen,
exists one foundation.
The channel, the capability, and the provider each have their own roles. This separation helps evolve the experience with more clarity about who is responsible for each piece of work.
The experience presents.
App, desktop and console play different roles. The channel organizes the interaction and shows the state received from the core.
Banking receives the app. BaaS connects the account and the provider. Banking Product Portfolio organizes the product catalog.
A request.
Two sides of the experience.
Walk through an example to see how the account holder's experience connects to the operations team's work.
The request starts in the channel.
The person prepares a transaction and reviews what they intend to do.
Explanatory demo. No order, authorization, or transaction is carried out.One operation.
A clear next step.
The console should not yet treat intent as a transaction.
Having a balance.
Understand what
can use.
A hold changes how the balance is read. Explaining the available balance helps the account holder decide the next step and helps the team respond clearly.
A simplified reading of the guide's structured hold example. It does not double-count holds already deducted by the provider.Illustrative example in USD. Fictitious amounts; no currency conversion.
Part of the amount goes elsewhere.
The structured reserve of USD 200.00 reduces the balance available for transfers to USD 100.00.
Behind the account,
there is an operation.
The console brings position, reason, and history together.
Whoever handles it finds an explanation.
Operators find the context.
How much is on hold.
For what reason.
Which reference accompanies the block.
can be explained.
Other areas of the console appear in the guide prototype. Open the screenshots to explore the design.
See the composition
gain ground.
A visual montage of the reference screenshots. To see the details, open the images in the gallery.
Assembling product materials.This is not a recording of a banking transaction.
Browse the screenshots and zoom in on the details.
Account portfolio, balances and authorization policy in the console.
Console implemented · staging · guide dated 09/29/2026Preserved reference
docs/design/conta-app/guia/real/bo-real-accounts.jpgdee85d302cb884dfe801dcdfe3af3668c82d0b55Available, reserved, and spendable: a reading of the account position.
Console implemented · staging · guide dated 09/29/2026Preserved reference
docs/design/conta-app/guia/real/bo-real-holds.jpg3f9abd9b58d9da8c47589ebf178639a87f82d2c1Staging screenshots. These are not a recording of a flow and do not confirm that these interfaces have been released to production.
The product meets
its parts.
A composition can bring these capabilities together depending on the scope. Explore the role and stage of each one.
The app's entry point
Connects the channel to the responsible capabilities.
The relationship with the account
Organizes the integration with the banking provider.
Identity and access
Defines people, organizations and permissions.
Identity verification
Can be part of the planned verification journeys.
The product catalog
Organizes products and their versions.
Step-by-step evolution
Controls the exposure of configured features.
A history with a reference
Records the events published by the capabilities.
Account activity
can be part of
a bigger product.
Your account can connect to your own credit product. Explore how proposal, acceptance and tracking can make up this journey, depending on scope and integrations.
Design your credit product ↗A complete view.
With source context.
The materials show the product's direction and the parts already implemented. The availability of each journey depends on your scope and validated integrations.
See the full guide ↗On-device capture, as of 10/09/2026. Implementation and journeys evolve with the technical documentation.
Account holder prototype in the guide. The image shows the experience design.
Accounts and holds appear in screenshots from the implemented staging environment. Other areas shown here are prototypes.
The catalog distinguishes between Alpha and Beta stages. A screen or simulated test does not confirm certification of a real integration.