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
  2. Integration Plan

Integration Plan - Technical Team

PreviousIntegration Plan - BusinessNextMultisignature

Last updated 1 year ago

Steps to integrate - Stage environment

The interaction between the counterparty and DCM processing requires the implementation of certain technical solutions:

#
Who
What
Outcome

1

Bank IT Team

authorization is ready for deployment

2

DCM DevOps

Send a public key for JWT signature check

Bank IT Team has a pubkey

3

DCM Admin

Registers a counterparty in Processing Center with asset_code = ‘UAH’

a counterparty is visible in UI

4

DCM Admin

Asks DCM DevOps to rollout infrastructure components

a Jira task

5

DCM DevOps

Deploys instances for Frontend application and authentication module Ory.

Creates separate hosts backoffice-{alias}-integrate api-{alias}-integrate

hosts are available from internet

6

Bank IT Team

Bank officer has access to secrets

7

Bank officer

Register secrets for key keeper (needed for “Identification” and “Processing” entities)

GET /key returns secrets for 2 users

8

Bank officer

Prepare onboarding data and send it to a DCM administrator:

  • URLs to reach authorization endpoints

  • bank alias

  • email address for the first employee

Data is sent to DCM Admin

9

DCM Admin

[UI] 1. Update counterparty attributes with system URLs2. Create the first employee for the counterparty

The employee is created

10

DCM Admin

Creates identification and processing entities for the counterparty

Identification and processing entities are created

11

Bank officer

Setup password for the first employee.

An employee is logged into UI

12

Bank System operator

[API] Create a request to create identifier

The request is sent to DCM

13

DCM Admin

Identifiers are received

14

Bank officer

Creates secrets for customers

Secrets are ready

15

Bank System operator

16

Bank System operator

Checks have passed

Asset_code = 'UAH'

Implement an authorization to authenticate requests from the DCM Processing Center. The specification is available .

Deploy authorization with pubkey and provide a way to create secrets for a Bank officer There is also an option to choose an approach of

[API] Confirm the created amount and it to an identification entity of the bank

[API] (with accounts)

Customers

[API] Make and other checks to fulfill the integration test scenario

📅
Multisignature for transfers
here
transfer
Create customers
are created
transfer