Ibanera Customer API
Customer Portal
  • Overview
  • Terminology
    • Exchanges of Assets
    • Payees
    • Personal Customers
    • Business Customers
      • Managees
    • Enumerations, Codes and Definitions
      • Source of Funds Types
      • Transfer Purpose Codes Reference
  • Getting Started
    • Access the API
    • API Principal Account
    • Common Response Format
    • First API Call
    • Authentication & Authorization
      • Generating a Time-Based One-Time Password (TOTP) with a Shared Secret
  • API Endpoints
    • Accounts
    • Business Onboarding
    • Cards
    • Crypto Exchanges
    • Foreign Currency Exchange
    • Payees (Beneficiaries)
    • Transfers
    • Transaction Cancellation
    • Managees
    • Information Requests (RFIs)
    • Quick Buy
    • Simulated Testing
  • Callbacks
    • Managee Jumio Completed
    • Cryptocurrency Transfers
    • Exchange Status Updated
    • Fiat Deposit Received
    • Managee Card Approval Updated
    • Managee KYC Updated
    • Transaction Status Updated
    • Information Requests
  • QuickBuy
    • QuickBuy Callback
    • QuickBuy Front End Implementation
    • Validating the Webhook Signature
    • QuickBuy Pro
      • Visual Customization
      • Getting Started / Authentication
      • API Endpoints
        • Create Payment
        • Retrieve Payments
        • Delete Payment
      • Callbacks
        • Payment Captured
        • Cryptocurrency Transferred
Powered by GitBook
On this page
  • Introduction
  • Eligibility and Access Process
  • Functionality of the Customer Management API
  • API Credentials and Security
  1. Getting Started

API Principal Account

PreviousAccess the APINextCommon Response Format

Last updated 1 year ago

Introduction

The Ibanera platform categorizes certain personal or business customers as Customer API Principal users. These users are distinguished by additional privileges that grant them access to the customer management API. This specialized API is a tool for Customer API Principal users to create and administer additional customer users, often referred to as managed customers or managees.


Eligibility and Access Process

To qualify as a Customer API Principal user, a personal or business customer must first complete the KYC (Know Your Customer) or KYB (Know Your Business) verification process. Following this, they can reach out to the Ibanera support team to apply for an elevation to Customer API Principal status.

Functionality of the Customer Management API

The primary function of the customer management API is to offer a streamlined and scalable solution for organizations to effectively handle accounts, cards, and funds distribution among their members, such as employees within a business. As of now, the management of these features is facilitated exclusively through the API, as there is no user interface available for customer management. The API is designed as a collection of RESTful endpoints, secured through bearer token authentication.


API Credentials and Security

Upon gaining API access, a user is provided with specific API credentials, which include:

  • Username

  • Password

  • Shared Secret

The Shared Secret plays a crucial role in the security infrastructure of the account. It is utilized to generate two-factor authentication codes, a mandatory requirement for API interactions. This additional layer of security is instrumental in safeguarding the account holder's information and operations within the API.

Refer to our guide on Generating a Time-Based One-Time Password (TOTP) with a Shared Secret.