Direct Payment Integrator V6 - Online Help
Direct Payment Integrator V6
Questions / Feedback?

FDMSHealthCare Component

Properties   Methods   Events   Configuration Settings   Errors  

The FDMSHealthCare component is an advanced tool used to authorize FSA cards for healthcare transactions in either a retail or e-commerce/moto environment. This component makes authorizing these types of transactions very easy. Supported Industry Types include retail stores, direct marketing (e-commerce and mail order/phone order) and grocery or food stores.

Syntax

nsoftware.InPayDirect.Fdmshealthcare

Remarks

This component connects to the First Data Merchant Services (FDMS) processor, by way of the Datawire VXN transaction transport network. Transactions originating with these components go through Datawire, to the FDMS processor where the transaction is authorized. The result is then returned back through Datawire and received by the component. This component can be integrated into web pages or stand-alone Point Of Sale applications. Because all SSL communications are handled inside the component, any application or web page can be deployed without the need for expensive dedicated SSL servers.

The FDMSHealthCare component makes authorizing healthcare and FSA card transactions 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, you must register and activate your account with Datawire. Datawire will provide you with a MerchantNumber and MerchantTerminalNumber, but you'll need to use the FDMSRegister component to activate the merchant and receive a DatawireId. Once you acquire the DatawireId and receive your transaction URLs through Service Discovery, you may begin to authorize transactions.

To authorize a credit card, set the MerchantNumber and MerchantTerminalNumber with the values supplied by FDMS and Datawire, and the DatawireId with the value retrieved by the FDMSRegister component after activating your merchant account. Set the URL property with one of the URLs you retrieved during Service Discovery.


  FDMSHealthCare.MerchantNumber = "000000999990";                 'Supplied by FDMS/Datawire
  FDMSHealthCare.MerchantTerminalNumber = "555555";         'Supplied by FDMS/Datawire
  FDMSHealthCare.TPPID = "VNT001";                                 'Supplied by FDMS/Datawire
  FDMSHealthCare.VisaIdentifier = "0B34567890123456789";           'Supplied by FDMS/Datawire
  FDMSHealthCare.DatawireId = "0000B47FFFFFFFFFFFFF";                                'Retrieved with the FDMSRegister component.  
  FDMSHealthCare.URL = "https://staging1.datawire.net/sd/"         'Retrieved with the FDMSRegister component.

Then set the Card fields with the customer's cardholder data. Most card readers are capable of reading both Track1 and Track2 data off of a credit card. If both are present and correctly read, you should default to sending Track1 data. If your card reader cannot read the card at all, you may manually enter the credit card number and expiration date. If your IndustryType is set to itDirectMarketing, you may only use manual entry. Do not forget to set the EntryDataSource field, as it is used by the component during authorization to create the proper type of payload.

   FDMSHealthCare.Card.MagneticStripe = "B4662060000000005^FDCS TEST CARD^120410123456789"
	 FDMSHealthCare.Card.EntryDataSource = edsTrack1

Next, set properties that contain details about the transaction. The TransactionNumber should be incremented for every transaction you authorize. The TotalMedicalAmount and TransactionAmount must now be set, along with any optional amounts such as PrescriptionAmount, VisionAmount, DentalAmount, or ClinicAmount. Please note that the TotalMedicalAmount need not equal the TransactionAmount, but it CANNOT be greater than the TransactionAmount. All amounts are set with an implied decimal point (ie: $1.00 is "100"). The IndustryType should also be set at this time, as it will indicate whether this transaction is made for a Retail store, e-commerce, or a grocery store.


  FDMSHealthCare.TransactionNumber = 1
	FDMSHealthCare.PrescriptionAmount = "6000"
  FDMSHealthCare.TotalMedicalAmount = "8000"
  FDMSHealthCare.TransactionAmount = "20200"
  FDMSHealthCare.IndustryType = itRetail

Finally, submit the transaction via the Authorize method.


  FDMSHealthCare.Authorize()
When the component receives a response, the result of the authorization will be available in several Response properties. The DatawireStatus and DatawireReturnCode indicate whether any errors occurred while passing the transaction through the Datawire VXN system. These two properties alone do not indicate a successful transaction, they only tell whether or not there were any problems transporting the authorization request and response through the Datawire system. If the transaction was successfully authorized by FDMS, then the CaptureFlag will be True, and the ApprovalCode will contain an approval code that beings with "AP". (or "AL" for components that support partially-approved/split-tender transactions).

Once an authorization request is approved, the money in the customer's account is blocked and tagged for the merchant. This transaction must go through the Batch Settlement process in order for the blocked money to be transferred to the merchant account. This is done by passing the XML aggregate returned from the GetDetailAggregate method to the FDMSSettle component. Usually, a Batch Settlement of all authorized transactions is done at the end of each business day.

Note that FSA cards may be only partially approved. If the card is authorized for less than the full amount, the ApprovalCode field will begin with "AL" instead of "AP", and the AuthorizedAmount will contain the amount that was actually removed from the card. The customer must then pay the remainder via another means. If the customer cannot pay the remainder or wishes to cancel the transaction, use the ReversePartialAuth method to reverse the authorization.

A fully authorized transaction may also be reversed by using the ReverseFullAuth method. Reversals are used instead of voids for FSA cards because the block on the customer's FSA card is immediately released and funds are quickly made available for use. The customer does not have to wait for the block to expire before he can use his FSA card again.

Property List


The following is the full list of the properties of the component with short descriptions. Click on the links for further details.

ApplicationIdIdentifies the merchant application to the Datawire System.
CardContains the customer's credit card information.
ClinicAmountTotal amount of Clinic or Other qualified medical items for Healthcare auto-substantiation.
CustomerAddressThe customer's billing address.
CustomerZipCustomer's zip code (or postal code if outside of the USA).
DatawireIdIdentifies the merchant to the Datawire System.
DentalAmountTotal amount of Dental items for Healthcare auto-substantiation.
FDMSPlatformSpecifies the FDMS platform that the transactions will be processed on.
IndustryTypeCode which indicates the industry the merchant is engaged in.
MerchantNumberA unique number used to identify the merchant within the FDMS and Datawire systems.
MerchantTerminalNumberUsed to identify a unique terminal within a merchant location.
PrescriptionAmountTotal amount of Prescription/Rx items for Healthcare auto-substantiation.
ProxyA set of properties related to proxy access.
ResponseContains the response to an authorization request.
SSLAcceptServerCertInstructs the component to unconditionally accept the server certificate that matches the supplied certificate.
SSLCertThe certificate to be used during SSL negotiation.
SSLServerCertThe server certificate for the last established connection.
TimeoutA timeout for the component.
TotalMedicalAmountSum total of all medical item amounts.
TPPIDThird Party Processor Identifier assigned by FDMS.
TransactionAmountPurchase amount to be authorized.
TransactionNumberUniquely identifies the transaction.
URLLocation of the Datawire server to which transactions are sent.
VisaIdentifierAdditional merchant identification field used when authorizing Visa transactions.
VisionAmountTotal amount of Vision or Optical items for Healthcare auto-substantiation.

Method List


The following is the full list of the methods of the component with short descriptions. Click on the links for further details.

AuthorizeAuthorizes an FSA card for a Healthcare transaction.
AVSAndCVVOnlyPerforms an AVS/CVV only check using the specified Card data.
BalanceInquiryPerforms a Balance Inquiry Request using the specified Card data.
ConfigSets or retrieves a configuration setting .
GetDetailAggregateReturns an aggregate containing details of this transaction, which is then used for settlement.
InterruptInterrupts the current action.
ResetClears all properties to their default values.
ReverseFullAuthThis performs a reversal of a fully-authorized transaction.
ReversePartialAuthThis performs a reversal of a partially-authorized transaction.

Event List


The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.

ConnectedFired immediately after a connection completes (or fails).
DisconnectedFired when a connection is closed.
ErrorInformation about errors during data delivery.
SSLServerAuthenticationFired after the server presents its certificate to the client.
SSLStatusShows the progress of the secure connection.
StatusShows the progress of the FDMS/Datawire connection.

Configuration Settings


The following is a list of configuration settings for the component with short descriptions. Click on the links for further details.

ClientTimeoutIndicates timeout client application will wait for response.
CurrencyCodeCurrency Code for this transaction.
DebugTraceWhether to enable debug logging.
ACIRequested Authorization Characteristics Indicator (ACI).
TerminalLaneNumberThe Unique Terminal Lane Number.
ConnectionTimeoutSets a separate timeout value for establishing a connection.
FirewallAutoDetectTells the component whether or not to automatically detect and use firewall system settings, if available.
FirewallHostName or IP address of firewall (optional).
FirewallPasswordPassword to be used if authentication is to be used when connecting through the firewall.
FirewallPortThe TCP port for the FirewallHost;.
FirewallTypeDetermines the type of firewall to connect through.
FirewallUserA user name if authentication is to be used connecting through a firewall.
KeepAliveTimeThe inactivity time in milliseconds before a TCP keep-alive packet is sent.
KeepAliveIntervalThe retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received.
LingerWhen set to True, connections are terminated gracefully.
LingerTimeTime in seconds to have the connection linger.
LocalHostThe name of the local host through which connections are initiated or accepted.
LocalPortThe TCP port in the local host where the component binds.
MaxLineLengthThe maximum amount of data to accumulate when no EOL is found.
MaxTransferRateThe transfer rate limit in bytes per second.
RecordLengthThe length of received data records.
TCPKeepAliveDetermines whether or not the keep alive socket option is enabled.
UseIPv6Whether to use IPv6.
TcpNoDelayWhether or not to delay when sending packets.
TLS12SignatureAlgorithmsDefines the allowed TLS 1.2 signature algorithms when UseManagedSecurityAPI is True.
ReuseSSLSessionDetermines if the SSL session is reused.
SSLCipherStrengthThe minimum cipher strength used for bulk encryption.
SSLEnabledProtocolsUsed to enable/disable the supported security protocols.
SSLProviderThe name of the security provider to use.
SSLSecurityFlagsFlags that control certificate verification.
OpenSSLCADirThe path to a directory containing CA certificates.
OpenSSLCAFileName of the file containing the list of CA's trusted by your application.
OpenSSLCipherListA string that controls the ciphers to be used by SSL.
OpenSSLPrngSeedDataThe data to seed the pseudo random number generator (PRNG).
AbsoluteTimeoutDetermines whether timeouts are inactivity timeouts or absolute timeouts.
FirewallDataUsed to send extra data to the firewall.
InBufferSizeThe size in bytes of the incoming queue of the socket.
OutBufferSizeThe size in bytes of the outgoing queue of the socket.
CodePageThe system code page used for Unicode to Multibyte translations.

 
 
Copyright (c) 2017 /n software inc. - All rights reserved.
Build 6.0.6240.0