Marketplace / Payments / Transaction Platform

EuQueroMilhas

A marketplace platform built to bring structure, trust, and operational flow to airline miles transactions.

EuQueroMilhas was created to organize airline miles transactions that were happening informally through WhatsApp and Telegram groups in Brazil.

The platform was designed to connect people who buy, sell, or quote airline miles and tickets through a more structured experience - with offers, negotiations, chat, payments, wallet tracking, reports, and user ratings inside one system.

Project Snapshot

The shape of the work.

Type
Marketplace / Payments / Wallet / Transaction Platform
Role
Full-stack development, marketplace logic, payment flow, wallet structure, user experience, server configuration
Stack
Laravel, MySQL, HTML, CSS, JavaScript, Mercado Pago API, CEP API, Airports API, Linux server configuration
Deliverables
Marketplace flow, offer listings, quote requests, buy/sell flow, negotiation system, chat, payment flow, wallet, withdrawal request logic, transaction reports, user ratings, external API integrations, Linux server setup

01

Context

The idea came from a real market behavior: airline miles transactions were often handled inside private groups, informal conversations, and fragmented tools.

Experienced users could negotiate through those channels, but the process was difficult to scale, hard to organize, and not accessible enough for people who did not already understand how airline miles worked.

The opportunity was to turn that informal flow into a platform where users, buyers, sellers, and travel agencies could interact through a more organized and trustworthy process.

02

Challenge

The main challenge was not only listing offers. The platform needed to support different types of users and different levels of experience.

Some users already knew how to buy and sell miles. Others only wanted to request a quote without having all final travel details. Travel agencies needed a way to estimate values and connect with sellers before having full customer information.

The system also needed to reduce friction and uncertainty by centralizing negotiation, payment, confirmation, wallet tracking, and user reputation.

03

Solution

I built a marketplace with three main offer segments: quote, buy, and sell.

The quote flow allows users or travel agencies to provide basic trip details, such as passenger count, destination, and travel dates, and receive offers without needing to understand the full airline miles process.

Once a transaction moves forward, users can chat, finalize details, complete payment, track funds, confirm transaction steps, and rate each other after the process.

What I Built

A reusable system of workflows, roles, and product logic.

Each module exists because it supports a real behavior inside the product, not because it looks good in a checklist.

Marketplace Offer Structure

A platform structure where users can list offers, request quotes, buy miles-related services, and sell available miles.

Quote Flow

A simplified flow for users or travel agencies that need estimated values before having all final passenger details.

Buy and Sell Flow

Dedicated flows for experienced users who want to buy or sell airline miles and negotiate directly through the platform.

Negotiation System

Users can make proposals, respond to offers, and move transactions forward inside the platform instead of relying on scattered conversations.

Direct Chat

A chat flow that keeps negotiation and communication connected to the transaction context.

Payment Flow

A payment process integrated with the platform so transactions can move from negotiation to payment without relying on disconnected tools.

Wallet and Withdrawal Logic

Users can track earnings, view available balance, and request withdrawals after the transaction conditions are completed.

Transaction Reports

A reporting area for users to follow their transaction activity and understand the status of each deal.

User Ratings

A rating system that allows users to evaluate each other after a transaction, helping the platform build more trust over time.

Stack & Integrations

The technical foundation.

Laravel

Core backend logic, marketplace structure, transaction flows, business rules, and application architecture.

MySQL

Database structure for users, offers, transactions, wallet records, reports, ratings, and platform data.

Mercado Pago API

Payment integration used to support transaction payments inside the platform flow.

CEP API

Address and location data support where needed inside user or transaction flows.

Airports API

Airport-related data used to support travel, quote, and destination-related workflows.

Media Breakdown

Screens worth reviewing next.

These slots are ready for the final screenshots, videos, or diagrams when you want to replace the interface placeholders.

Marketplace Listings

Users can create and browse offers based on the transaction type: quote, buy, or sell.

Quote Request Flow

The quote flow helps users and travel agencies receive estimates using simple trip information.

Negotiation and Chat

Negotiation stays connected to the transaction through an integrated chat experience.

Payment Flow

Transactions can move from proposal to payment without depending on disconnected external processes.

Wallet

Users can track earnings, available balance, and withdrawal requests inside the platform.

Transaction Reports

Reports help users follow activity, status, and transaction history.

Outcome

What changed.

EuQueroMilhas transformed an informal group-based process into a structured marketplace experience.

Instead of scattered negotiations across messages, payments, and third-party tools, the platform creates a single place for users to list offers, request quotes, negotiate, complete payments, track funds, and evaluate transactions.

The system supports both experienced airline miles users and people who need a simpler entry point into the process, creating a more organized experience for buyers, sellers, and travel agencies.

Next Step

Need a marketplace with real transaction logic?

I build custom marketplace systems with the workflows, rules, payments, user roles, and operational logic needed to support real platform behavior.

Request a project review