Borica APGW e-Gateway Resources

Dear customers,

We strive to offer ready-to-use solutions for e-commerce merchants, with a view to integrating card payments with a minimum of effort, time and resources. From the beginning of 2023, we offer a plugin for the most famous platform in Bulgaria WordPress, respectively WooCommerce. We are now launching a plugin for another popular platform – Magento. The download and usage of the plugins are free of charge. You can find here the ready-to-use solutions for virtual POS integration to the BORICA payment server:

The software can be used by clients of all financial institutions for which BORICA is processor of virtual payments (FI serviced by BORICA for e-commerce_EV.docx FI serviced by BORICA for e-commerce_BV.docx). In case of questions regarding the installation of the plugins, you can contact us at the following address:
e-comPlugins@borica.bg

APGW supports automatic repeat of transaction in case of SoftDecline.
The amount for TRTYPE=21 should not exceed original amount.
The amount for TRTYPE=22 should match original amount.
Default signing scheme for virtual terminals is MAC_GENERAL The fields included in the signing string for each TRTYPE are listed Below:
NTRTYPEP_SIGN_FIELDS_REQUESTP_SIGN_FIELDS_RESPONCE
1 1TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_IDACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
2 12TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_IDACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
3 21TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_IDACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
4 22TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_IDACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
5 24TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_IDACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
6 90TERMINAL, TRTYPE, ORDER, NONCEACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
Quesitons and Answers
Question: I am getting message "Missing BACKREF parameter, using default. " . What may be the reason?
Answer: APGW returns the response data to a URL, defined for the terminal in APGW database. Check with the bank that this URL is correctly set for the terminal.
Question: I am not getting any response. What may be the reason?
Answer: In case cardholder closes the browser on card details entry screen the transaction remains in state 'Transaction form in progress' for the next 24 hours and response will not be sent. Also check with the bank that BACKREF URL is correctly set for the terminal.
Question: How to match the response to the request?
Answer: Transaction matching can be done using fields TERMINAL, ORDER and NONCE.
Question: I get RC=-17 in the response. What may be the reason?
Answer: APGW return RC=-17 in the following cases:
  • Bad signature caused by malformed request signature string or invalid key
  • TIMESTAMP in request is older than 15 minutes (UTC timezone). Field STATUSMSG contains text "Expired transaction."
  • Transaction is currently in processing
  • Transaction type is not allowed for the terminal
Question: I get RC=-25 in the response. What may be the reason?
Answer: Cardholder has pressed 'Back' button on card details entry screen. The status is not final as cardholder may submit the transaction later on.
Question: I get RC=-19 in the response. What may be the reason?
Answer: APGW return RC=-19 when there was an error with cardholder authentication at the issuer's ACS.