A trust-critical first impression.

Designed registration for first-time and crypto-native users. Added a pre-registration info screen to set expectations before the form; reducing drop-off anxiety and aligning with industry onboarding patterns. Google login was scoped but held for Phase 3; the design accommodated it without requiring a rework later.

Document upload flow: government ID, proof of residence, selfie; designed in three clearly signposted steps. A pre-KYC info screen named what was coming before the user started. Step indicators maintained momentum through a compliance-heavy process.

The original design showed a 24-hour wait notification. After a cross-team review with engineering and cybersecurity, this was replaced with an in-progress status indicator, a copy decision that protected first impressions at a critical trust moment.

While awaiting verification, users accessed a view-only mode; keeping engagement without granting premature trading access.

From asset selection through to crypto release.

Designed the end-to-end flow for purchasing crypto with Mexican pesos. Before wireframing, I mapped the full transaction from both sides: the buyer placing the order and the liquidity provider releasing the asset. Understanding that dual perspective was essential to designing wait states that felt intentional rather than broken.

The key design challenge was the waiting period. Rather than a generic loading screen, the wait state was designed to be descriptive; explaining to the user why they were waiting and what was happening behind the scenes. Once a match was found, the buyer was shown the seller's account details with a clear list of payment instructions, a pattern adopted from established P2P crypto apps to reduce friction at the most anxiety-prone moment in the flow.

After payment, the user uploads proof of payment. The seller verifies and releases the crypto. Order status from pending through to completed is visible throughout.

Releasing Crypto to a Buyer

The liquidity provider sits on the other side of every Buy Crypto transaction; an institutional or registered user releasing crypto assets in exchange for fiat currency via bank transfer. Designing this flow required a shift in lens: this user is experienced, time-pressured, and operating under a strict 10-minute trade window set by KMBIO's business rules.

The LP user browses available orders, accepts a trade, and waits for the buyer to complete payment. Once the buyer uploads proof of payment, the LP must verify and release the asset.

The critical design moment was this verification step. Releasing crypto is irreversible: if the LP confirms without checking their bank account for the actual credit, the asset is gone with no recourse. A warning message was added at this point, deliberately interrupting the flow to prompt the LP to verify funds before proceeding. In a high-trust, time-sensitive transaction, that friction is intentional and necessary.

On completion, the LP's wallet reflects the updated transaction, closing the loop on both sides of the trade.

P2P is KMBIO's core product and primary differentiator.

Kmbio Pro users publish and respond to live trade offers here while setting their own terms rather than accepting platform prices.

Creating a buy advert is a multi-step configuration: the user selects the asset coin, fiat currency, and their preferred price per unit. In the next step they set the total quantity they want to buy, which the system uses to calculate the minimum and maximum order value for that advert. A processing fee breakdown is shown before confirmation, giving the user full visibility of what KMBIO takes before they commit. Payment method and optional trade notes complete the setup. The published advert then appears under My Offers, visible to potential sellers in the P2P market.

The backend was already fully functional. My role here was to redesign the interface and own the UX writing end-to-end that would translate a technically complex configuration into a step-by-step flow, only a Pro user could move through with confidence. Every line of copy required sign-off from the legal and cybersecurity teams before the flow was marked ready for development. The language had to be precise enough to satisfy compliance and clear enough that users didn't need to re-read.

is KMBIO's core product and primary differentiator.

The Phase 2 Buy Crypto flow was designed under time pressure to meet the launch deadline, a deliberate MVP decision that got the product in front of investors on time. Phase 3 was the opportunity to go back and do it properly.

Three things changed:

1. Fiat deposit to KMBIO was marked out of scope by the client and removed from the flow entirely. This simplified the experience and reducing cognitive load for the buyer.

2. The payment method type was restructured to align with the P2P trade model, with the backend already functioning correctly. The design work here was about making the mechanics of how payment works legible to the user.

3. Some screens added in Phase 2 were engineering-led solutions to meet delivery timelines rather than considered UX decisions. The proof of payment upload was a clear example: functioning via a pop-up in one instance and an on-screen file upload in another, inconsistent and rough. The redesign consolidated this into a single, clear interaction pattern.