e-Commerce Notifier

Confidentiality
All the information in the current document is considered confidential. Using it outside the
context of this consultation or disclosing it to exterior persons is subject to prior approval by
EDPS S.A..
 Revision : 1 [2022/03/14] - EDPS Confidential

Table of Contents
1 Introduction.............................................................................................................................................3
1.2 Setup Requirements....................................................................................................................4
2. Information returned to the merchant....................................................................................................4
Appendix....................................................................................................................................................6
Table 1 : BID Descriptions...............................................................................................................6
Table 2 : Typical Transaction Response Codes................................................................................6
Table 3 : Typical System Error Codes..............................................................................................7

Page 2 of 7
 Revision : 1 [2022/03/14] - EDPS Confidential

1 Introduction
The eCommerce Notifier is an optional feature that ensures that the
transaction data is passed back to the merchant's website when a transaction is
completed, even if the customer closes the browser during the redirection. It
POSTs the data the as soon as the transaction is approved or declined before the
redirection is performed.

Page 3 of 7
 Revision : 1 [2022/03/14] - EDPS Confidential

1.2 Setup Requirements

EDPS e-Commerce platform setup requirements :

 All communication between the merchant's server and the EDPS
eCommerce server must be encrypted with protocol TLS 1.2 or later as per
guidelines set by PCI DSS. Use of the strongest possible ciphers is
recommended. 3DES,MD5,CAMELLIA,AES128, among others, are disabled.

2. Information returned to the merchant

After the transaction the following information will be transferred to the
merchant via HTTPS form post:

Field Description
aa A transaction id that can be used to identify the transaction across
EDPS systems.
amount The transaction amount.
installments Installments for the transaction. 2 numeric digits (01-99).
postdating Postdating for the transaction. 2 numeric digits (01-99).
auth A six-digit transaction approval code, if the transaction was
successful.
bid A three-digit code that identifies the bank that processed the
transaction. *
date The transaction date.
pan Credit card number used to perform this transaction. Due to
security restrictions, all but the last four digits will be masked.
rc Response code returned by the bank for this transaction. The
response data type is an2 (alphanumeric string of length 2) as per
the ISO8583 definition of field 39.
stored Indicates whether this is a new transaction response, or a response
for an already completed transaction that didn't reach the
merchant and was stored by EDPS until the merchant posts another
request with the same transaction id (txnid).
time The transaction time.
txnid The transaction id that was used by the merchant to identify the
transaction.

Page 4 of 7
 Revision : 1 [2022/03/14] - EDPS Confidential

type Card brand (VISA, MASTERCARD, etc).

uid Unique one time transaction/user signature.
userdata Optional user data submitted by merchant.

* See Appendix Table 1 for bid details.

** See Appendix Table 2 for a description of the most common response codes.

The merchant is strongly advised to check the uid signature, txnid and amount in
order to find a match in his/her own list of pending transactions. The values of
these fields must match the ones the merchant had before initiating a new
transaction.

Page 5 of 7
 Revision : 1 [2022/03/14] - EDPS Confidential

Appendix

Table 1 : BID Descriptions

BID BANK NAME

011 NATIONAL BANK OF GREECE
014 ALPHABANK
016 ATTICA BANK
017 PIRAEUS BANK
026 EUROBANK

Table 2 : Typical Transaction Response Codes

This is not an exhaustive list.
Note: The descriptions are not to be shown to the customer, but are for internal
use only.

Response Description
Code
00 Transaction was completed successfully.
05 Generic negative response.
15 Card not supported. This card is not supported by the bank. This
usually occurs for cards that have not been issued by banks in
Greece.
26 Transaction not found
27 Amount error
51 Insufficient funds in cardholder's account
76 Original transaction not found
88 Bank is not responding and transaction attempts result in time-
outs.
91 Service temporarily unavailable.
D* Not authenticated (3DSecure).
Response codes that start with ‘D’.

Page 6 of 7
 Revision : 1 [2022/03/14] - EDPS Confidential

Table 3 : Typical System Error Codes

Error Cause
700 Service Disabled
701 Curl Failed
702 Bad or missing txnID received by transient
703 Bad or missing amount received by transient
704 Bad or missing txMode received by transient
705 Bad or missing txnDate received by transient
706 Bad or missing mid received by EDPS
707 Bad or missing txnid received by EDPS
708 Bad or missing uid received by EDPS
709 Bad or missing amount received by EDPS
710 Bad or missing txn mode received by EDPS
711 Bad or missing txn date received by EDPS
712 EDPS Server error
713 Bad user data received by EDPS
714 Bad installments received by EDPS

Page 7 of 7