Integration Guide for Banks
[ENG] Integration Guide for Bank
[ENG] Integration Guide for Bank
  • General
    • 💰Overview
      • Transfers between digitized entities
        • Option 1. Fast transfer
        • Option 2. Standard transfer (optional)
      • Version history
      • API change log
      • Glossary
    • 🌐Common requirements
    • 👉Basic use case
    • 📅Integration Plan
      • Integration Plan - Business
      • Integration Plan - Technical Team
      • Multisignature
    • ❗Error messages
  • 🛠️API methods
    • Authentification
      • Authorization via JWT
      • Bank authorization
      • JWT format
    • Emlpoyee
      • How to add a user to a role
      • Role management
    • Customer
      • Segments
    • Digital entity
    • Identifiers
    • Transfer
      • Multisignature for transfers
      • [optional] Callbacks
      • Category
    • Limits
    • Reconciliation
    • [optional] Branch
      • Branch access
      • How to add employee to branch
      • Filter by branch
      • Transfers (branches)
      • Branch digital entity
Powered by GitBook
On this page
  1. General

Common requirements

For API users the following recommendations are applicable:

PreviousGlossaryNextBasic use case

Last updated 1 year ago

  1. Each API request contains a counterparty_guid in URL, which you received at .

  2. A session token must be sent for all API requests in the HTTP Authorization Header (see page Authentification for details)

  3. Time is represented in ISO 8601 format with timezone, for example: 2021-09-30T21:43:26+00:00

  4. identifiers used for testing in Stage environment: asset_code: UAH asset_issuer: GDW7XVWZNMOUPSXYBPTEF4PDPNMNEUV3ZFXXZN6CWJ5RFGKQPKSOIDZJ

🌐
onboarding process