Services · Ecommerce development · Financial product marketplaces

Financial marketplaces built for Saudi regulators, Saudi rails and Saudi customers.

Codeeo delivers financial product marketplace website development in Saudi Arabia for licensed finance companies, insurance intermediaries, debt crowdfunding platforms, advisory firms and the groups that bring them together. We build the web platform where providers apply to list, products appear in comparable form, customers apply with Nafath verified identity and consent, paid services are charged through mada and other local methods, and commission is invoiced in a ZATCA compliant format. Every rule on the platform maps back to the licence the operator holds.

A Saudi financial marketplace answers to more than one authority. SAMA, the Insurance Authority and the Capital Market Authority each supervise different products, and SDAIA enforces the PDPL across all of them. We design the platform so each listing, application and payout sits under the right rulebook from the first release.

Built for
Licensed or licence applicant operators running financial product marketplaces across the Kingdom, from a single city launch to national coverage.
Typical timeline
Set once discovery has confirmed your licence scope, the providers joining at launch and the payment and identity integrations, then agreed in writing with review points for your compliance team.
What you own
Source code, provider and customer records, consent logs, the commission ledger, payment and gateway accounts and hosting, all registered to your Saudi entity.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the marketplace covers

The national building blocks of a Saudi financial marketplace.

Financial services marketplace platform development in Saudi Arabia is mostly a question of which national systems the platform plugs into and which regulator governs each product category. Personal finance and debt crowdfunding sit with SAMA. Motor, health and property cover moved to the Insurance Authority when it took over from SAMA. Equity crowdfunding and investment products fall under the CMA. A marketplace that mixes these categories needs separate disclosure, consent and complaint rules for each, enforced by the software rather than by a staff memo.

Underneath sit the shared rails: Nafath for identity, SIMAH where credit checks are permitted, mada and SADAD for payment, ZATCA Fatoora for invoices, and data hosted in line with PDPL and the NCA controls. These are the components we build and connect.

Explain your project
  • Provider onboarding by regulator

    Banks, finance companies, insurers, brokers and crowdfunding platforms apply through a portal that asks for their commercial registration and the licence relevant to each product they want to list. Your team reviews documents, records the licence number and expiry, and approves listings category by category, so a provider cleared for personal finance cannot quietly publish an insurance product.

    Only verified, correctly licensed providers reach your customers.

  • Comparable product listings

    Each category gets its own data model: annual percentage rate, tenor and fees for finance, cover limits and deductibles for insurance, target return and risk wording for crowdfunding. Providers enter data through structured forms, and your team approves changes before they go live, so customers compare like with like in Arabic and English.

    Fair, consistent comparisons that hold up to a regulator's review.

  • Nafath identity and consent

    Applicants confirm identity through Nafath before sensitive details are collected, then grant consent for each provider who will receive their file. Consent is recorded with the wording shown, the time and the recipients, and it can be withdrawn from the account area at any point.

    An auditable consent trail under the PDPL for every application.

  • Application routing

    One application can be shared with several providers when the customer agrees, with each provider seeing only the fields it needs. Providers update status inside their portal, and the customer sees offers arrive in one place rather than chasing separate call centres.

    Fewer duplicate forms for customers, cleaner leads for providers.

  • Paid services checkout

    Where your licence allows charging customers, for example for an advice session, a credit report review or document preparation, the checkout takes mada, Apple Pay, credit cards, STC Pay and SADAD bill payment through a SAMA licensed gateway, with receipts issued automatically.

    Customers pay with the methods they already use.

  • Commission ledger and payouts

    Lead fees, per approval commission and listing subscriptions are calculated from the events providers confirm, reconciled monthly, and turned into invoices to each provider. Payouts to referral partners or advisers follow the same ledger, with holds for disputed cases.

    A single figure everyone agrees on at month end.

  • ZATCA e-invoicing

    Invoices to providers and receipts to customers are generated in the format Fatoora requires, with VAT applied correctly and integration to ZATCA handled for the phase your business falls under.

    Tax documents that match the commission ledger.

  • Complaints and disputes

    Customers raise a complaint against a listing or a provider from their account. Each case carries a reference, a deadline and an owner, with escalation to the provider and a record of the outcome for your compliance reporting.

    Complaints handled inside set timeframes, with evidence kept.

  • Provider portal and statements

    Each provider logs in to manage its listings, respond to applications, confirm approvals and download monthly statements. Branch staff and head office users get different permissions, so a regional sales team sees its own leads while the provider's compliance team sees everything published under its name.

    Providers manage their side without emailing your operations team.

  • Search friendly category pages

    Customers rarely search for a marketplace by name. They search for a product type, such as car insurance or SME finance, in Arabic first. Category and guide pages are rendered on the server, carry structured data and hreflang for both languages, and load quickly on mobile data across the Kingdom.

    Organic traffic arriving at the right product category.

Who this is for

Four kinds of operator we build Saudi marketplaces for.

The right first release depends on what you are licensed to do and how many product categories you want to cover. A single category marketplace can launch with a lighter compliance model, while a multi category platform needs separate rules per regulator from day one. These are the four situations we see most often across the Kingdom.

01

Insurance aggregators and brokers

Motor and medical cover are the categories most Saudi customers already compare online. The platform pulls quotes from insurer APIs, shows them side by side with the cover details the Insurance Authority expects to be disclosed, and issues the policy only after payment. We plan around your licence category and the insurers you have agreements with, so quotes and policy documents come from the right source. Renewal reminders and policy documents are stored in the customer account so the next comparison starts with the existing policy.

Insurer integrations are scoped one by one.

02

Finance companies and lending referrers

A finance company or referral partner wants qualified applicants for personal, auto or SME finance. The marketplace collects the application once, checks eligibility rules you define, and routes it to lenders with consent. Debt crowdfunding operators can add an investor side, with SAMA disclosure requirements such as default rates shown where the rules require them. Eligibility rules are editable by your credit team, so a change in a lender's appetite does not need a developer.

03

Advisory and wealth firms

Firms licensed by the CMA for advising or arranging can run a marketplace of investment products, model portfolios or paid advice sessions. We separate educational content from anything that could read as a recommendation, add suitability questions before access, and keep the record your compliance officer needs to show what each customer saw. Paid advice sessions are booked and charged on the platform, with the adviser's licence details shown before payment.

04

Groups launching a national platform

Holding companies, banks and telecom groups sometimes want one platform carrying several product types, often with their own subsidiaries as providers. We design the governance first: who approves listings, how conflicts are disclosed, and how the platform stays neutral enough to be called a marketplace. Ranking rules are documented and shown to customers in plain language, which also protects the operator if a provider questions its placement.

Conflict disclosures are designed into each listing.

Six stages from licence map to a live national marketplace.

  1. 01Licence and product mappingWe list every product category you plan to offer, the regulator that governs it, and what your licence permits you to display, collect, charge and receive commission on.
  2. 02Marketplace rulesListing approval, ranking logic, commission models, refund terms and dispute timeframes written down and signed off before design, because they shape every screen.
  3. 03Arabic first designRight to left layouts, Arabic product terms written by people who know finance, Hijri and Gregorian dates, and English mirrored from the Arabic rather than the reverse.
  4. 04Integration buildNafath, the payment gateway, SADAD, provider APIs, ZATCA e-invoicing and your CRM connected and tested against sandbox environments before any live data flows.
  5. 05Security and compliance reviewNCA control mapping, penetration testing, PDPL records of processing and a walk through of consent and complaint flows with your compliance lead before launch.
  6. 06Launch and expansionA controlled launch with a first group of providers, then new categories and cities added once commission, complaints and support are running cleanly.

Technology

What we build this with.

Chosen for Saudi hosting and audit needs: a modern web framework with server rendering for Arabic SEO, a relational database for the ledger, cloud regions inside the Kingdom where your data classification requires it, and gateways licensed by SAMA.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions Saudi operators ask before building a financial marketplace.

A web platform, a provider portal, an admin system and the national integrations that connect them.

Customers need listings they can compare, an application they complete once and a clear view of offers. Providers need onboarding, a portal to manage listings and leads, and accurate statements. Your team needs approval tools, a commission ledger and a complaints log. Around that sit Nafath, payments, ZATCA invoicing and secure hosting. We scope which of these belong in the first release after discovery. A focused launch with fewer categories and complete compliance tooling is usually safer than a broad one with gaps.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews