A recovery path for transfers
Manteca requires a linked account for bank transfers. When that information is missing, the flow requests it during the purchase so funds can be returned if the operation fails.
Product Design · Fintech / Web3
R3al BlocksDesigning trust for
real-world asset investing.
Overview
From opportunity discovery
to account management.
R3al Blocks connects people with investment opportunities linked to tokenized real-world assets. The challenge was to make a complex financial category understandable to people with different levels of familiarity with finance and Web3.
The Consumer experience needed to connect discovery, project evaluation, purchase and post-purchase management while responding to real constraints around identity, payments, custody, blockchain and financial communication.
Critical journey
One financial experience, several decisions.
- 01
Discover
Move from the brand promise to a real opportunity.
- 02
Evaluate
Understand the asset, conditions and documentation.
- 03
Validate
Confirm identity and request only the data required.
- 04
Purchase
Choose quantity, currency and payment method.
- 05
Confirm
Make the operation and its current status explicit.
- 06
Manage
Follow investments, orders, balance and movements.
Product and context
Real assets inside a digital experience.
The marketplace translated the proposition into concrete opportunities without turning the experience into a crypto exchange or a speculative promise.
Before opening a project, the cards surfaced the token information needed to continue: estimated annual return, token value, total units and sold units. The hover creates a second level of information while keeping the first view focused on the products.
A concrete case
Understanding the opportunity before taking action.
Mathienzo made the journey tangible: what the asset was, what a person needed to understand before investing and how the Web experience supported that evaluation.
The view organizes the asset, project story, token value, estimated return, payment methods and next action in one continuous experience. Context appears before conversion.
Commercial resultSold out in less than 24 hours.
Presented as a result of the broader project and collaborative work—not as an outcome attributed exclusively to UX design.
Purchase flow
Requesting information when
the payment method requires it.
Registration and identity verification do not force people to complete every account detail upfront. The purchase flow asks for information progressively, according to the selected payment method.
Conversion calculated at the end
When a payment requires currency conversion, the quote is calculated at the end of the flow. This reduces the risk of presenting an outdated amount while the person completes the previous steps.
Launching a new asset
From anticipation to a concrete
investment experience.
Gold was introduced through one continuous sequence: first creating intrigue, then revealing the launch and finally leading into the product view.
It appears after the general purchase flow because its behavior is different from tokenized projects. People can review its value and market evolution, then buy or sell it from the same experience.
After the purchase
The experience continues inside the account.
Buying is not the end of the journey. The account brings together profile information, investments, wallet activity and orders so people can understand what they own and what is happening next.
Each area answers a different post-purchase question: what was invested, which operations are still in progress, which funds are available and what action can be taken from the current state.
Operational states
An order needs a clear state after the purchase.
Mis órdenes makes the status of each operation visible: pending, sold, paid or on sale. The person can understand what happened without reopening the entire flow.
Product and development
Technical constraints became interface decisions.
Identity validation, payment providers, bank transfers, currency conversion and custody were not implementation details hidden behind the UI. They defined when information was requested, how states were explained and which recovery paths were necessary.
The work was developed in collaboration with product and engineering. The case presents the resulting Consumer Web experience and does not attribute business or technical outcomes to design alone.
Product principle
Clarity does not mean removing complexity.
In a financial product, clarity means organizing context, risk and the next action so a person can understand what they are doing.