Knowledge BaseCustom Payment Module Example: DocData

Custom Payment Module Example: DocData

Back Next

Determining the Right Configuration

There are few things we can configure for each PSP implementation. They are almost all related to the way the user should be redirected to the PSP payment page. DocData has two options to do this: GET or POST. Since POST is the safest we chose to use this method. This means we need to create a hidden form and post this to the payment site. The payment library already supports this by default; we need to configure the payment module in the following way:

ResponseUseXml	False
ResponseUsePost	True
IsFramed True	True
PaymentPage	https://test.tripledeal.com/ps/com.tripledeal.paymentservice.servlets.PaymentService?command=show_payment_cluster

This will make the pre-process pipeline redirect the user the 'paymentframe.aspx' page. This page contains an iframe that points to 'payment.aspx'. It will create a hidden form with all configuration values that have the property 'isRequestParameter' set to true. This form will be posted to the external payment page. In the configuration we also set the values we want to post, for example:

<add name="merchant_name" value="" isRequestParameter="true" />
<add name="merchant_password" value="" isRequestParameter="true" />
<add name="days_pay_period" value="14" isRequestParameter="true" />

These are all static values that DocData needs. But it might also need to post the 'OrderId' and price to this page. In that case we will need to add the configuration values in the code. We can do this by overwriting the 'SetPaymentConfiguration' function. Passed to this function is a list of loaded configuration values called 'configurationToLoad'. Adding configuration values to this collection at this point will add them for the entire payment module. Let's take the example of 'OrderId' and price, we add them like this:

configurationToLoad.Add(new PaymentConfigurationSetting { Value = order.Id.ToString(), Name = "merchant_transaction_id", IsRequestParameter = false });


string price = Math.Round(order.TotalPrice, 2).ToString(CultureInfo.InvariantCulture);
  configurationToLoad.Add(new PaymentConfigurationSetting { Value = price, Name = "price", IsRequestParameter = false });

Now all the right values will be sent to the payment page. These settings will depend on what the PSP requires.

Back Next

Knowledge BaseCustom Payment Module Example: DocData

Sitemap

Installation

Product Versions

Sana Software Links

Sana Commerce does not accept any liability for the content of this website, or for the consequences of any actions taken on the basis of the information provided. The information below should be interpreted as an example. No rights can be derived from this information.

Sana Software – e-Commerce for Microsoft Dynamics

Updated: September 2011