Borica APGW e-Gateway

Borica APGW e-Gateway Resources

Dear customers,

Reaching this page, you might probably searching for a solution to accept payments with debit/credit cards in your online shop by integration with BORICAs payment gateway. If your online shop is developed on WordPress, Magento or OpenCart, you could freely use our plugins for theese platforms. No need of code-typing, just plug-and-play with minimum configurations in a few fast and easy steps. Аlthough, if you have any questions, we will be glad to support you at e-comPlugins@borica.bg

WordPress / WooCommerce Plugin(Download latest version. Please note that BORICA Payments plugin v.2.x will be available in WordPress marketplace after 02.12.2024)
Magento 2.x
OpenCart 3.x

Please note that the software is free of any charge and can be used by clients of all financial institutions (FI) 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).

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.

APGW e-Commerce CGI Interface for Virtual Merchants BG

APGW e-Commerce CGI Interface for Virtual Merchants EN

APGW Response Code List

APGW AUTH_STEP_RES Table

ECI (Electronic Commerce Indicator) Table

APGW TEST Public key for validation of response

APGW PRODUCTION Public key for validation of response

Private Key and CSR Generation Tool

Sample PHP code for request signing

Sample PHP code for response signature verification

Sample Java code for digital signature

Sample PHP code (veneliniliev, MAC_GENERAL support)

Sample PHP code for Request (dimitarminchev), MAC_GENERAL support

Sample PHP code for Response (dimitarminchev), MAC_GENERAL support

Sample PHP code (eXtreme-bg, Bogdan Kovachev, MAC_GENERAL support)

Sample PHP code (vanssata)

Sample Perl code (rosen_mitev, MAC_GENERAL support)

Default signing scheme for virtual terminals is MAC_GENERAL The fields included in the signing string for each TRTYPE are listed Below:

N	TRTYPE	P_SIGN_FIELDS_REQUEST	P_SIGN_FIELDS_RESPONCE
1	1	TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_ID	ACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
2	12	TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_ID	ACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
3	21	TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_ID	ACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
4	22	TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_ID	ACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
5	24	TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, TIMESTAMP, NONCE, MERCH_TOKEN_ID	ACTION, RC, APPROVAL, TERMINAL, TRTYPE, AMOUNT, CURRENCY, ORDER, RRN, INT_REF, PARES_STATUS, ECI, TIMESTAMP, NONCE, MERCH_TOKEN_ID
6	90	TERMINAL, TRTYPE, ORDER, NONCE	ACTION, 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.