Platform — Payments

Money thatmoves now

Real-time payments, transfers and merchant collections, built for Algeria: person to person, business to business and merchant payments settled as they happen — not gathered into a nightly batch and cleared the next working day.

Scroll

01 — Real time, not overnight

Every payment, as it happens.

A payment on Pixely is not a request that waits for the end of the day. It is screened, routed and posted while the person who sent it is still looking at the screen — and both sides see the same state at the same moment.

01

Person to person

Send to a contact or an account, and the money is there when the confirmation is — no waiting for the next clearing cycle.

02

Business payments

Suppliers, payroll and transfers between your own entities, with the approvals your organisation already requires sitting in the path of each one.

03

Merchant collections

Take payment online, in store or by request, and see each collection land on your ledger the moment it settles rather than in tomorrow's report.

04

Payouts

Pay many people at once — sellers, staff, refunds — by file or by API, every line tracked to its own outcome.

05

One confirmation

The sender, the recipient and your systems all hear the same thing at once: initiated, settled, or refused and why.

06

Reconciled as it lands

Every movement arrives categorised and matched to what it pays for, so reconciliation is a property of the ledger rather than a monthly event.

Payment eventsSample

  • payment.initiatedp2p · mobileOK
  • screeningsanctions · no matchCLEARED
  • policywithin limitsCLEARED
  • route.selectedbook transferBOOK
  • ledger.posteddebit · creditPOSTED
  • payment.settledrecipient notifiedSETTLED
  • collection.receivedmerchant · qrSETTLED
  • route.selectedlarge valueARTS
  • approvalpayroll · 2 of 3HELD
  • route.selectedforeign supplierSWIFT
  • policyvelocity exceededREFUSED

02 — The rails underneath

Four ways out, one platform.

Algeria's money moves on national rails, and the platform is built on them rather than around them. Each payment is routed to the rail that fits it — and whichever it takes, it lands on the same ledger, in the same record.

  1. 01

    Book

    Inside the platform

    Between two accounts on Pixely, a payment is a pair of entries on one ledger. There is no rail to wait for.

  2. 02

    ARTS

    Real-time gross settlement

    Large-value payments between banks, settled one at a time and in real time rather than netted at the end of the day.

  3. 03

    ATCI

    Interbank clearing

    The everyday payments that pass between Algerian banks — transfers, collections and card payments — cleared on the national system.

  4. 04

    SWIFT

    Cross-border

    Payments that leave the country, on the network banks use to message each other worldwide, with the foreign leg on the same record.

03 — How it runs

From a tap to settled.

Four movements, and none of them waits for the night: the checks run in the path of the payment, not after it.

  1. 01

    Initiate

    From an app, a checkout or an API call — the payer proved once by the platform's identity layer, not asked again.

  2. 02

    Screen

    Limits, policy, sanctions and fraud signals judged before anything moves, with the reasons kept beside the decision.

  3. 03

    Route

    The platform chooses the rail — book transfer, ARTS, ATCI or SWIFT — from where the money is going and what it is for.

  4. 04

    Settle

    Posted to the ledger, confirmed to both sides and announced to your systems at once. The record is final, and it is the same everywhere.

04 — Built around

The texts it answers to.

A payment platform in Algeria is built for a body of law, not around it. These are the texts the payments service is designed to work within.

Each text opens in the Journal Officiel of the République Algérienne, in its French edition, at the page it starts on. They name the framework the platform is being built for; they are not a licence or a certification.

05 — Get started

Move yourfirst dinar

Create an account and move money between sandbox accounts, or talk to an engineer about your flows and your rails.