Money movement designed as a conversation, engineered as a transaction system.
A US-based fintech wanted cross-border payments to feel less like a financial form sequence and more like a guided conversation. Mantra Labs helped design and engineer a messaging-first journey backed by identity, payment, notification, support, and cloud architecture.
Cross-border payments fail when users have to trust too many unfamiliar steps at once.
Sending money across borders is a high-intent action with trust, compliance, and clarity requirements.
The experience had to make sensitive steps feel secure and recoverable while keeping the interaction simple on the surface.
Access friction
Users needed a faster way to begin and complete money movement without learning another financial interface.
Trust friction
Identity, card, recipient, and transaction steps had to feel secure, legible, and reversible.
Context friction
The product needed to support sending, requesting, gifting, and account actions without forcing one generic path.
Scale friction
The system had to support future corridors, rails, wallets, and adjacent products.
A messaging-first payment journey backed by transaction architecture.
The surface was conversational, but the operating layer handled regulated payment workflows underneath.
Conversational interface
Guided users through payment actions in a familiar messaging-led channel.
Identity and verification services
Structured trust checks for sensitive financial actions.
Payment orchestration
Send, request, gift, card, recipient, and confirmation flows connected into one journey.
Notification and support layer
Status updates, recovery, and service support embedded into the payment experience.
From message initiation to completed money movement.
Begin in a familiar channel
Start the journey through a conversational entry point instead of a standalone financial workflow.
Verify payment readiness
Sequence identity, card, and account checks before exposing transaction actions.
Choose the action
Support send, request, gift, and recipient-linked flows based on user intent.
Confirm and complete
Make amount, recipient, payment method, and next status clear before completion.
Track and recover
Keep status, support, and future actions available in the same operating layer.
The experience looked conversational. Underneath, it behaved like a transaction-grade operating system.
What changed when the workflow became connected.
Users moved between unfamiliar financial screens and support channels.
Users could move through key money movement actions in a guided messaging-led journey.
Identity, card, recipient, and payment steps created trust friction.
Sensitive steps were sequenced with clearer state, confirmation, and recovery paths.
Send, request, gift, and support actions were treated as disconnected tasks.
Payment, recipient, notification, and support workflows became part of one product layer.
Future corridor and wallet expansion risked adding product complexity.
The architecture supported additional corridors, rails, wallets, and adjacent services.
The chatbot could not be a thin interface on fragmented payment systems.
Payment state had to travel
Every message needed to understand where the user was in the transaction lifecycle.
Trust could not be decorative
Verification and confirmation had to be designed into the journey, not appended at the end.
Support had to stay close
Payment questions, status, and recovery needed to live where the user was already acting.
Expansion needed discipline
Future corridors and payment services had to fit without rethinking the experience model.
Mantra can make conversational interfaces credible for regulated financial workflows.
Beyond a chatbot
The work connected conversation design to identity, payments, support, and operational architecture.
Trust-heavy UX
Sensitive user actions were sequenced into guided, recoverable steps.
Platform extensibility
The system created room for corridor, rail, wallet, and service expansion.
Financial workflow depth
The product story is about operating-layer design, not a messaging widget.
The capabilities behind the build.
Digital Product Engineering
Journey design and engineering across onboarding, recipient setup, transaction flows, and support.
Core Platform Modernization
Service separation and integration logic for identity, payment, notifications, and support.
Data & Intelligence Activation
Structured transaction and interaction state made future guidance and monitoring possible.
Governance & Compliance Enablement
Sensitive payment and identity steps were handled through controlled, auditable workflow design.
Other systems where complexity had to move.
A governed trade-data exchange for ecosystem-scale transactions.
A permissioned trade-data exchange that helped participants share the right information at the right moment without losing control over confidential inputs.
A permissioned exchange layer for structuring, linking, contextualizing, and routing participant data across trade and supply-chain workflows.
Investor confidence before the property transaction.
A connected investor portal and operations console for property discovery, ROI evaluation, documents, appointments, leads, tenants, and support.
A web-based investment platform for property discovery, ROI assessment, investor dashboards, document workflows, appointments, lead management, and operations control.
Insurance decisions made clearer on mobile.
A mobile-first insurance engagement platform designed around customer decisions rather than insurer departments.
Product discovery, buying, claims, renewals, and value-added services redesigned around clearer customer decisions.