Forum OpenACS Q&A: Integration of payment gateway

I am relatively new to openacs ecommerce and would like to know how exactly is the payment gateway integrated with the exommerce module.

I would also appreciate any help regarding the communication of the ecommerce module with the payment gateway.

Thanks in advance.

Overview

API integration is a solution provided by PaySat Inc. to all merchants that have their own orders database, and desire to keep the order page under their identity.

Paysat offers two solutions that vary according to the environment of the merchant site:
 CGI script (platform independent).
 Managed .Net DLL, for integration with .Net web projects.

This document illustrate the .Net integration module

.Net API Integration

To use the .Net DLL API, the following steps must be performed:

a. The merchant will download .Net API version from his Paysat Merchant Profile which will contain 3 files (MerchantApiWebService.dll , MerchantAPIClient.dll & MAPIConfig.xml)
b. The merchant will include those file in his shopping Cart Web Project and add a reference to them so that he can use the classes included in them.
c. Using (MerchAPIClient) class which is included in (MerchantAPIClient) namespace the merchant will create an order object.
d. This object will contain the 5 Functions that will be used.
SingleOrder
AmountOrder
RecurringOrder
SpecialOrder
GetStatus
Merchant will pass the required parameters for each Function, this function return a string which will contain the Response to ordering operation.

AmountOrder

The parameters will be passed to this function are:

( loginName , loginPassword , orderID , merchantID , DomainID , amount , currency , orderDescription , cardType , cardNo , ValidityMonth , validityYear , cardCVV , cardHolderName , countryID , billingState , billingAddress , billilngZipCode , billingEmail , billingPhone , billingCity , buyerIP )

SingleOrder

The parameters will be passed to this function are:

( loginName , loginPassword , orderID , productID , merchantID , DomainID , cardType , cardNo , ValidityMonth , validityYear , cardCVV , cardHolderName , countryID , billingState , billingAddress , billilngZipCode , billingEmail , billingPhone , billingCity , buyerIP )

RecurringOrder

The parameters will be passed to this function are:

( loginName , loginPassword , orderID , productID , merchantID , DomainID , cardType , cardNo , ValidityMonth , validityYear , cardCVV , cardHolderName , countryID , billingState , billingAddress , billilngZipCode , billingEmail , billingPhone , billingCity , buyerIP )

SpecialOrder

The parameters will be passed to this function are:

( loginName , loginPassword , orderID , productID , merchantID , DomainID , cardType , cardNo , ValidityMonth , validityYear , cardCVV , cardHolderName , countryID , billingState , billingAddress , billilngZipCode , billingEmail , billingPhone , billingCity , buyerIP , recurringPeriodInDays )

GetStatus

This function is used to get the order status (Authorized, Captured, etc.)

Merchant can design his Web Application so that he can pass the parameters using a Web Page that contain the required Fields and assign every field to the function desired.

For instance you can use this syntax

private void Recurring()
{
MerchantAPIClient.MerchAPIClient Order_Object = new MerchantAPIClient.MerchAPIClient();
string Return_Text = Order_Object.RecurringOrder(login.Text,password.Text,order.Text,product.Text,merchant.Text,domain.Text,cardtype.Text,cardno.Text,vmonth.Text,vyear.Text,cvv.Text,hname.Text,country.Text,state.Text,address.Text,zipcode.Text,email.Text,phone.Text,city.Text,ip.Text);


}

Where:

1-
Order_Object is the Object was instantiated from (MerchAPIClient) class


2-(login,password,order,product,merchant,domain,cardtype,cardno,vmonth,vyear,cvv,hname,country,state,address,zipcode,email,phone,city,ip) are the text boxes that are used in merchant web form and they will be passed to the Function (Order_Object.RecurringOrder)

Please note that the XML included with API is unique for every merchant, it contains an important data that is essential for Communication between PaySat & the Merchant.