eCommerce transaction is online payments processed from website or mobile application in 3DS model.

EMV® Three-Domain Secure (3-D Secure or 3DS) is an anti-fraud messaging protocol that allows consumers to authenticate themselves with the issuer of their payment card using OTP verification during the payment process.

A one-time password (OTP), also known as one-time pin or dynamic password, is a password that is valid for only one login session or transaction, on a computer system or other digital device. It will be generated and validated by Issuing Party (Bank or any other financial institute).

To implement 3DS transaction from website or mobile application, developer can download the EPG Integration Guide from Download section and refer section 2 for implementation procedure.

MOTO, or Mail Order/Telephone Order, is a type of card-not-present transaction in which services are paid for and delivered via telephone, mail, fax, or internet communication.

No, MoTo transaction is not a secure transaction and all kind of liability will be upon merchant

To implement MOTO transaction, developer can download the EPG Integration Guide from Download section and refer section 5 for implementation procedure.

Pre-Auth payment means the payment amount will be put on hold in payer’s card itself. It will not be debited from payer’s card until Capture is performed for this transaction.

To implement Pre-Auth transaction, merchant need to set “TransactionHint” to “CPT:N” in the Registration API request.

Any un captured amount will be released to payer’s card after certain number of days as per bank policy.

Registrtion API will initiate 3DS transaction process. Merchant pass order details in this API and in response EPG will return a unique TransactionID and PaymentPage URL.

EPG TransactionID is a unique reference number assgined to every tranasction in EPG. Merchant will use this ID throughout the lifecycle of a single transaciton.

EPG Payment Page is secure page for collection of Card details i.e. Card Number, Card Expiry & CVV. Once received in response of Registration API, merchant need to redirect to this URL.

Usually it will be same for all transactions but EPG always recommend not to consider it as constant. Merchant will always receive this in response of Registration API and they should always use the same for redirecting towards EPG Payment Page.

Finalization API will authorize the payment with processing bank and complete the transaction.

After the redirection to Etisalat payment page, payer will enter their card details and submit the payment. After authenticating the card details, EPG will return back the control to ReturnPath URL provided by merchant in Registration API request. During this call back, EPG will post the same TransactionID which was posted during the payment page redirection. Once the control land on this URL, merchant need to initiate Finalization API call.

In case of auto capture (TransactionHint : CPT:Y) payments, there is no other API call required.

If the payment is processed with manual capture (Pre-Auth) option, then Capture API is to be called, when merchat decides to collect the money from payer's card, after Finalization API to capture the amount. Any uncaptured amount will not be settled to merchant account.

If the payment is not settled and to be voided, Reversal API to be used. Developer can download the EPG Integration Guide from Download section and refer section 7 for more details.

In order to initiate online refund request, merchant can use the Refund API. However prior approval from bank is required.

This API can be used to get the current status of payment transaction from EPG.

Developers can download the Query Data manual from Download section in the portal.

Yes, EPG offers plugins to integrate with EPG from shopping platform like Magento, WordPress(WooCommerce) etc.

Developers can download the plugin from Download section on EPG portal.

Developers can download the plugin from Download section on EPG portal. This download media contains the installation procedure document with staging environment credentials.

Yes, EPG allows merchant to customize the payment page in order to have the similar look and feel of their website or mobile application theme.

Request Integration Support team (Merchant-Integration@etisalat.ae) for various option available for customization.

Once the integration and testing is completed, merchant need to share few EPG TransactionID (12 digit number) for both success and failed payments for certification. Once certification process is completed, bank will issue the MID for moving live.

Once the integration and testing is completed, merchant need to share few EPG TransactionID (12 digit number) for both success and failed payments for verification. This verification process is called certification.

Yes, certification required for new integration and any changes in the existing integration. Certification not required for eInvoice services.