Skip to content
Start in the sandboxStart free
All connectors
Ozow logo

Ozow

Accounting, billing & payments

Keep Ozow in step with your orders, invoices and payments without re-keying, with the right person approving what changes.

32 ways to read, 1 way to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Ozow with Nexra

Connected, approved, proven.

The things teams do most with Ozow, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create payment requestApproval by rule
  • List transaction reportRead

Example flow

  1. Ozow · List transaction reportDone
  2. Ozow · Create payment requestNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Ozow.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Ozow
  • Ozow's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Ozow Payments, One and Payouts APIs: transactions, payment requests, refunds, settlements and line items, subscriptions, webhooks and payouts (read); creates payment requests.

Ozow API docs
Source actions
32
Destination actions
1
Data types
24

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Bulk payment jobs1
  • Get bulk payment request jobSource

    Status of a bulk payment-request job by its job reference (seven-day window). Read only.

Legacy refunds2
  • Get refund (Payments API)Source

    Read one Payments API refund by Ozow refund ID.

  • List refunds (Payments API)Source

    Payments API refunds for a date and status, for sites without One API credentials. Read only.

Legacy settlements1
  • List recent settlements (Payments API)Source

    The most recent Payments API settlements (up to 100).

Legacy site settlements1
  • List site settlement lines (Payments API)SourceIncremental

    Transactions settled to the connection's site between two dates.

Legacy transaction refunds1
  • List refunds for a transaction (Payments API)Source

    Payments API refunds against one Ozow transaction ID.

Payment methods1
  • List payment methodsSource

    Payment methods and banks available to the site, with current availability.

Payment request transactions1
  • List transactions for a payment requestSource

    Payment attempts made against one One API payment request.

Payment requests3
  • Create payment requestDestinationProvider duplicate protectionApproval before production

    Create a One API payment request and get the Ozow-hosted payment URL. No money moves until the customer pays.

  • Get payment requestSource

    Read one payment request (One API).

  • List payment requestsSource

    One API payment requests created between two dates.

Payment transactions2
  • Get payment transactionSource

    Read one payment transaction (One API).

  • List payment transactionsSourceIncremental

    One API transactions (payment attempts) created between two dates.

Payout banks1
  • List payout banksSource

    Banks Ozow can pay out to, with their universal branch codes.

Payouts2
  • Get payoutSource

    Read one Payouts API payout and its status. Read only.

  • Search payoutsSource

    Search Payouts API payouts by date range, amount range, real-time clearing or bulk reference. Read only.

Refund notifications1
  • List refund webhook deliveriesSource

    Webhook delivery attempts for one refund, with receiver response.

Refunds2
  • Get refundSource

    Read one refund (One API).

  • List refundsSourceIncremental

    One API refunds requested between two dates. Read only.

Regions1
  • List payment regionsSource

    Regions (countries) where Ozow payments are available (One API).

Settlement line items1
  • List settlement line itemsSource

    Transactions, refunds, payouts, fees and adjustments that make up one settlement, for bank reconciliation.

Settlements2
  • Get settlementSource

    Read one settlement (One API).

  • List settlementsSourceIncremental

    One API settlements paid to your bank account between two dates.

Subscription transactions1
  • List subscription collectionsSource

    Scheduled and completed collections for one recurring subscription.

Subscriptions2
  • Get recurring subscriptionSource

    Read one recurring-payment subscription (One API).

  • List recurring subscriptionsSource

    One API recurring-payment subscriptions for the site, optionally by status.

Transaction notifications1
  • List transaction webhook deliveriesSource

    Webhook delivery attempts for one transaction, with receiver response.

Transaction refunds1
  • List refunds for a transactionSource

    Refunds requested against one One API transaction. Read only.

Transaction report1
  • List transaction reportSource

    Payments API transaction report for the connection's site between two dates, for reconciliation.

Transaction status1
  • Get transaction by Ozow IDSource

    Read one Payments API transaction by the Ozow transaction ID from the redirect or notification.

Transactions1
  • Read transactions by merchant referenceSource

    Read up to ten Ozow attempts associated with an existing merchant reference.

Webhooks2
  • Get webhook subscriptionSource

    Read one webhook subscription (One API).

  • List webhook subscriptionsSource

    One API webhook endpoints and the events they receive.

Access and limits

Authentication
Ozow API key, One API client credentials and Payouts API key
Plans and access
An Ozow merchant site. Payments API operations use the site API key; One API operations need a One API client ID and secret; payout reads need the separate Payouts API key issued after payout approval. Ozow no longer onboards new merchants to the Payments API; new merchants use One API. Payout credentials are only issued to approved merchants.
Test environment
Staging (stagingapi.ozow.com, stagingone.ozow.com, stagingpayoutsapi.ozow.com) has its own credentials, available from Ozow on request. Payins can also be tested in production with isTest.
Rate limits
Ozow does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries.
Pagination
One API lists use limit/offset and links.next; Payments API lookups and the transaction report return one page; payout search pages by index.
Provider events
One API webhooks (transaction.complete, refund.complete) and Payments API notify URLs; subscriptions can be read here. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Intentional exclusions: payment cancellation, transaction processing steps, refund submission and cancellation, subscription creation, collection and cancellation, payout requests, bulk payment requests, unique or static bank-transfer references, bank account verification, webhook create, update, delete and replay, the webhook secret, and Payments API hash-signed payment requests.
  • Payments API refund and settlement reads (/secure/*) are offered as legacy_* operations for sites without One API credentials; they use a bearer token from the Payments API /token endpoint (ApiKey and site code). The One API equivalents remain the primary refund and settlement operations.
  • Read-only additions: regions, refunds and webhook deliveries per transaction, refund webhook deliveries, legacy refunds and settlements, site settlement lines and bulk payment-request job status. Resending notifications, Get Banking Details (returns the deposit account number for a bank-transfer reference) and the webhook secret are not exposed.
  • Ozow has no customer, merchant, store, terminal, dispute, balance, fee or plan API; the API surface is small and these entities are not available.
  • Disputes and chargebacks: Ozow's API has no dispute or chargeback endpoint. Chargeback amounts withheld or released appear only as settlement line items of type chargebackwithheld or chargebackreleased (List settlement line items), so reconcile chargebacks from settlement lines.
  • Account numbers, branch codes, customer names and identity data are not mapped from transactions, refunds, settlements or payouts.
  • The One API, Payouts API and Payments API environment follows the connection's origin (api.ozow.com is production, stagingapi.ozow.com is staging).

Developer reference

  1. Create the Ozow credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Ozow, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Ozow docsAPI referenceOzow docsAuthenticationOzow docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/ozow and the Connections API.