Back to Selected work
Tranna Pay / Money Transfer

Tranna Pay money transfer app for Oman to other countries.

A multi-country transfer experience that helps customers in Oman send money to supported destinations with less uncertainty around exchange, recipients and delivery status.

ClientTranna Pay
MarketOman
ProductInternational money transfer app
FocusCross-border transfer journey
Discuss a similar product
The product brief

Make international money transfers from Oman easier to understand.

Sending money from Oman to another country carries several high-attention decisions: who receives the money, how much OMR is sent, what the recipient receives and what happens next.

The experience brings those decisions into one coherent flow, with exchange context, review points, destination details and delivery status visible before the customer confirms the transfer.

The remittance process

Four clear steps from intent to confirmation.

The interface keeps the transfer state visible while giving each decision enough space to be understood.

01

Send from Oman

Oman source

02

Convert currency

Exchange step

03

Choose destination

Supported country

04

Track the transfer

Recipient receives

The product solution

Design the whole system around the decisions that matter.

The solution treats international money transfer as a connected product system—not a single screen. It gives customers sending money from oman and payment operations teams a clear path through send from Oman, convert currency, choose destination, while keeping the decisions, dependencies and next actions visible to the teams responsible for the experience.

01

Recipient and destination selection

Shape recipient and destination selection around the real decisions in a international money transfer journey.

02

Exchange-rate context

Keep exchange-rate context understandable for customers sending money from oman and payment operations teams with clear states, context and next steps.

03

Transfer review and confirmation

Connect transfer review and confirmation to the surrounding workflow without hiding conditions or exceptions.

04

Delivery-status tracking

Make delivery-status tracking reviewable through useful information, ownership and operational signals.

Product-building process

From a framed problem to a product teams can run.

We move from product framing to workflow mapping, prototyping, validation and operational readiness. This is a representative delivery shape.

01

Frame the brief

Align the product opportunity, customers sending money from oman needs and the constraints around international money transfer.

02

Map the workflow

Make the path from send from oman to track the transfer explicit across roles and systems.

03

Prototype the experience

Test the information hierarchy, decision points and recovery paths before committing to a larger build.

04

Validate and operationalise

Review edge cases, controls, service dependencies and ownership so the product can evolve after launch.

Product architecture

A connected architecture for the full tranna pay money transfer app for oman to other countries journey.

A representative system view showing how customer touchpoints, product services, data, controls and external BFSI dependencies work together. The exact implementation would be validated against the client’s existing landscape.

How to read this system

Experience and API decisions sit between the people using the product and the services that fulfil it. Controls, audit context and recovery paths remain visible across every layer.

Impact framing

What a better tranna pay money transfer app for oman to other countries experience should change.

These are the outcomes the product is designed to make possible. They are qualitative design outcomes, not claimed client performance results.

01

Customer experience

A clearer path through international money transfer, with decisions and next steps visible before commitment.

How to evidence itQualitative review of journey clarity, task completion paths and comprehension points.
02

Operations

A shared operating view for payment operations teams to manage ownership, status and exceptions.

How to evidence itWorkflow walkthroughs, queue states, handoff points and exception scenarios.
03

Risk & trust

More deliberate moments for consent, disclosures, review and human escalation.

How to evidence itControl mapping, edge-case review and visible decision history—not an implied compliance guarantee.
04

Product evolution

A modular foundation for extending international money transfer as policy, partners and customer needs change.

How to evidence itCapability boundaries, integration contracts and maintainable release increments.
Project questions

Questions teams ask before building a tranna pay money transfer app for oman to other countries product.

Start with the product and operating questions that shape a credible BFSI delivery plan.

What does this international money transfer product experience cover?

This representative experience covers a multi-country transfer experience that helps customers in oman send money to supported destinations with less uncertainty around exchange, recipients and delivery status. The main flow moves through send from Oman, convert currency, choose destination, track the transfer, with recipient and destination selection, exchange-rate context, transfer review and confirmation treated as connected product capabilities.

Who is the international money transfer product designed for?

The primary audiences are Customers sending money from Oman, Payment operations teams. The interface and operating model should give each group the context, permissions and next action appropriate to its role.

How would integrations and operational dependencies be handled?

The integration boundary would be mapped around international money transfer data, account services and operational systems. Evoque would separate customer-facing states from service responses, surface pending or failed conditions clearly and agree ownership for reconciliation, support and exceptions.

How are security, compliance and responsible AI considerations included?

The product should make consent, access, disclosures, review paths and audit context part of the journey. Where AI is relevant, outputs remain grounded in approved sources with confidence signals, human review and escalation rather than open-ended automation.

Can Evoque build a similar payments & digital assets product?

Yes. We can help frame the product, map the operating workflow, design the experience, connect the required services and build an incremental delivery plan around your users, controls and existing technology landscape.

Build the next journey

Working on a banking or payments product?

Talk to an Expert