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
  • Continue to the next page for information on Callback Types and Formatting

Callbacks

PreviousSimulated TestingNextManagee Jumio Completed

Last updated 1 year ago

Overview

Webhook callbacks can be enabled for customers to receive updated on accounts, transactions and exchanges as they happen. To do so please contact the support team and provide a callback URL you with to use for it. You will be provided with a hash secret for authenticating callbacks.

Callback requests have the following properties:

  • Content type is of type application/json.

  • It will contain webhook-signature header. It is generated by using a SHA256 hashing algorithm on a concatenated string of requestBody + hashSecret. Use the hash secret provided to you to verify the authenticity of the request before processing it.

  • It's content will contain a JSON object with following fields:

    • Id - GUID for the request.

    • Type–Callback type code indicating what type of event has occurred.

    • Data (object): containing details about the event. Details depend on the event type.

  • A 200 HTTP response code is expected. If a different response is returned, the request will be retried with exponential backoff for 2 hours.

Continue to the next page for information on Callback Types and Formatting