Integration Guide for Banks
CtrlK
[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
  2. 📅Integration Plan

Multisignature

What if bank signs a payment?

In order to use multisignature for transfers a Counterparty should additionally implement a method POST /sign in Authorization as depicted on the diagram.

All the other steps are the same as for the usual Integration Plan.

The interaction between the Counterparty and DCM processing requires the implementation of certain technical solutions as described in the Integration Plan.

PreviousIntegration Plan - Technical TeamNextError messages

Last updated 1 year ago