Callback
  • From a market stall to a store

  • -

  • From a store to a retail chain

  • -

  • From retail to manufacturing

Setting up merchant bank terminal in Torgsoft

Volodymyr Vytyshchenko
Volodymyr Vytyshchenko

Trade automation expert at Torgsoft

The merchant determines which settlement account the funds are credited to and through which sole proprietor the payment is fiscalized for cash register purposes. Errors in merchant settings result in funds being credited to the wrong account, declined refunds, and blocked transactions.

This guide concerns the configuration of bank terminal merchants that determine which account funds are credited to and through which sole proprietor cashless payments are processed, so it should be followed with particular care. An incorrect Merchant ID or a mistake when selecting the active account may result in funds being credited to the wrong sole proprietor, refund errors, and discrepancies between the bank statement, the cash register, and the fiscal data. Before making changes, be sure to record the current merchant settings and make sure you understand which account and which sole proprietor should be used for payments and refunds. If in doubt, do not change merchants at random and contact technical support or the bank.

When merchant settings should be checked

  • When connecting a new bank terminal.

  • If several sole proprietors work on one workstation.

  • After changing the sole proprietor, software cash register, or settlement account.

  • When the payment goes through, but the funds are credited to the wrong account.

  • If card refunds are unavailable or end with an error.

How to understand that the issue is related to the merchant

  • Cashless payment is credited to a different sole proprietor than cash payments.

  • The payment goes through, but a different merchant is indicated on the fiscal receipt.

  • Terminal error: card not supported.

  • Error: the refund amount exceeds the payment amount.

  • Program error: fmBankTerminalWS already exists.

  • Communication error: error No. 3 or CANCELLED.

  • Message: Transaction log is full.

  • During a refund: payment RRN not received.

Why transactions go through the wrong merchant

  1. Incorrect merchant for the «Payment» or «Refund» operation. The settings contain a Merchant ID linked to a different account.

  2. Several sole proprietors on one PC. The default settlement account was not switched before the sale.

  3. Automatic merchant detection. The merchant name or number does not match the data in the terminal, so the system selects the first available one.

  4. Loyalty programs (Bonus+). A merchant with a bonus program is used for ordinary cards or for refunds.

  5. Terminal or communication technical failures. Transaction log overflow, unstable RDP, or network issues.

How to check and correct merchant settings

1. Check merchants in Torgsoft

Settings → Parameters → Bank terminal

  • For each operation (Payment, Refund), the correct Merchant ID must be specified separately.

  • The Merchant ID must correspond to the account of the specific sole proprietor.

Rule:
Merchant ID → Settlement account → Sole proprietor — no crossovers.

2. Funds are credited to the wrong place

  • Check which sole proprietor is active on the payment form.

  • Make sure the correct merchant is selected for that sole proprietor.

  • If automatic order import is used (online sales), check on which cash register they are fiscalized.

3. Error «Card not supported»

Typical for PrivatBank terminals with the Bonus+ program.

Action:

  • Use:

    • the main merchant (regular cards);

    • a separate bonus merchant (PrivatBank cards).

  • If the error appears for no apparent reason, temporarily set the merchant number to 0.

4. «The refund amount exceeds the payment amount»

  • Cause: a bonus merchant (actual credited amount ≠ charged amount).

  • Solution: register a second merchant without Bonus+ and process refunds through it.

5. fmBankTerminalWS already exists

  • Completely close and relaunch Torgsoft on this PC.

  • This is a local component initialization error.

6. Error No. 3 / CANCELLED (RDP)

  • Cause: unstable connection channel.

  • Recommended:

    • BPOS1 protocol (with confirmation wait);

    • connecting the terminal via Ethernet (LAN).

7. Transaction log is full

  • On the terminal itself, perform:

    • Shift closing or

    • Z-balance.

8. «Payment RRN not received»

Typical for Verifone terminals (for example, X990).

  • Enter the authorization code from the receipt manually when processing the refund.

  • Cause: the bank library does not transmit the RRN automatically.

How to verify that the merchant is configured correctly

  1. Make a test payment (1–2 UAH).

  2. Check the Merchant ID on the terminal receipt.

  3. Check the bank statement — the funds must be credited to the correct account.

  4. Perform a test refund.

How to avoid mistakes when working with merchants

  • Use a static IP address for the terminal.

  • For Ingenico terminals, create separate merchants for payments and refunds.

  • For the BPOS protocol (refunds):

    • service parameter: 0054//RRN;

    • the «Use service» option must be enabled.

  • Regularly reconcile data using the «Get terminal information» function.

What is important to remember

If the merchant does not match the sole proprietor's account, the funds will be credited incorrectly or the transaction will be blocked.
Checking merchants is a mandatory step whenever there are payment or refund issues.


Програма обліку товару | Торгсофт



Facebook Instagram YouTube Twitter Google News Apple Podcast SounCloud

Add comment

Add comment
Thank you for your feedback! It will be published after being reviewed by a moderator.
Related articles