Home

Introduction

Wiza API is an asynchronous plug in once and get multiple business value tools . Wiza API's allows businesses to reduce the number of efforts required to incorporate multiple payment methods or SMS notifications into their business by integrating with one single API. All the settlements are executed by the payment processors within 24 hours time and the money is credited straight to the merchant account, giving the businesses the ability to plan the next day operations, while the SMS notifications are delivered straight away to your customers being it for OTP notifications or that important order confirmation.

Payment Flow

SMS Flow

Host

The sandbox and production systems are accessed through the same host. To send requests to a production system use production token and to user sandbox system use sandbox token.

The Wiza host name is https://api.wiza.ao

Example:

Payment

• POST https://api.wiza.ao/v1/hosts/payments to start new payment request.

SMS

• POST https://api.wiza.ao/v1/hosts/sms to start new sms notification request.

Authentication

Businesses simplicity and security is our primary goals and that's why https connections and bearer API Token are essential and mandatory through every single connection. Every single business transaction requires a valid header Authorization parameter.

Authorization: <some-token-generated-at-merchant-portal>

Callback

To tighten even more the security in the response callback to your system we included a signature header which is constructed using a Signature Token that only the merchant has access and can be generated at the merchant portal tokens management page. The signature is created (signature token and raw payload body encoded) as per the secure algorithm below and should match the one sent by Wiza.

HexEncode(HMAC-SHA-256(Signature Token, raw HTTP body))

Payments

Request a Payment

curl -XPOST "https://api.wiza.ao/v1/hosts/payments" \
-H "Content-Type: application/json" \
-H "Accept: application/json"
-H "Authorization: eyJhbGciOiJIUzI1NiJ9.eyJtZXJjaGFudF9pZCI6IjE3ZDI5ZDZiLWNhNjUtNDc1Ni1hM2UzLTQzOTY0NjI4MWQ5YSIsInRva2VuX2lkIjoiYjc2MWE3ZDYtMmQxNy00OTczLTg5NGYtZTM4ODVlYWYwNzU1IiwidHlwZSI6InBheW1lbnQiLCJleHAiOjE3MjI0NzAzNDB9.o_3z0dqXrk8f68rPeGieeMNpksSpvwSbLYmKDETa4vs" \
-d '{
        "amount": "123.45",
        "currency": "aoa",
        "reference_id": "123456789",
        "success_url": "https://where-to-redirect-in-case-of-success",
        "failure_url": "https://where-to-redirect-in-case-of-failure",
        "callback_url": "https://send-response-here-when-is-completed"
    }

HTTP Request

POST https://api.wiza.ao/v1/hosts/payments

Headers

Payload

Response

Headers

location: https://hosted.wiza.ao/?id=f3c6ff4c-3f05-4ce6-a253-28b871d682ab&nonce=7079db324f4815ceeda498ebb1261f8205721c9864a52071a738db4f7db89a1d

Example of user process

1. Select payment methods

1. Input phone number

1. Wait while it processes

1. Finished payment (at this stage the system calls back merchant callback)

When user and the payment processor finishes processing Wiza will call back the provided URL at (callback_url) with the payload at the confirm the payment section

Confirm the Payment

curl -XPOST "https://merchant-provided-payment-callback-url" \
-H "Content-Type: application/json" \
-H "Accept: application/json"
-H "signature: aoiufsd98f7sdfkjshdf87d6fsdjhgdu6fd90fdf0988fgd" \
-d '{
        "id": "f3c6ff4c-3f05-4ce6-a253-28b871d682ab",,
        "currency": "aoa",
        "amount": "1000.54",
        "status": "accepted",
        "status_reason": "2000",
        "status_datetime": "2023-03-21T15:28:28.355Z",
        "currency": "aoa",
        "customer": "912123123",
        "reference_id": "123456789",
        "processor": "gpo"
    }

HTTP Request

POST https://merchant-provided-payment-callback-url

Headers

Payload

Response

This callback is a fire and forget. It is the merchant responsability to guarantee the proper endpoint that accepts the callback request

SMS^Beta

Request a SMS

curl -XPOST "https://api.wiza.ao/v1/hosts/sms" \
-H "Content-Type: application/json" \
-H "Accept: application/json"
-H "Authorization: eyJhbGciOiJIUzI1NiJ9.eyJtZXJjaGFudF9pZCI6IjE3ZDI5ZDZiLWNhNjUtNDc1Ni1hM2UzLTQzOTY0NjI4MWQ5YSIsInRva2VuX2lkIjoiYjc2MWE3ZDYtMmQxNy00OTczLTg5NGYtZTM4ODVlYWYwNzU1IiwidHlwZSI6InBheW1lbnQiLCJleHAiOjE3MjI0NzAzNDB9.o_3z0dqXrk8f68rPeGieeMNpksSpvwSbLYmKDETa4vs" \
-d '{
        "numbers": ["912345678", "912456789"]
        "content": "Your awesome message to your awesome customer"
        "callback_url": "https://send-response-here-when-is-completed"
    }

HTTP Request

POST https://api.wiza.ao/v1/hosts/sms

Headers

Payload

Response

{
  "id": "4fe3972e-3d4d-475e-a0ec-477764064641",
  "numbers": ["912345678", "912456789"],
  "sent_sms_count": 0,
  "content": "Your awesome message to your awesome customer",
  "status": "requested",
  "requested_at": "12.01.2025 10:15"
}

Headers

location: https://api.wiza.ao/v1/hosts/sms/4fe3972e-3d4d-475e-a0ec-477764064641

SMS Callback

curl -XPOST "https://merchant-provided-sms-callback-url" \
-H "Content-Type: application/json" \
-H "Accept: application/json"
-H "signature: aoiufsd98f7sdfkjshdf87d6fsdjhgdu6fd90fdf0988fgd" \
-d '{
      "id": "4fe3972e-3d4d-475e-a0ec-477764064641",
      "numbers": ["912345678", "912456789"],
      "content": "Your awesome message to your awesome customer",
      "status": "sent",
      "status_reason": "2000"
    }

HTTP Request

POST https://merchant-provided-sms-callback-url

Headers

Payload

Response

This callback is a fire and forget. It is the merchant responsability to guarantee the proper endpoint that accepts the callback request

Sandbox

Payments

When using Wiza payments API with a sandbox token the payment scenarios uses a very specific phone numbers to simulate the successful and rejection transactions status.

The processes for callback, signature and any other requirement specified previously still apply just like it would when using production token.

SMS

When using Wiza SMS API with a sandbox token the SMS scenarios uses a very specific phone numbers to simulate the successful and rejection notifications status.

The processes for callback, signature and any other requirement specified previously still apply just like it would when using production token.

Status Codes

Payments

Wiza Payments API uses the following status codes:

SMS

Wiza SMS API uses the following status codes: