Pin Taxi - Complete Solution Taxi app

PinTaxi V4 Coming soon next week is a complete, ready-to-launch ride-hailing platform: four native apps, eleven web panels and a Laravel 12 server, sold as one package with full source code. Version 4 is the release where every hardcoded assumption came out — the currency, the payment provider, the SMS and email providers, the map keys, the language, the fare rules and the commission are all settings an operator changes in the admin panel.

Try the live demo

Every login below is real and works right now. Click a panel’s icon to open it.

<thead>OpenPanelEmailPassword</thead><tbody> Admin paneladmin@admin.com123456 Dispatcherdispatcher@gmail.com12345678 Support desksupport@gmail.com12345678 Accountingaccountant@gmail.com12345678 CRMcrm@gmail.com12345678 CMScms@gmail.com12345678 Fleet panelfleet@gmail.com12345678 Corporate portalcorporate@gmail.com12345678 Driver web paneldriver@gmail.comDriver12345 Rider web panelrider@gmail.comRider12345 Public website—no login needed </tbody>

23 payment gateways, and a real integration behind each one

Each gateway reaches the payment methods people actually use in its market — mada and KNET in the Gulf, UPI in India, Pix in Brazil, OXXO in Mexico, GCash in the Philippines, QRIS in Indonesia, iDEAL in the Netherlands, mobile wallets in Egypt and Nigeria. No payment SDK ships inside any app: the server mints a hosted checkout URL, the app opens it, the server confirms the result.

Paying drivers is the other half of the problem

The driver wallet underneath these rails is a real ledger. Earnings, commission, tips, adjustments and financing instalments are all entries in it, and the headline figure a driver sees is the sum of that ledger — not a second calculation that can quietly disagree with it. A fleet driver’s fare posts to the fleet’s pooled wallet instead, with the fleet’s own cut taken by a percentage you set.

SMS, email and push are settings, not code

Every provider screen has a Verify button that authenticates your saved credentials without spending a message, and a Send test button that actually delivers one. You find out the keys are wrong on the settings page, not from a rider who never got their OTP.

Eleven web panels, eleven separate logins

Around a thousand routes across the eleven panels — and the dispatch board is one shared implementation mounted under four of them, so phone booking, the live map, driver reassignment and cancellation behave identically whether the admin, a dispatcher, support or CRM is using them, and cannot drift apart.

Public website

An instant fare quote before anyone signs up.

Admin panel

The operator’s control room.

Dispatcher

The call-centre booking desk.

Support desk

Answering “where is my driver?” while the caller waits.

Accounting

A finance-only login for the bookkeeper.

CRM

Complaints, lost property and account problems.

CMS

Website content, edited by marketing.

Fleet panel

For taxi companies that supply drivers to your platform.

Corporate portal

Companies whose staff rides are invoiced monthly.

Driver web panel

The driver app, in a browser.

Rider web panel

Booking and tracking without the app.

Rider app · iOS and Android

Book, ride, pay, rate.

Driver app · iOS and Android

Go online, earn, get paid.

What the operator controls

Around 180 stored settings, every one of them reachable from a screen rather than a constant in the source.

Nine languages, right-to-left included

There is a translation editor in the admin panel too: search for untranslated keys, type the wording you want, and it appears across the website, the panels and the apps. Adding a tenth language does not need a developer.

Built to be audited

109 test scripts, 3,648 assertions, and one of them books, dispatches, drives, pays and rates a complete ride end to end against the real application. The whole suite ships inside the download — run it against the copy you buy.

Every feature — all 278 of them

Not a highlights reel. Below is the complete catalogue of what is in the package, grouped by where you would look for it. Everything listed is implemented and reachable — nothing is a stub or a screen without a server behind it.

• First-run language chooser — On first launch the rider picks their language from a list where every language names itself, and the whole app — including the onboarding tour that follows — starts in that language.
• 9 languages with in-app switching — The rider app ships in English, Arabic, French, Spanish, Russian, Hindi, Tamil, Urdu and Turkish, and the rider can switch language at any time from the menu without reinstalling.
• Right-to-left layout for Arabic and Urdu — Choosing Arabic or Urdu flips the entire interface to right-to-left, so the app reads naturally for Middle-Eastern and South-Asian riders.
• Onboarding walkthrough — A short three-panel intro tour explains requesting, tracking and paying for a ride before the rider signs up.
• Email sign-up and sign-in — Riders register with name, email, mobile and password, then sign in with email and password.
• Social sign-in — Google, Facebook, Apple — Riders can sign in with a Google, Facebook or Apple account instead of creating a password.
• First-run walkthrough — Three intro screens explain to a new driver that requests come to them, every trip pays, and the earnings are theirs to withdraw.
• Language chooser and in-app language switch — The driver picks their language on first launch and can change it any time from the menu, with the whole app flipping to right-to-left for Arabic and Urdu.
• Driver sign-up with phone verification — A driver registers with name, email, password and mobile number, picks their country code, and confirms the number with an SMS code.
• Social sign-in — Drivers can sign in with Google or Apple instead of a password.
• Password login, forgot password and change password — Email-and-password sign-in, a reset flow that sends a code to the driver, and a change-password screen inside the app.
• Document upload with expiry dates — The driver photographs or picks each required document — licence, insurance, vehicle photo with plate — and sets its expiry date before submitting.
• Riders & Drivers — Account deletion requests — One screen listing every pending in-app account-deletion request from riders and drivers, with the ability to cancel a request during its grace window.
• Surge — Demand surge pricing — Set how few free drivers count as a shortage, and how much extra to charge when that happens.
• Promotions & Coupons — Promo codes — Create discount codes with an expiry, a usage cap, a target audience and a zone, and see exactly who used each one.
• Wallet — Driver wallet policy — Decide whether cash rides run through the driver’s wallet, and how much a driver may owe you before the system stops offering them rides.
• SMS Settings — SMS provider — Pick one SMS provider from nine, enter its keys in the panel, send a real test message, and verify the saved keys without spending money.
• Email Settings — Mail transport — Pick one of eleven email transports, enter its credentials, set the sender name and address, send a test email, and verify the login without sending anything.
• Admin Panel — The operator’s full control room — every rider, driver, ride, price, payout, integration and sub-account on the platform is managed from here.
• Driver Web Panel — A browser version of the driver app, so a driver can work, check earnings and request a payout without a phone.
• Rider Web Panel — The passenger’s own dashboard — book a ride in the browser, track it live, pay, and see where their money went.
• Dispatcher Panel — The call-centre booking desk — take a ride over the phone, watch every car on a live map, and reassign or cancel in seconds.
• Support Panel — The customer-service desk — answer ‘where is my driver’, rebook or reassign on the call, and clear the payout review queue.
• Accounting / Finance Panel — A finance-only login for the bookkeeper — every revenue statement and every driver payout, with none of the admin panel’s settings.
• Cash — The rider pays the driver in the car; the ride closes without contacting any payment provider.
• Stripe — Card payments charged against a card the rider has saved in the app, including holding the fare on the card before the driver is dispatched.
• PayPal — The rider is sent to PayPal to approve the fare and returns to the app, where the money is captured.
• Adyen — A single global acquiring contract covering most of the world, plus local methods like iDEAL, Bancontact, BLIK, Twint, Swish, Boleto, Konbini and Alipay.
• Checkout.com — Card acquiring across Europe, the Middle East and Asia-Pacific, with the fare held on the card before dispatch.
• PayTabs — Gulf and Egyptian card acquiring with local settlement, carrying mada and KNET on the same checkout as Visa and Mastercard.
• Admin-managed SMS provider system — A settings screen where the operator picks which SMS company sends their text messages, fills in the keys, and switches provider later without touching code.
• Twilio (SMS) — Send verification codes and alerts through Twilio, the global SMS provider.
• Vonage (Nexmo) (SMS) — Send text messages through Vonage, formerly Nexmo.
• MessageBird (SMS) — Send text messages through MessageBird.
• Infobip (SMS) — Send text messages through Infobip.
• Unifonic (SMS) — Send text messages through Unifonic, a Gulf-region provider.
• Dispatch — ride assignment engine — Decides which drivers get offered each ride, in what order, and gives up cleanly when nobody takes it, so riders are never left watching a spinner.
• Fare — pricing, zones and coverage — One pricing engine that prices every ride the same whether it is booked in the app, on the website or by a dispatcher, using the fare plans the operator sets per zone and vehicle class.
• Payout — paying drivers and fleets out — Turns approved driver withdrawal requests into real bank or PayPal transfers, or leaves them for the operator to pay by hand, with full state tracking of what has been sent.
• Financing — vehicle loans and instalments — Lets an operator who buys cars and hands them to drivers record the loan and collect it automatically out of each ride’s earnings.
• Corporate — company accounts and credit limits — Lets companies be invoiced for their employees’ rides instead of the employee paying, with a credit ceiling the operator controls.
• Money — multi-currency charging and reporting — Makes the platform charge, hold, settle and report in real currencies rather than a display symbol, including per-zone currencies.
• Separate logins for every back-office role — Admin, dispatcher, fleet owner, corporate client, support agent, CMS editor, CRM user, driver and rider each sign in through their own guarded login, and one role’s session can never reach another role’s pages.
• Token-authenticated mobile APIs (Passport + JWT) — The rider app authenticates with OAuth2 access tokens and the driver app with signed JWTs; every app endpoint requires a valid token and returns clean JSON on expiry rather than an error page.
• Per-device API rate limiting and brute-force protection — Login, signup, password-reset and verification endpoints are rate limited per device and per account, so nobody can machine-gun password guesses at your server — and real drivers behind a shared mobile network are never throttled by each other’s traffic.
• SMS/OTP abuse controls — Phone-verification codes expire, cannot be resent in a burst, and self-destruct after repeated wrong guesses — which protects both your riders’ accounts and your SMS bill.
• Enforced 8-character password policy — Every password field on the platform — rider signup, driver signup, every panel that creates a colleague’s login, every reset — demands at least 8 characters, set in one place.
• CSRF protection on all web panels — Every form in the admin, dispatcher, fleet, corporate, CRM and CMS panels carries a one-time token, so a malicious page in another browser tab cannot make your logged-in staff perform actions.

…and 254 more. The complete list follows.

Prefer to search or copy it? The complete feature list is also plain text at pintaxi.programna.net/v4.

Talk to us

Three ways in, and every one of them is a real person at Programna. Click a tile.

<tbody> <tbody> Email support@programna.com Opens your mail app with the subject filled in. </tbody> <tbody> WhatsApp +20 100 050 3064 Opens a WhatsApp chat with the message already written. </tbody> <tbody> Web programna.com Documentation, other products and the support desk. </tbody> </tbody>

VERSION 4.0 266 changes since version 2.0

Every entry below is a real change to the shipped code. Where a defect is listed, a test was added with the fix so it cannot come back.

New

NEW Payment methods are now drawn from your admin panel instead of the app build

NEW Riders on a corporate account see their company as a payment option

NEW Drivers get a wallet ledger and can pay their balance in

NEW Vehicle-financing card shows a driver what is left to pay on their car

NEW A driver below the minimum balance is told why requests stopped

NEW Sign in with Apple on all four apps

NEW In-app account deletion with a 30-day window and financial holds

NEW First-run language chooser in nine languages

NEW Language can be changed at any time from the menu

Improved

IMPROVED Every payment runs as a hosted checkout in a secure in-app browser

IMPROVED Riders can top up their wallet with whichever gateway you have enabled

IMPROVED Phone verification runs on your own SMS provider and is checked by your server

IMPROVED Full right-to-left layout for Arabic and Urdu

IMPROVED Server messages come back in the language the app is set to

IMPROVED New black Uber-style sign-in, registration and splash across all four apps

IMPROVED The vendor’s stock-photo splash screen is gone

IMPROVED Apps rebranded to PinTaxi with their own package identifiers

IMPROVED Address search is billed once per search instead of once per keystroke

Fixed

FIXED Idle polling costs a fraction of what it did — measured, not asserted

FIXED Poll cadence is the operator’s to set, and can never make a driver miss an offer

FIXED A live offer is never served from the cheap path

FIXED Driver dashboard totals are cached and invalidated when money moves

FIXED Driver location writes are throttled, not dropped

FIXED Older app builds are unaffected by any of the polling work

FIXED Redis is a supported, exercised upgrade path — and a wrong switch is reported, not fatal

FIXED A health readout tells the operator what they are running on and whether it works

FIXED Push notifications no longer block the ride-request response

Security and hardening

SECURITY Framework internals are no longer downloadable over the web

SECURITY An upload can no longer choose its own filename or extension

SECURITY A webshell, a GIF/PHP polyglot, an SVG and a rogue .htaccess are all refused — proven with real hostile bytes

SECURITY The public contact form is no longer an open mail relay

SECURITY SQL injection removed from the busiest query in the product

SECURITY Rider login now checks the password

SECURITY Rider and driver password-reset account takeover closed

SECURITY Driver authentication restored, and the open document upload closed

SECURITY Real API rate limiting replaces a limiter that allowed 1,000 password guesses a minute

The full release notes — all 266 of them, each with the detail — follow.

Prefer to search or copy it? The full changelog is also plain text at pintaxi.programna.net.

Version 2.0

• AdMob integrated into Android and iOS
• Female driver gender choice on request
• Driver tips
• Flutterwave payments on Android and iOS
• Mercado Pago payments on Android and iOS
• Minor bug fixes

Version 1.0

• Initial release

© 2026 Programna Software Solutions. PinTaxi is licensed, not sold. All source files carry authorship and licence headers; unauthorised redistribution is pursued under the DMCA. Third-party names and marks shown above belong to their respective owners and appear only to identify the services PinTaxi integrates with.