Ozow Hub
POSThttps://one.ozow.com/v1/payments/{id}/transactionsProduction

Start a transaction against an existing payment request by supplying the payment details directly, rather than redirecting the payer to Ozow. Takes a paymentType and the details object matching it.

Authentication

  • OAuth 2.0
    scopespayments

Path parameters

  • id string required

    The unique identifier of the payment.

    example497f6eca-6276-4993-bfeb-53cbbbba6f08

Header parameters

  • X-Correlation-ID string

    Optional correlation id for the request, if not supplied a new one will be generated and passed onto all underlying requests and returned as a header.

  • Idempotency-Key string

    The unique key idempotency keyIdempotency A request is idempotent when sending it twice has the same effect as sending it once. It matters most where a retry after a timeout could otherwise take a payment twice.IETF draft as per the following IETF Draft

Request body

  • paymentType string required

    The payment type being made. To redirectRedirect Sending the payer to the Ozow payment page to complete the payment, and returning them to your site afterwards. The alternative is embedding the checkout in your own page, where the payer never leaves it. to Ozow with a specific institution pre-selected please use the ozowredirect type.

    Except for the ozowredirect payment type, all the other listed options require implementation of a callback url to handle responses and requests for more information to complete processing.

    Payment types such as absapay, card and payshap have pre-requisites that must be met and may not be available for particular payments and amounts.

    values"ozowredirect""absapay""bankdeposit""card""nedbankdirecteft""ozowwallet""payshap""voucher"
  • details one of

Responses

200 OK
  • X-Correlation-ID header

    The correlation id for the request that was processed.

  • transaction Transaction
    Fields of Transaction
    • Fields of TransactionLinks
      • self string uri required

        The unique URI for this resource.

      • refund string uri

        The refund operation for this transaction. This is a POST operation.

      Open TransactionLinks on its own page
    • id string uuid required

      The transaction id of the payment.

    • amount Amount

      The amount that was requested.

      Fields of Amount
      • currency string required

        The ISO 4217ISO 4217 The three-letter currency codes, such as ZAR for the South African rand. Always uppercase.Wikipedia current code.

        min length3max length3
      • value number float required

        The amount in the currency specified.

        min0.01
      Open Amount on its own page
    • merchantReference string required

      The merchant's reference for the transaction.

      max length50
    • siteCode string required

      The merchant site codeSite code The unique code for a site registered under a merchant. A site is a place to transact: a website, or a branch of a store. A merchant can have several, and each transaction names the one it belongs to, so sending the wrong code files the payment against the wrong place. in use for this payment.

      max length50
    • institution string required

      The institution for the transaction.

    • status TransactionStatus required

      The status of the transaction.

      values"Incomplete""Successful""Error""Pending""Refunded"
    • reason string

      Payment status reason.

    • createdDate string date-time required

      The date the transaction was created.

    • completedDate string date-time

      The date the transaction was completed.

    Open Transaction on its own page
  • requiredActionOptions array of RequiredAction
    Fields of RequiredAction
    • action string required

      The action if any that is required next.

      values"redirect""api""websocket"
    • uri string uri

      The URI to redirectRedirect Sending the payer to the Ozow payment page to complete the payment, and returning them to your site afterwards. The alternative is embedding the checkout in your own page, where the payer never leaves it., connect to the WebSocket or make the POST API call if required.

    • inputRequired InputResponse
      Fields of InputResponse
      • transactionId string uuid required

        The transaction id of the payment being processed.

      • paymentStep string required

        The name of the payment step being performed.

      • pageTitle string required

        The title of the page, this will be a user friendly message and can be displayed to the end user.

      • pageInstructions string required

        Instructions for the end user to perform, this will be a user friendly message and can be displayed to the end user.

      • pageActionText string required

        The action type, this could typically be used as the text for a button or link. This will be a user friendly message and can be displayed to the end user.

      • displayType string required

        The display type which indicates what sort of action should be taken. form will require asking the user for input, prompt will require instructing the user to perform an action (e.g. accept a push message) and busy will require asking the user to wait.

        values"form""prompt""busy"
      • If the object is of the form display type the input fields the user would need to complete will be returned in this array.

        Fields of InputField
        Open InputField on its own page
      Open InputResponse on its own page
    Open RequiredAction on its own page