Remittance Cost Comparator for Gulf to South Asia Corridors Using World Bank Price Data

The problem: the fee looks small, the rate does not

Remittances from the Gulf are a lifeline for families in Pakistan, India, Bangladesh and Nepal. Senders compare advertised fees, but much of the cost is in the exchange rate margin: the gap between the rate they get and the mid-market rate. A transfer with zero fee can cost more than one with a fee. Workers on low incomes, often sending small amounts, lose a large share.

What already exists and the gap

• The World Bank's Remittance Prices Worldwide database publishes the cost of sending money across many corridors, updated regularly, including Gulf to South Asia routes.
• Commercial comparison sites such as Monito compare providers, mainly for Western sending countries.
• The Pakistan Remittance Initiative, a joint effort of the State Bank and government, promotes formal channels for remittances to Pakistan.

The gap is a simple, multilingual tool aimed at Gulf-based workers that explains total cost and lets them check a real quote in a few taps, built on public data with sources shown.

Inspiration

UN Sustainable Development Goal target 10.c aims to reduce remittance transaction costs to less than 3 percent and eliminate corridors costing more than 5 percent by 2030. The World Bank database is how progress is measured. Your project turns that dataset into something a sender can use.

What you build

• Migrant workers enter the amount and the quote they were offered and see the true cost and what their family will receive.
• Families and community groups see which provider types are cheaper on average.
• Researchers and journalists see corridor trends with sources.

The technically interesting part

• Correct cost maths. Total cost equals fee plus exchange rate margin, as a share of the amount sent. Write tests with worked examples.
• Data handling. The dataset is published in periodic releases with its own structure. Build a repeatable import and keep the release date visible.
• Honest comparison. Averages hide spread. Show ranges, not only means.
• Accessibility and language. Many users are on older phones with limited data. Keep pages light.

How to evaluate it

• Calculator correctness against hand-checked examples.
• Data accuracy: spot checks of corridor averages against the World Bank's published figures.
• Usability: time for a test user to check a quote, in at least two languages.
• Page weight and load time on a slow connection.

Suggested plan

• Weeks 1 to 3: study the dataset and choose corridors.
• Weeks 4 to 6: import pipeline and cost calculator.
• Weeks 7 to 10: corridor pages, charts and quote checker.
• Weeks 11 to 13: translations and performance work.
• Weeks 14 to 15: usability test, report and demo.

Path to a product

Migrant welfare organisations, banks wanting to attract remittance customers and fintechs in the corridor all benefit from transparent pricing. A trusted, public-data comparator could earn through partnerships, as long as rankings stay independent. The project is a clean example of building a useful product on open data.

Scope warning

Do not quote live provider prices you cannot verify, and never present your page as financial advice. Show the date of every data release. Do not collect personal financial data beyond what the calculator needs.

Learn what you need on Sefism

• Full-stack roadmap: building the app.
• Data analytics roadmap: importing and summarising the dataset.
• Frontend roadmap: fast, light pages for slow connections.
• pandas User Guide: preparing the data.
• Our World in Data: presenting public data clearly.

Get help with this idea

It is easy to compute cost wrongly or show stale data. Tauseef can help you set up tests and a clear data note. If you are new here, create a free account first.

• Discuss this idea with a mentor
• Send a query to Tauseef
• Book a 1:1 session