Integrate custom payement gateway to [login to view URL] wordpress group clone.

We need integration of custom payement gateway for wpgroupbuy groupclone script. We have all integration documents availible.

4. AUDIENCE

For the merchants who don’t have their own payment page but uses ISPC Hosted Payment Page (HPP) model of integration.

5. TRANSACTION PART

This is for ISP BIH merchants, who are using Hosted Payment Page redirect method. In this solution card details are entered on ISPC Hosted Payment Page (HPP).

The main characteristics of this way of integration are:

- payment page is on ISPC/ISP BIH side

- card holder data are collected on ISPC/ISP BIH side

- Merchant back-office system can be integrated with NestPay as back-office system - Merchant Center

5.1. “3D PAY HOSTING” MODEL SCHEME

Ecommerce buying steps for “3D Pay Hosting” model are described on below scheme:

Note: payment page is on ISPC/ISP BIH side

“3DPayHosting Model Diagram” represents buying steps, starting from the most left yellow arrow, in one part. The timeline starts on left and ends on right. There are three parties of ecommerce buying process on acquiring side. First one the Merchant system represented on upper part of diagram (blue boxes), Customer in the vertical middle (gray box) and NestPay of ISPC/ISP BIH on lower part (green box).

5.2. BUYING STEPS

“3D Pay Hosting” model on Diagram:

1. Customer fill the shopping carts with products and, by Merchant system “Hidden Parameters POST”, it’s redirected to ISPC/ISP BIH Hosted Payment Page (HPP)

2. Customer enters Payment Parameters (card number, CVC2, expiry date) on secure NestPay Hosted Payment Page (HPP) of ISPC/ISP BIH

3. NestPay sends “Hidden 3D Request” to Issuer bank*

4. Issuer bank sends “Hidden Page” to NestPay with 3-D Secure authentication result*

5. NestPay sends “3D Result” parameters together with authorization message to ISP BIH*

6. ISP BIH sends “Authorization” response to NestPay

7. NestPay sends “Result” to Merchant “Return URL”

* Only for MasterCard, Maestro and VISA cards. For other card brands those steps are skipped.

5.3. INTEGRATION MODEL IN SHORT

In “3D Pay Hosting” model HTTP request should be sent to NestPay “3D Pay Hosting” service link on TEST [url removed, login to view] where 3-D Secure authentication will be checked and authorization message will be made.

Note: for PRODUCTION link is [url removed, login to view]

HTTP requests are described in “[url removed, login to view]” manual:

1. “3D Pay Hosting” model enables processing of 3-D Secure card transactions and authorization:

a. easy to use HTTP Post method is supported for Merchant integration

b. settlement is done automatically by NestPay

2. The customer personal information is not saved by the Merchant, because credit card information is collected on NestPay hosted payment page (HPP) of ISPC/ISP BIH.

3. ISPC/ISP BIH SSL certificate is used so the customer can trust to NestPay hosted payment page

4. Beside mandatory fields the Merchant can POST to NestPay optional data, such as username, user email or user id

The Result of 3-D Secure authentication check and authorization will be in NestPay response to Merchant URL.

Request that follows original authorization request could be sent to NestPay to void, refund or to post-authorize primary transaction. Also check requests to NestPay are also possible. How to generate API following authorization requests is described in “ISPC_Nestpay_Merchant Integration API [url removed, login to view]” manual:

a. Secondary transactions (post-authorization, void, refund)

b. Order status query

c. Order history query

Note: Names for types of authorization and following transaction messages in comparison to other used names:

- preauthorization = preauthorization/authorization with completion

- auto-post-authorization/sale = authorization/ authorization without completion

- post-authorization = completion

- void = reversal/cancellation transaction

- refund = refund

- order status query = authorization check status/completion check status

6. MERCHANT ADMINISTRATION

Merchant administration back-office system is NestPay Merchant Center.

There are two instances of Merchant Center:

- TEST [url removed, login to view]

- PRODUCTION [url removed, login to view]

It is used for:

- administration:

o orders

o transactions

o users

o merchant parameters for connection to NestPay transaction system

- searching:

o downloading needed documents for integration with NestPay transaction system

o bank information

o help

and many other things related to NestPay transaction system. Details can be found in “[url removed, login to view]” manual.

PHP Arquitectura de software

Nº del proyecto: #7131517

Sobre el proyecto