Pulse: Embedded Crypto Payments

Removing a design-to-engineering bottleneck to deliver a working proof of concept in five days.

My roleProduct Designer & Front-end Developer (Payments, SaaS)
TeamProduct Owner, Engineering, Business Development
TimeframeJuly 2026 · five working days
IndustryFintech, Web3
PlatformWeb, B2B, SaaS
Context

Pulse as a SaaS product

It gives businesses the tools to integrate crypto payment checkout and the operational software to monitor payments, manage settlements and reconcile transactions.

01

Partner integrates Pulse

Through the SDK or API directly into mobile or web products.

02

Customer pays

USDC, USDT or BTC from 20+ networks.

03

Pulse in action

Crypto payment is converted to fiat, settlement is made to the account, and the user gets value.

Product model

Four user personas across three product surfaces

Admin

Manages the workspace, team, settings and operational access.

Developer

Works with API keys, webhooks, documentation and test environments.

Viewer

Monitors transactions and performance without changing the system.

Customer

Completes the embedded crypto checkout inside the product.

Partner Operations Dashboard
Developer Integration Portal
Embedded Checkout SDK
Constraint

A partner wanted to see Pulse working in 5 days

Piggyvest helps over 6 million customers achieve their financial goals by helping them save and invest with ease.

Business Development identified the prospective partner, managed the relationship and translated its interest into a Friday product evaluation.

Piggyvest needed to see the embedded checkout SDK and API working together, supported by the Partner Operations Dashboard and Developer Integration Portal.

Discovery

The capabilities the partner prioritised

Clarification sessions with Business Development and Engineering focused on one question: what are the most important features needed by the partner?

01

Embedded checkout

Customers could complete a crypto payment within Piggyvest's Android and iOS mobile apps.

02

Operational visibility

A portal with roles for teams to monitor, investigate and reconcile transactions.

03

Integration clarity

Documentation, webhooks and API reference for Piggyvest developers to integrate Pulse.

Decision

Handoff the front-end in React directly from the design system

Instead of
  1. Figma high-fidelity mockups
  2. Conversion to front-end
  3. Endpoint implementation
I used
  1. Helium Design system
  2. Prompt and Codex for front-end implementation
  3. Endpoint implementation
Optimised for

Design-system components already existed in Storybook as React components.

Rapid prototyping for review and immediate handoff.

Build and iterate with AI using the Codex harness to hand off the different experiences.

Solution

One working proof across the three product surfaces

Prompt.md

# Master build prompt — Pulse Partner SaaS

Build a high-fidelity, fully functional React prototype of the Pulse Partner SaaS for the seeded partner PiggyVest.

Master prompts

The source documents used for the React build

MASTER-BUILD-PROMPT.mdSelectable text · source excerpt
# Master build prompt — Pulse Partner SaaS

Use the following prompt to recreate the Pulse Partner SaaS prototype represented by this repository.

You are a senior product designer, growth product manager, and master front-end engineer. Build a high-fidelity, fully functional React prototype of the Pulse Partner SaaS for the seeded partner PiggyVest.

This is an enterprise financial-operations product. Think through the user experience and information architecture before composing each screen. The result must feel calm, exact, accountable, and production-ready—not like a generic AI-generated dashboard.

## Source-of-truth order

1. Inspect the existing repository and preserve working functionality.
2. Read PRODUCT.md for product boundaries.
3. Read DESIGN.md for the final dashboard design rules.
4. Inspect the checkout SDK in src/App.jsx and reuse it rather than recreating it.
Design.md

# Pulse Partner Dashboard Design System

The source of truth for an authenticated partner dashboard that feels calm, exact, accountable, and ready for production.

Master prompts

The source documents used for the React build

DESIGN.mdSelectable text · source excerpt
# Pulse Partner Dashboard Design System

This document is the source of truth for the authenticated Partner Dashboard. It complements the detailed checkout SDK geometry.

## Product character

Pulse is an enterprise payment-operations product. It should feel calm, exact, accountable, and ready for production. The interface is not a token-price dashboard and not a collection of decorative cards. It helps PiggyVest reconcile the path from an on-chain payment to an NGN or USD disbursement.

Use the patterns common to strong enterprise dashboard references:

• Keep the partner identity and current environment globally visible.
• Put high-frequency navigation in a stable left rail.
• Use tables for credentials, webhooks, transactions, team members, sessions, and audit history.
• Pair list views with focused detail or inspector views.
• Prefer one clear operational report over a wall of unrelated cards.
Outcome

Five days later, the integrated SaaS proof helped secure the partner business.

The commercial deadline was met.

The partner saw the SDK and API integration working together.

The dashboard showed how the business would operate and reconcile payments.

The frontend became the base for engineering integration rather than a disposable design prototype.

Next

Replace manual provisioning with onboarding + public launch

Work email
KYB
Beneficial owners
Controlling-owner KYC
Passkey and recovery
Business approval
Explore the developer documentation
Next case studyCutting time to value with a passkey-led onboarding