Netwallet API docs
  • Introduction
  • GETTING STARTED
    • Merchant Onboarding
      • Authentication
      • Error Handling
  • PAYMENT PROCESS
    • Overview
      • Pre-requisites
    • Get access token
    • Get account balance
    • Get provider
    • Get supported countries
    • Request payment by collection
    • Request transfer by payout
    • Get transaction status
  • Webhook
    • Get notification on status changed
  • Reference
    • Supported Countries
    • Mobile Money Operator Prefixes
    • Payment Options
    • Currency Limits
    • Transaction Status Reference
    • Security
      • Hashing Algorithms
    • Error code
Powered by GitBook
On this page
  • Authorization
  • API Keys
  1. GETTING STARTED
  2. Merchant Onboarding

Authentication

Some API requests require some authorization to either access data or send fund

Authorization

APIs that return an error: Unauthorized API access requires you to include the secret key in the header.

  1. Collection of funds API requests only require the public key. The secret key should not be included in the header.

  2. Sending of funds API requests require both the public and secret key. The secret key must be included in the header.

API Keys

Applications keys are the unique identifiers of your merchant account when integrating. Service delivery and issue resolution are all dependent on these keys.

When you create a Netwallet account, you are given two kinds of keys:

  1. Primary Key: This is a unique identifier of your merchant account. It is required to make every API request to the platform

  2. Secondary Key: This is a unique identifier of your merchant account. It is complementary to the primary key

The Primary Key has to be included in the API request where authentication is mandatory.

Primary and Secondary keys can be found on the dashboard of your account.

Each account or subaccount has separate key.

PreviousMerchant OnboardingNextError Handling

Last updated 1 year ago