Changelog

Changes for October 22, 2025

API changes

New splitAmount field in transfer responses

We added a new splitAmount field to transfer-related responses. This field represents the sum of each splitFundingAmount of each record in the transfer, providing better visibility into split funding allocations without requiring additional API calls.

Affected endpoints

• GET /MoneyOut/get-transfers: Added splitAmount to the Summary object in the response
• GET /MoneyOut/get-transfer-detail: Added splitAmount to the Summary object in the response
• GET /MoneyOut/get-transfer-by-id: Added splitAmount to the individual transfer record in the response

What changed

• Added splitAmount as an optional double field in transfer summary and detail responses
• The field will be null if the transfer has no split funding configuration
• The value represents the total of all splitFundingAmount values across all records in the transfer

Example response (GET /MoneyOut/get-transfers)

1
{
2
  "Summary": {
3
    "transferAmount": 935.00,
4
    "splitAmount": 650.22,
5
    "totalNetAmountTransfer": 935.00,
6
    "serviceFees": 30.00
7
  }
8
}

Example response (GET /MoneyOut/get-transfer-by-id)

1
{
2
  "transferAmount": 1004.00,
3
  "splitAmount": 650.22,
4
  "netTransferAmount": 1004.00
5
}

New wallet fields in statistics responses

We added the new inWalletTransactions and inWalletVolume fields to paypoint and organization statistics responses. Only the GET /Statistic/basic/{mode}/{freq}/{level}/{entryId} endpoint is affected.

What changed

• Added inWalletTransactions as an integer field representing the total number of transactions made with wallets in a paypoint or organization
• Added inWalletVolume as a double field representing the total volume of transactions made with wallets in a paypoint or organization

Example response

1
[
2
  {
3
    "statX": "2023-03",
4
    "inTransactions": 150,
5
    "inTransactionsVolume": 25000.5,
6
    "inWalletTransactions": 10,
7
    "inWalletVolume": 1000.5
8
  }
9
]