DCM Platform Guide
  • 🌐DCM platform
  • ⚙️Specifics of working with the API
    • 🔐Security stack
    • 🔑Key Generation
    • 🔐Data encrypting
    • 🪃Retry policy
  • 🎨Design guide
  • 🗂️DCM platform's artifacts
  • 🏦Bank
    • 📋Preparing for integration
    • 🏪E-commerce
      • 📦Order and payment
      • 📨Payment message
        • 1️⃣Validation
        • 2️⃣Сallback 1 “Pay-in”
        • 3️⃣Callback 3 “Pay-out”
        • 4️⃣Callback 4 "Credit callback"
      • 🎯Testing
      • 🖇️Merchant Onboarding
      • ⛔Error reference guide
    • 🗃️Alias database
      • 🗝️Adding alias
      • ↕️"Сallback "Alias updated"
      • ☑️Get alias status
    • 💸p2p transfers
      • 📲p2p by phone number
        • ⏺️p2p order (to pay)
        • 🔍Receiver search
        • 🗂️Get receiver's data
        • ⏪Callback "Pay request"
      • 🖇️p2p by deeplink or QR code
        • ⏺️p2p order (to request)
        • Pay request initiation
      • 📨Payment message
        • 1️⃣Validation
        • 2️⃣Сallback “Pay-in”
        • 3️⃣Callback "Pay-out"
    • 💲Gross settlement
      • 1️⃣Callback “Gross_Settlement”
      • 2️⃣Gross_settlement_list
      • 3️⃣Gross_settlement_by_id
      • 4️⃣Gross_settlement_pay
      • 5️⃣Gross_settlement_confirm
      • 6️⃣Gross_settlement_confirm_internal
      • 📧Email notification
    • ✔️Reconciliation
  • 🏢Merchant
    • 🏫DCM platform for Merchants
      • 🔠Integration options
    • 👨‍🏫Preparing for integration
      • ⚙️Working with the API
      • 🔑Key Generation
      • 🖥️Updating interfaces
    • 🏪E-commerce
      • 📦Order
        • 💵Payment through the DCM platform
        • 💳Payment on the Merchant's website
        • 📋Emitters
        • 📬Order status
      • 1️⃣Сallback "Pay-in"
  • 📑Document data
    • 🆕Version history
    • 📃Change log
Powered by GitBook
On this page
  1. Merchant
  2. Preparing for integration

Key Generation

PreviousWorking with the APINextUpdating interfaces

When establishing a business relationship with DCM platform, the Merchant must generate a cryptographic key pair consisting of a private and public key.

  • The private key is used to sign Orders.

  • The public key is provided to DCM platform to verify Orders received from the Merchant.

Key Generation Procedure and Public Key Format Requirements:

  1. Generate the key pair using an appropriate cryptographic tool.

  2. Copy the public key.

  3. Open the key conversion tool at .

  4. Paste the public key into the field labeled "PEM encoded key or certificate".

  5. In the "Key ID" field, specify the "kid" value (one of the private key parameters).

  6. In the "Key algorithm" field, select "RS256".

  7. In the "Key use" field, select "Signature".

  8. Click "Generate".

  9. Copy the data from the "PEM Generation Results" field.

  10. Host the generated public key data at a corresponding jwks_url containing a "keys" object and the information copied from "PEM Generation Results". Example - https://api-hyncmh.develop.dcmapis.com/api/v1/.well-known/jwks.json

  11. Provide the link to DCM platform. Example - https://api-hyncmh.develop.dcmapis.com/api/v1/.well-known/jwks.json

🏢
👨‍🏫
🔑
https://jwkset.com/generate