FDMSOmahaECommerce Component

Properties   Methods   Events   Configuration Settings   Errors  

The FDMSOmahaECommerce component is used to perform Credit card transactions in both Mail Order (Direct Marketing) and eCommerce environments, where the customer is ordering products or services via the telephone or Internet.

Syntax

nsoftware.InPayDirect.Fdmsomahaecommerce

Remarks

This component allows for a connection to the FDMS FDMSOmaha platform via a VPN or PPP (dial-up) connection. This component can be integrated into web pages or stand-alone Point Of Sale applications.

The FDMSOmahaECommerce component makes authorizing Card-Not-Present transactions (where the customer's card is manually entered) very easy by adding an additional layer of abstraction between the programmer and the protocol. There is no need to deal with raw sockets, TLS/SSL handshakes, or data packet formatting. The steps to setting up the component and authorizing a transaction are outlined below:

First, set the merchant and POS specific properties with setup information acquired from your member bank or processor. For instance:

FDMSOmahaECommerce.MerchantNumber = "123456789123456"
FDMSOmahaECommerce.MerchantTerminalID = "XXX01"
FDMSOmahaECommerce.DeviceId = "DID1" // Optional, Merchant-Assigned

Next, set properties that contain details about the transaction. At the minimum, you must set a BatchNumber, TransactionNumber, and TransactionAmount. The TransactionNumber is a sequence number, and should be incremented for each transaction you send. TransactionAmount is the amount of sale formatted with two decimal places. Additionally you can set the DirectMarketingType to specify the transaction type you wish to process.

FDMSOmahaECommerce.BatchNumber = 1
FDMSOmahaECommerce.TransactionNumber = 1
FDMSOmahaECommerce.TransactionAmount = "1.00"
FDMSOmahaECommerce.DirectMarketingType = dmECommerce

Now set the credit card properties, as well as the card holder's address and zip code (the address and zip code will be checked by the FDMS servers to make sure it matches the customer's billing address). Note: card data must be manually entered.

FDMSOmahaECommerce.Card.EntryDataSource = edsManualEntryNoCardReader
FDMSOmahaECommerce.Card.Number = "4444333322221111"
FDMSOmahaECommerce.Card.ExpMonth = 1
FDMSOmahaECommerce.Card.ExpYear = 2013
FDMSOmahaECommerce.CardCVVData = "999"
FDMSOmahaECommerce.CustomerAddress = "8320 Hightower"
FDMSOmahaECommerce.CustomerZip = "85284"  

Finally, submit the transaction by calling Sale or AuthOnly. The following code demonstrates a sale:

FDMSOmahaECommerce.Sale()

When the component receives a response from the FDMS FDMSOmaha servers, the result of the authorization will be displayed in the Response properties. Success indicates whether the transaction was approved. The remaining properties provide additional information about the transaction.

Once a Sale transaction is approved, the DetailAggregate must be added to the FDMSOmahaBatchMgr component to be used when the batch is closed.

For AuthOnly transactions, they must first be captured via the FDMSOmahaDetailRecord component for the funds to be flagged for transfer. Once captured the DetailAggregate can then be added to the FDMSOmahaBatchMgr component to be used when the batch is closed.

After all the wanted detail records have been added to the FDMSOmahaBatchMgr component, the batch can be closed to start the settlement process and initiate the transfer of the funds.