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
  • Overview
  • Data Object
  • Data Example
  1. Callbacks

Managee Jumio Completed

PreviousCallbacksNextCryptocurrency Transfers

Last updated 1 year ago

Overview

This callback is sent when a customer under management has completed the Jumio KYC process. Once the Jumio process is complete, the account will reviewed by Ibanera's compliance team. Prior to receieving this callback, a manager can prompt a new customer to complete the Jumio process by accessing the .

Data Object

Field
Description

ManageesId

Id of the managee / Customer

ManageeCustomerUsersId

ID of the CustomerUser that completed Jumio. A Customer represents the account entity, whereas a CustomerUser represents a singular user that is linked to a Customer.

Accounts for personal customers will only have one CustomerUser per Customer.

Accounts for Businesses, may have several CustomerUser per Customer, where the Customer represents the Business, and the CustomerUser represents a user that can access the Business account.

DateJumioCompleted

Date of Jumio Completion

Data Example

{
      "Id":"8b3291e8-633a-4aa0-a548-61b479dde915",
      "Type":"MANAGEE_JUMIO_COMPLETED",
      "Data":
            {
                  "ManageesId":14017,
                  "ManageeCustomerUsersId":14040,
                  "DateJumioCompleted":"2024-04-04T15:41:52.15"
            }
}
jumioLink from creating a managee