Solutions

One connection.
Every corridor you are licensed for.

Payzone is built for organisations that already carry the licence and the liability. You bring the regulatory permission and the customer relationship; the platform brings the corridors, the controls and the record.

The outcomes
  1. 01

    Reach corridors without signing twenty contracts

    One integration and one commercial agreement covers origination through payout. Provider relationships, certification and reconciliation sit behind a canonical contract instead of on your roadmap.

    Reach
  2. 02

    Answer the de-risking question before it is asked

    Correspondent banks do not de-risk businesses for moving money. They de-risk businesses that cannot evidence how they moved it. The evidence is produced as a by-product of operating.

    Banking
  3. 03

    Put the control in the path, not in a policy

    Screening before authorisation, maker–checker on binding instructions, step-up authentication on privileged actions. A control that can be skipped under pressure is not a control.

    Risk
  4. 04

    Survive an examination without a project

    Append-only records and write-once evidence mean the audit answer is a query, not a three-week reconstruction from spreadsheets and email.

    Assurance
  5. 05

    Stop stranding liquidity at a correspondent

    Settle a corridor position once, net, on a cycle both sides agreed and countersigned — instead of moving money for every obligation in both directions and funding a bank account to do it.

    Liquidity

Applied by entity type on Industries. The settlement mechanics are on Clearing and settlement.

One integration

Send and pay out on a single connection.

A single API covers origination through to settlement. You are not stitching a quoting service to a payout provider to a screening vendor and reconciling three sets of identifiers afterwards.

API reference
Capability

Two sides, one contract.

Origination and payout are the same integration, so a transfer keeps one identifier from quote through to settlement.

Send

Quote, create and authorise a transfer. Sender and beneficiary requirements come from the corridor, not from your code.

Pay out

Bank account, mobile wallet or cash pickup, routed to a rail certified for that exact country and method.

What you are actually buying

Three things that are hard to build and harder to prove.

01

Corridor reach

Twenty destination markets across South Asia, South-East Asia, Africa, the Middle East, Latin America and Europe — with three payout methods and per-country, per-method certification behind each route.

02

Compliance that holds

Screening before authorisation, maker–checker on binding instructions, step-up authentication on privileged actions, and case management for holds. Controls sit in the authorisation path, not in a procedure document.

03

A record that survives scrutiny

Append-only financial and compliance records, hash-chained audit events, and write-once evidence for binding decisions. Corrections are compensating entries — originals are never edited.

Why integrators choose it

A single API

Origination, payout, compliance and reporting on one contract.

Idempotent by default

Retry after a timeout and get the original result, never a duplicate transfer.

Typed errors

Stable machine-readable codes. Compliance outcomes are explicit states.

Traceable end to end

A correlation id you supply, carried through every hop and every record.

Scoped access

OAuth 2.0 scopes bound to what your entity is authorised to do.

Fails closed

Unavailable controls hold the transaction. Nothing proceeds unchecked.

Integration

Quote, create, authorise.

The whole lifecycle is three calls and a read. Everything else — corridor rules, screening, routing, evidence — happens inside the platform.

API reference 
POST /v1/quotes
  Idempotency-Key: 8f1c…  X-Correlation-ID: 3b90…

  { "send_currency": "CAD", "receive_country": "PH",
    "payout_method": "MOBILE_WALLET", "send_amount_minor": 50000 }

POST /v1/transactions            → 201  quote bound, screening queued
POST /v1/transactions/{id}/authorize
  If-Match: 1                    → 200  released
                                 → 202  held for compliance review

GET  /v1/transactions/{id}       → status timeline through settlement

Bring the licence. We will bring the corridors.

Credentials and corridor enablement are issued during onboarding, scoped to the permissions your entity holds.

Book a demo API reference