Kazakhstan platform

BaSaZa

not a BAnk of the Self-employed

One operating contour for businesses and self-employed contractors

Contractor onboarding, tasks and payouts — without manual spreadsheets or messengers.

BaSaZa connects the customer, the contractor and the partner bank inside one process: from onboarding to receipts and mandatory payments. We are not a bank, not a tax agent, and we never hold user funds — the bank payment contour stays with the licensed partner bank.

BaSaZa is an internet platform. All settlements and transfers are executed by a licensed partner bank in accordance with the legislation of the Republic of Kazakhstan.

Task and result
Task
Prepare product cards for an online store
Status
Result approved

Result

24 product cards uploaded; descriptions and photos verified by the customer.

Fragmented processes do not scale

Fragmented processes do not scale

While onboarding, tasks, payouts and mandatory payments live in different spreadsheets and chats, mistakes and missed deadlines are inevitable.

Spreadsheets and messengers
Contractor data and tasks live in scattered files and chats without a shared history or owners.
Manual payouts
Registries are built by hand; a single bad row blocks the entire payment and postpones the rest.
Missed mandatory payments
Tax and social deadlines get lost between emails; penalties arrive unexpectedly.
No transparent history
Who approved the result, who changed the amount and when — reconstructing this takes weeks.

Value for every party

BaSaZa is built for three roles at once: the customer, the contractor and the partner bank. Each party sees its own scope of responsibility and knows the next step.

For business (LLP)
  • Onboard self-employed contractors with data checks and role confirmation.
  • Tasks, work results and approvals live in a single history.
  • Payout registries with row-level statuses and retry only on failed rows.
  • Control over mandatory payments with a clear next step for accounting.
  • Documents, reports and exports for tax and internal reviews.
For self-employed
  • A single account for every customer and task.
  • Transparent remuneration, receipts and payout history.
  • Reminders for mandatory payments and a clear next step.
  • Marketplace of public tasks and a contractor catalogue.
  • Documents and income confirmations inside the workspace.
For the partner bank
  • A unified digital contour for accepting payout registries.
  • Row-level payment statuses and correct handling of partial failures.
  • Participant identification and a verifiable operations history.
  • A point of presence in front of the Kazakhstan business and self-employed audience.

The full platform process

From registration to reporting — one digital contour where every operation has a status, an owner and a trace in history.

  1. 1

    Registration

    A company or self-employed contractor confirms data and role.

  2. 2

    Contractor onboarding

    Invitations, data checks, agreement to terms.

  3. 3

    Tasks

    Task briefs with descriptions, deadlines and remuneration amounts.

  4. 4

    Work result

    The contractor submits the result; the customer approves it.

  5. 5

    Accrual

    Calculation of remuneration, mandatory payments and related costs.

  6. 6

    Payout registry

    Registry with per-row amounts and recipients.

  7. 7

    Bank contour

    The registry is sent to the partner bank; the bank processes payouts.

  8. 8

    Payout

    Successful rows close; failed rows return with a reason.

  9. 9

    Receipt

    Receipt is recorded and linked to the task and the contractor.

  10. 10

    Mandatory payments, documents and reporting

    Deadline control, documents and exports for reporting.

How it looks inside the product

Below are fragments of the product interface on demo data. All amounts, identifiers and names are fictional.

Payout registry

Row-level statuses: successful payout, failure with a reason, pending.

  • Contractor
    A. Yerlanqyzy
    Amount
    KZT 185,000
    Status
    Paid
  • Contractor
    D. Talgatuly
    Amount
    KZT 142,500
    Status
    Failed
    Invalid bank details
  • Contractor
    G. Aidarqyzy
    Amount
    KZT 96,000
    Status
    Pending

A single failed row does not block the others. Only failed rows can be retried.

Accrual
RemunerationKZT 185,000
Mandatory paymentsKZT 18,500
Platform feeKZT 5,000
Bank costsKZT 800
To fundKZT 209,300
Payout totalKZT 185,000
Receipt
Number
RCP-2026-001482
Issued
12 Mar 2026
Contractor
A. Yerlanqyzy
Amount
KZT 185,000
Status
Confirmed
Mandatory payment
Obligation
Mandatory payment on remuneration
Deadline
25 Mar 2026
Amount
KZT 18,500
Status
Awaiting payment

Next step

Fund the payment through the partner bank by 25 March.

Documents and reporting

Contracts, acts, reports and exports — with versions and history.

  • Contract

    Service contract

  • Act

    Act of completed work

  • Report

    Consolidated accruals report

  • Export

    Mandatory payments export

Marketplace of contractors and tasks

Public tasks and an open catalogue of self-employed contractors — with filters, applications and in-platform ratings.

Public tasks
All tasks
  • Courier delivery across Almaty

    20 Mar 2026

    KZT 120,000

  • Short video shoot and editing

    28 Mar 2026

    KZT 260,000

  • Copywriting for product cards

    22 Mar 2026

    KZT 90,000

Contractor catalogue
All contractors
  • A. Yerlanqyzy

    Copywriting

    Almaty

  • D. Talgatuly

    Logistics

    Astana

  • G. Aidarqyzy

    Video production

    Shymkent

Security and action confirmation

Significant actions require explicit confirmation. The confirmation method depends on the partner bank and platform settings.

Confirmation summary
  • SMS code
    Available now
  • EDS
    Planned as a configurable capability
  • Digital ID
    Planned as a configurable capability
  • Biometrics
    Planned as a configurable capability
Core principles
  • BaSaZa never accepts or holds user funds — settlements are performed by the partner bank inside the lawful payment contour.
  • Financially significant history is append-only: corrections create versions and preserve prior values.
  • A single failed row in a payout registry does not block the others; retries apply only to failed rows.

Partner bank

A neutral slot for the future partner bank. We do not claim an existing partnership with any bank. Logos and products will appear only after a partnership is legally confirmed.

Partner bank

Neutral slot for the future partner bank. Logos and products will appear once a partnership is confirmed.

Frequently asked questions

Short answers to the key questions. The full list lives on the FAQ page.

Is BaSaZa a bank?
No. BaSaZa is an internet platform. Money stays inside a licensed partner bank; the platform organizes process and data.
Who pays the taxes?
The calculation and transfer of mandatory payments follow the legislation and the selected bank integration model.
What happens if one payout fails?
Successful rows close; the failed one returns with a reason. Retries apply only to failed rows — successful payouts are never duplicated.
How are significant actions confirmed?
SMS codes are available today. EDS, Digital ID and biometrics are planned as configurable confirmation capabilities and connect as they mature.

Ready to bring work with self-employed contractors into one contour?

Open the company or contractor workspace — the interface runs on demo data with no connection to production systems.