Multitran

Overview

The AgentRecipient API enables multiple transactions to be executed simultaneously through a single JSON request. This API supports processing main transactions along with additional commission fees in a single batch operation.

JSON Structure

Sender Object

{
  "sender": {
    "bankAccount": "-",
    "multiTranParams": [
      // Array of transaction objects
    ]
  }
}

MultiTranParams Parameters

Each transaction object contains the following parameters (all optional):

Parameter	Type	Required	Description
order	string	No	Transaction order sequence (1, 2, 3, ...)
CL	string	No	Sender (outgoing) account number (masked format)
CO	string	No	Recipient (incoming) account number (masked format)
SUM	string	No	Transaction amount (supports template variables)
PUR	string	No	Transaction purpose/description (supports template variables)

Recipient Object

All recipient parameters are optional:

{
  "recipient": {
    "merchantId": "123",      // Optional: Merchant identifier
    "terminalId": "234",      // Optional: Terminal identifier
    "port": "4444",          // Optional: Port number
    "creditType": "UNIVERSAL_CREDIT"  // Optional: Credit type
  }
}

Template Variables

The following variables can be used within the JSON structure:

Transaction Amount Variables

• ${t.requestAmount} - Main transaction amount

• ${t.systemCommissionDownAmount} - Lower commission amount (calculated as % of transaction)

• ${t.systemCommissionUpAmount} - Upper commission amount (calculated as % of transaction)

Contract & Agent Variables

• ${t.id} - Contract ID number

• ${t.date} - Contract date

• ${senderNciId} - Agent NCI identifier

Customer Variables

• ${fio} - Customer full name

• ${r.shortName} - Short name/reference

• ${commission} - Commission percentage

Complete JSON Example

{
  "sender": {
    "bankAccount": "-",
    "multiTranParams": [
      {
        "order": "1",
        "CL": "2989************3444",
        "CO": "4524************3013", 
        "SUM": "${t.requestAmount}",
        "PUR": "Deposit account replenishment according to contract № ${t.id} from ${t.date} agent ${senderNciId}"
      },
      {
        "order": "2", 
        "CL": "2989************3444",
        "CO": "4524************3013",
        "SUM": "${t.systemCommissionDownAmount}",
        "PUR": "Card replenishment for ${fio} ${r.shortName} through agent ${senderNciId}"
      },
      {
        "order": "3",
        "CL": "2989************3444", 
        "CO": "4524************3013",
        "SUM": "${t.systemCommissionUpAmount}",
        "PUR": "Bank commission ${commission}% for card replenishment ${fio} ${r.shortName} through agent ${senderNciId}"
      }
    ]
  },
  "recipient": {
    "merchantId": "123",
    "terminalId": "234",
    "port": "4444", 
    "creditType": "UNIVERSAL_CREDIT"
  }
}

Transaction Types

1. Main Deposit Payment (order: "1")

• Purpose: Deposit account replenishment according to contract

• Amount: ${t.requestAmount} (base transaction amount)

2. Card Top-up (order: "2")

• Purpose: Customer card replenishment through agent

• Amount: ${t.systemCommissionDownAmount} (calculated as % of main amount)

3. Bank Commission (order: "3")

• Purpose: Bank commission for card replenishment service

• Amount: ${t.systemCommissionUpAmount} (calculated as % of main amount)

Commission Calculation

• systemCommissionDownAmount: Additional amount deducted as lower commission (percentage-based)

• systemCommissionUpAmount: Additional amount deducted as upper commission (percentage-based)

• Both commission amounts are calculated as percentages of the main transaction amount (t.requestAmount)

Account Number Format

• CL (Sender Account): Outgoing account number in masked format (e.g., "2989************3444")

• CO (Recipient Account): Incoming account number in masked format (e.g., "4524************3013")

Optional Parameters

All parameters in both sender and recipient objects are optional:

• If multiTranParams is empty, no transactions will be processed

• Missing template variables will remain as placeholders

• Optional recipient fields allow flexible integration with different payment systems

Security Notes

• Account numbers are displayed in masked format for security

• Template variables are populated at runtime

• All transactions are executed in sequential order

• Sensitive data should be handled according to PCI DSS standards

Error Handling

• Invalid template variables will result in processing errors

• Missing required account information may cause transaction failures

• Commission calculations require valid percentage values