FDMSRegister Class

Properties   Methods   Events   Config Settings   Errors  

The FDMSRegister class is a tool used to Register and Activate a merchant account with the Datawire VXN. This allows you to send transactions through the Datawire system to the First Data Merchant Services (FDMS) processor. This class is also used to find the appropriate URLs to which authorizations and settlements will be posted.

Syntax

dpaymentssdk.Fdmsregister

Remarks

The FDMSRegister class is a tool used to Register and Activate a merchant account with the Datawire VXN. This class communicates with the Datawire VXN transaction transport network, and allows you to set up your account so that credit card transactions made with the FDMSECommerce, FDMSRetail, and FDMSSettle classs will pass through Datawire and ultimately reach the First Data Merchant Services (FDMS) transaction processor. Before you can charge a single credit card, you must Register and Activate your FDMS account, and then run a ServiceDiscovery to find acceptable URLs, which you will ultimately use to send credit card authorizations.

The first thing you must do is Register your merchant account. First Data Merchant Services will provide you with a MerchantNumber and a MerchantTerminalNumber, which are required for registering with Datawire. If you are registering on the Rapid Connect platform you must also set the GroupId configuration setting. In addition, you will need to set the TransactionNumber with a unique value (the TransactionNumber should be incremented for each transaction you send to the Datawire VXN). The example below also sets the URL to point to the Datawire test server.

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; //FDMSRegister.Config("GroupId=FDMS_Assigned_GroupId"); //Rapid Connect Only FDMSRegister.TransactionNumber = "0000001V002500" 'any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do" FDMSRegister.Register()

If the registration was successful, the DatawireStatus will contain "OK", and the DatawireId will contain the new Id which you must save and send with every subsequent transaction. The PrimaryDiscoveryURL and SecondaryDiscoveryURL properties will also be filled after a successful authorization. These URLs should be saved for later, and used to perform ServiceDiscovery.

After registering, you must immediately Activate the merchant. If you wait too long, your registration will time out, and you will have to contact Datawire to have them reset your account so that you may register again. When activating the merchant, the same properties are required as for the Register method, with the addition of the DatawireId property. Since the call to Register filled the DatawireId property with the correct value, all we need to do now is:

FDMSRegister.TransactionNumber = "0000002V002500" 'any unique number will do; check TransactionNumber property for format FDMSRegister.Activate()

After registering and activating the account, you may now move on to Service Discovery. The Register method will return both a PrimaryDiscoveryURL and a SecondaryDiscoveryURL. Use these URLs with the ServiceDiscovery method to retrieve a list of valid transaction URLs. For instance:

FDMSRegister.ServiceDiscovery("https://staging1.datawire.net/sd")

After a successful ServiceDiscovery the DatawireStatus will be "OK". The discovered URLs will be listed in the ServiceProviders array property. At this time, you should Ping each of these URLs and sort them in order of fastest to slowest response time. You will use the URL with the fastest response time to authorize transactions with FDMSRetail or FDMSECommerce. If the first URL stops responding, you should remove the URL and switch to the next URL in the list. The following example shows how to ping each of the ServiceProviders (you must save and sort the results yourself).

for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

If your list of servers becomes empty, perform ServiceDiscovery and the subsequent steps to re-populate the list of available servers.

You may now use the DatawireId and the Service Provider URLs retrieved by this class to submit transactions using the FDMSECommerce, FDMSRetail, and FDMSSettle classs.

Property List

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

Method List

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

Event List

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

Config Settings

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

ApplicationId Property (FDMSRegister Class)

Identifies the merchant application to the Datawire System.

Syntax

public String getApplicationId();


public void setApplicationId(String applicationId);

Default Value

"NSOFTDIRECTPXML"

Remarks

The Application ID includes the Merchant's application name and version number. This property is used to identify the merchant application within the Datawire system, and may be validated along with the MerchantTerminalNumber and DatawireId as connection credentials.

The default value of this property is assigned to the 4D Payments SDK, and is used for credit card transactions. To provision a merchant on the SVDot Closed Loop Gift Card System, use "IBIZINTGRGIFTXML" instead. You will then be able to use the FDMSGiftCard class to make transactions.

To provision a merchant for the Rapid Connect platform, use "RAPIDCONNECTSRS" instead.

Note, you may be required by FDMS or Datawire to have a new ApplicationId assigned for the software you create with this class.

DatawireId Property (FDMSRegister Class)

Identifies the merchant to the Datawire System.

Syntax

public String getDatawireId();


public void setDatawireId(String datawireId);

Default Value

""

Remarks

The Datawire Id is a unique customer identifier generated by Datawire and returned to the client after successfully registering the merchant (using the FDMSRegister class). This Id (which is sent in all subsequent transactions) allows a transaction, to pass through the Datawire system and be correctly routed to the FDMS Payment processor.

The maximum length for this property is 32 characters.

DatawireReturnCode Property (FDMSRegister Class)

Contains an error code providing more details about the DatawireStatus received.

Syntax

public String getDatawireReturnCode();

Default Value

""

Remarks

When a registration transaction has been successfully processed by the Datawire VXN, the DatawireStatus will be "OK" and the DatawireReturnCode will be "000". The following is a list of possible Datawire return codes:

This property is read-only.

DatawireStatus Property (FDMSRegister Class)

Status of the communication with Datawire.

Syntax

public String getDatawireStatus();

Default Value

""

Remarks

When a registration transaction has been successfully processed by the Datawire VXN, the DatawireStatus will be "OK" and the DatawireReturnCode will be "000". The following is a list of possible Datawire response status codes:

This property is read-only.

FDMSPlatform Property (FDMSRegister Class)

Specifies the FDMS platform that the transactions will be processed on.

Syntax

public int getFDMSPlatform();


public void setFDMSPlatform(int FDMSPlatform);


Enumerated values:
  public final static int fpNorth = 0;
  public final static int fpNashville = 1;
  public final static int fpOmaha = 2;
  public final static int fpRapidConnect = 3;

Default Value

0

Remarks

This property is used to identify the FDMS platform that the transactions will be sent to and processed on. The following table lists the platforms supported by this class.

MerchantNumber Property (FDMSRegister Class)

A unique number used to identify the merchant within the FDMS and Datawire systems.

Syntax

public String getMerchantNumber();


public void setMerchantNumber(String merchantNumber);

Default Value

""

Remarks

This property contains a unique number (typically 12 digits) which is assigned by the signing merchant's bank or processor. This field is used to identify the merchant within the FDMS and Datawire systems, and is used along with the MerchantTerminalNumber and DatawireId as connection credentials.

MerchantTerminalNumber Property (FDMSRegister Class)

Used to identify a unique terminal within a merchant location.

Syntax

public String getMerchantTerminalNumber();


public void setMerchantTerminalNumber(String merchantTerminalNumber);

Default Value

""

Remarks

This property contains a number (typically 6 digits) assigned by FDMS to uniquely identify a terminal within a merchant location, and is used along with the MerchantNumber and DatawireId as connection credentials.

PingResponseTime Property (FDMSRegister Class)

Returned after calling the Ping method.

Syntax

public int getPingResponseTime();

Default Value

0

Remarks

The PingResponseTime contains the total transaction time, in milliseconds, it took for the transaction to reach the Datawire server identified by the URL passed to the Ping method. This time includes only the time the transaction spent between pinged Datawire server and the FDMS host. This property is filled after calling the Ping method. For instance:

FDMSRegister.ServiceDiscovery("https://staging1.datawire.net/sd") for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

Note: This property does not apply to Rapid Connect implementations.

This property is read-only.

PrimaryDiscoveryURL Property (FDMSRegister Class)

URL to use with the ServiceDiscovery method to retrieve a list of service provider URLs.

Syntax

public String getPrimaryDiscoveryURL();

Default Value

""

Remarks

For the North, Nashville, and Omaha platforms: This property is filled after a successful call to the Register method. This URL should be saved, as it will be needed to perform ServiceDiscovery after you Register and Activate your account. Service Discovery should be tried first with the PrimaryDiscoveryURL. If no response is received or you are unable to connect to the primary URL, you should then attempt Service Discovery with the SecondaryDiscoveryURL instead.

This property is read-only and not available at design time.

Proxy Property (FDMSRegister Class)

A set of properties related to proxy access.

Syntax

public Proxy getProxy();


public void setProxy(Proxy proxy);

Remarks

This property contains fields describing the proxy through which the class will attempt to connect.

SecondaryDiscoveryURL Property (FDMSRegister Class)

URL to use with the ServiceDiscovery method to retrieve a list of service provider URLs.

Syntax

public String getSecondaryDiscoveryURL();

Default Value

""

Remarks

For the North, Nashville, and Omaha platforms: This property is filled after a successful call to the Register method. This URL should be saved, as it will be needed to perform ServiceDiscovery after you Register and Activate your account. Service Discovery should be tried first with the PrimaryDiscoveryURL. If no response is received or you are unable to connect to the primary URL, you should then attempt Service Discovery with the SecondaryDiscoveryURL instead.

This property is read-only and not available at design time.

ServiceProviders Property (FDMSRegister Class)

Array containing a list of URLs which may be used to send credit card transactions to.

Syntax

public String[] getServiceProviders();

Default Value

0

Remarks

For the North, Nashville, and Omaha platforms: This property is populated after a call to the ServiceDiscovery method, and contains a list of Service Provider URLs necessary to transport transactions from the application, through the Datawire VXN, then to the FDMS payment processor and back. You should Ping each of these URLs to determine which one has the shortest PingResponseTime, and use that URL for all subsequent credit card transactions.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.TransactionNumber = "0000001V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do"; FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000002V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate(); FDMSRegister.ServiceDiscovery(FDMSRegister.PrimaryDiscoveryURL); for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

For the Rapid Connect platform: This property is populated after a call to the Register method and contains a list of Service Provider URLs necessary to transport transactions from the application, through the Datawire VXN, then to the FDMS payment processor and back.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.Config("GroupId=10001"); FDMSRegister.TransactionNumber = "0000001VRC1234"; //any unique number will do; check TransactionNumber property for format FDMSRegister.ServiceDiscovery("https://prod.dw.us.fdcnet.biz/sd/srsxml.rc"); FDMSRegister.ApplicationId = "RAPIDCONNECTSRS"; FDMSRegister.TransactionNumber = "0000002VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000003VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate();

This property is read-only.

SSLAcceptServerCert Property (FDMSRegister Class)

Instructs the class to unconditionally accept the server certificate that matches the supplied certificate.

Syntax

public Certificate getSSLAcceptServerCert();


public void setSSLAcceptServerCert(Certificate SSLAcceptServerCert);

Remarks

If it finds any issues with the certificate presented by the server, the class will normally terminate the connection with an error.

You may override this behavior by supplying a value for SSLAcceptServerCert. If the certificate supplied in SSLAcceptServerCert is the same as the certificate presented by the server, then the server certificate is accepted unconditionally, and the connection will continue normally.

Please note that this functionality is provided only for cases where you otherwise know that you are communicating with the right server. If used improperly, this property may create a security breach. Use it at your own risk.

SSLCert Property (FDMSRegister Class)

The certificate to be used during SSL negotiation.

Syntax

public Certificate getSSLCert();


public void setSSLCert(Certificate SSLCert);

Remarks

The digital certificate that the class will use during SSL negotiation. Set this property to a valid certificate before starting SSL negotiation. To set a certificate, you may set the Encoded field to the encoded certificate. To select a certificate, use the store and subject fields.

SSLProvider Property (FDMSRegister Class)

This specifies the SSL/TLS implementation to use.

Syntax

public int getSSLProvider();


public void setSSLProvider(int SSLProvider);


Enumerated values:
  public final static int sslpAutomatic = 0;
  public final static int sslpPlatform = 1;
  public final static int sslpInternal = 2;

Default Value

0

Remarks

This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the class will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.

Possible values are:

In most cases using the default value (Automatic) is recommended. The class will select a provider depending on the current platform.

When Automatic is selected the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used.

SSLServerCert Property (FDMSRegister Class)

The server certificate for the last established connection.

Syntax

public Certificate getSSLServerCert();

Remarks

SSLServerCert contains the server certificate for the last established connection.

SSLServerCert is reset every time a new connection is attempted.

This property is read-only.

Timeout Property (FDMSRegister Class)

A timeout for the class.

Syntax

public int getTimeout();


public void setTimeout(int timeout);

Default Value

30

Remarks

If Timeout is set to a positive value, and an operation cannot be completed immediately, the class will return with an error after Timeout seconds.

The default value for Timeout is 30 (seconds).

TransactionNumber Property (FDMSRegister Class)

Uniquely identifies the transaction.

Syntax

public String getTransactionNumber();


public void setTransactionNumber(String transactionNumber);

Default Value

""

Remarks

The TransactionNumber (otherwise known as the Client Reference Number, or ClientRef) uniquely identifies the packet sent by the application to the Datawire system. This parameter stores some unique token of information, and is used to match the response to the initial request sent. For example, the client application could use a static counter that is increased with the each executed request.

For all classs except FDMSGiftCard the maximum length of this property is 14 alphanumeric characters.

The FDMS recommended format is "tttttttVnnnnrrr" where ttttttt is a 7 digit transaction id, V is a constant, and nnn is a 3 digit version number and rrr is a 3 digit revision number. The 6 digit version number is typically static but unique for an application (Example: Version 2.5 = tttttttV002500).

For the Rapid Connect platform, the 6 character version number should be your Project/TPPID value. The entire TransactionNumber must be unique within a 24 hour time period.

The FDMSGiftCard also passes this value to the FDMS Closed Loop Gift Card system as a transaction id, and therefore the following restrictions are enforced: The maximum length is 7 characters. If the first character is an 'X', the remaining characters must be in the range '0' through 'F', indicating a hexadecimal number. Otherwise the FDMS Closed Loop Gift Card system only allows digits in this property.

URL Property (FDMSRegister Class)

Location of the Datawire server to which transactions are sent.

Syntax

public String getURL();


public void setURL(String URL);

Default Value

"https://support.datawire.net/production_expresso/SRS.do"

Remarks

This URL is used by the Register and Activate methods to provision the merchant. The following URLs are available for use:

For the Rapid Connect platform, URL will be populated after a successful ServiceDiscovery request.

Activate Method (Fdmsregister Class)

Activates a merchant account on the Datawire VXN.

Syntax

public void activate();

Remarks

After you have successfully registered, you will still not be able to send transactions using the Datawire VXN until you activate your account. For the security reasons, a merchant is required to activate within a limited time period after receiving a successful registration response. Otherwise, the Datawire VXN will deactivate the account and you will need to restart the registration process again.

North, Nashville, and Omaha:

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.TransactionNumber = "0000001V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do"; FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000002V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate(); FDMSRegister.ServiceDiscovery(FDMSRegister.PrimaryDiscoveryURL); for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

Rapid Connect:

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.Config("GroupId=10001"); FDMSRegister.TransactionNumber = "0000001VRC1234"; //any unique number will do; check TransactionNumber property for format FDMSRegister.ServiceDiscovery("https://prod.dw.us.fdcnet.biz/sd/srsxml.rc"); FDMSRegister.ApplicationId = "RAPIDCONNECTSRS"; FDMSRegister.TransactionNumber = "0000002VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000003VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate();

Config Method (Fdmsregister Class)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every class. It is used to set and retrieve configuration settings for the class.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the class, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

Interrupt Method (Fdmsregister Class)

Interrupts the current action.

Syntax

public void interrupt();

Remarks

This method interrupts any processing that the class is currently executing.

Ping Method (Fdmsregister Class)

Used to find the fastest service provider to use to send credit card transactions.

Syntax

public void ping(String url);

Remarks

The Ping request is used to determine which one of the ServiceProviders URLs is the most efficient to use for transaction transport. The Ping request verifies that the ServiceProviders URLs are reachable and provides the average transaction time cost for each URL, returned in the PingResponseTime property. You should select the fastest ServiceProviders URL to be the active URL that you will use to process all transactions. You should maintain a list of the other ServiceProviders URLs in a queue from fastest to slowest, in the event that the fastest URL becomes unavailable.

A Ping should be sent for each of the ServiceProviders URLs after every 100 authorizations, to ensure that you're still using the fastest URL. A Ping should be run on the ServiceProviders URLs any time the application is first started.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.TransactionNumber = "0000001V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do"; FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000002V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate(); FDMSRegister.ServiceDiscovery(FDMSRegister.PrimaryDiscoveryURL); for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

Note: This functionaly does not apply to Rapid Connect implementations.

Register Method (Fdmsregister Class)

Registers a merchant account on the Datawire VXN.

Syntax

public void register();

Remarks

For the North, Nashville, and Omaha platforms: FDMS will supply you with a MerchantNumber, MerchantTerminalNumber, and Datawire will supply the URL to use to register your merchant. After setting the above properties, call the Register method. The Register method will send the registration request to Datawire, and will continue to poll the Datawire servers until a response is received. This may take several seconds, or even several minutes.

When the registration is complete, the registration response returns the merchant's DatawireId, and the PrimaryDiscoveryURL and SecondaryDiscoveryURL needed to perform ServiceDiscovery. Once received, these parameters must be saved permanently so that they can be reloaded and configured when necessary and are never lost due to power outages.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.TransactionNumber = "0000001V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do"; FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000002V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate(); FDMSRegister.ServiceDiscovery(FDMSRegister.PrimaryDiscoveryURL); for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

For the Rapid Connect platform: ServiceDiscovery will need to be performed first. After a successful ServiceDiscovery call, URL will be populated with the URL required to provision your merchant account. Once TransactionNumber and ApplicationId are set, Register can be called. The Register method will send the registration request to Datawire, and will continue to poll the Datawire servers until a response is received. This may take several seconds, or even several minutes.

When the registration is complete, the registration response returns the merchant's DatawireId, and the PrimaryDiscoveryURL and SecondaryDiscoveryURL needed to process transactions. Once received, these parameters must be saved permanently so that they can be reloaded and configured when necessary and are never lost due to power outages.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.Config("GroupId=10001"); FDMSRegister.TransactionNumber = "0000001VRC1234"; //any unique number will do; check TransactionNumber property for format FDMSRegister.ServiceDiscovery("https://prod.dw.us.fdcnet.biz/sd/srsxml.rc"); FDMSRegister.ApplicationId = "RAPIDCONNECTSRS"; FDMSRegister.TransactionNumber = "0000002VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000003VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate();

Reset Method (Fdmsregister Class)

Clears all properties to their default values.

Syntax

public void reset();

Remarks

This method clears all properties to their default values.

ServiceDiscovery Method (Fdmsregister Class)

Retrieves transaction URLs from Datawire.

Syntax

public void serviceDiscovery(String url);

Remarks

Service Discovery is the means by which you retrieve the actual transaction URLs, used for making credit card authorizations and sending batch settlements.

For the North, Nashville, and Omaha platforms: The response to a successful call to the Register method will return a PrimaryDiscoveryURL and SecondaryDiscoveryURL. After the account has been activated, call the ServiceDiscovery method with either of these URLs as the URL parameter. A successful ServiceDiscovery will provide a list of Service Provider URL's necessary to transport transactions from the application through the Datawire VXN to the FDMS payment processor and back. This list of URL's returned will be stored in the ServiceProviders array property. You should Ping each of these URLs to determine which one has the shortest PingResponseTime, and use that URL for subsequent credit card transactions (note that you should re-Ping each of the URLs received in the ServiceProviders array every 100 transactions, and when first initializing your software).

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.TransactionNumber = "0000001V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do"; FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000002V002500"; //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate(); FDMSRegister.ServiceDiscovery(FDMSRegister.PrimaryDiscoveryURL); for (int i = 0; i < FDMSRegister.ServiceProviders.Length; i++) { FDMSRegister.Ping(FDMSRegister.ServiceProviders[i]); Console.WriteLine(FDMSRegister.ServiceProviders[i] + " = " + FDMSRegister.PingResponseTime); }

For the Rapid Connect platform: ServiceDiscovery will be the first step in provisioning a merchant. FDMS will supply you with a MerchantNumber, MerchantTerminalNumber, and GroupId. After setting these properties, ServiceDiscovery should be called. The default URL, when URL parameter is set to "" (empty string), is "https://prod.dw.us.fdcnet.biz/sd/srsxml.rc". A successful ServiceDiscovery will provide the URL, accessible via URL, necessary to provision a merchant account.

For example:

FDMSRegister.MerchantNumber = "000000999990"; FDMSRegister.MerchantTerminalNumber = "555555"; FDMSRegister.Config("GroupId=10001"); FDMSRegister.TransactionNumber = "0000001VRC1234"; //any unique number will do; check TransactionNumber property for format FDMSRegister.ServiceDiscovery("https://prod.dw.us.fdcnet.biz/sd/srsxml.rc"); FDMSRegister.ApplicationId = "RAPIDCONNECTSRS"; FDMSRegister.TransactionNumber = "0000002VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Register(); FDMSRegister.TransactionNumber = "0000003VRC1234" //any unique number will do; check TransactionNumber property for format FDMSRegister.Activate();

Connected Event (Fdmsregister Class)

This event is fired immediately after a connection completes (or fails).

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void connected(FdmsregisterConnectedEvent e) {}
  ...
}

public class FdmsregisterConnectedEvent {
  public int statusCode;
  public String description;
}

Remarks

If the connection is made normally, StatusCode is 0 and Description is "OK".

If the connection fails, StatusCode has the error code returned by the Transmission Control Protocol (TCP)/IP stack. Description contains a description of this code. The value of StatusCode is equal to the value of the error.

Please refer to the Error Codes section for more information.

DataPacketIn Event (Fdmsregister Class)

Fired when receiving a data packet from the transaction server.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void dataPacketIn(FdmsregisterDataPacketInEvent e) {}
  ...
}

public class FdmsregisterDataPacketInEvent {
  public byte[] dataPacket;
}

Remarks

This event fires when a packet is received. The entire data packet (including all framing and error detection characters) is contained in the parameter "DataPacket". This parameter may be inspected for advanced troubleshooting, or to extract additional response properties beyond the scope of this class.

DataPacketOut Event (Fdmsregister Class)

Fired when sending a data packet to the transaction server.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void dataPacketOut(FdmsregisterDataPacketOutEvent e) {}
  ...
}

public class FdmsregisterDataPacketOutEvent {
  public byte[] dataPacket;
}

Remarks

This event fires right before each data packet is sent. The entire data packet (including all framing and error detection characters) is contained in the parameter "DataPacket". This parameter may be inspected for advanced troubleshooting, or may be modified to support additional features beyond the scope of this class.

Disconnected Event (Fdmsregister Class)

This event is fired when a connection is closed.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void disconnected(FdmsregisterDisconnectedEvent e) {}
  ...
}

public class FdmsregisterDisconnectedEvent {
  public int statusCode;
  public String description;
}

Remarks

If the connection is broken normally, StatusCode is 0 and Description is "OK".

If the connection is broken for any other reason, StatusCode has the error code returned by the Transmission Control Protocol (TCP/IP) subsystem. Description contains a description of this code. The value of StatusCode is equal to the value of the TCP/IP error.

Please refer to the Error Codes section for more information.

Error Event (Fdmsregister Class)

Fired when information is available about errors during data delivery.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void error(FdmsregisterErrorEvent e) {}
  ...
}

public class FdmsregisterErrorEvent {
  public int errorCode;
  public String description;
}

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the class throws an exception.

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

SSLServerAuthentication Event (Fdmsregister Class)

Fired after the server presents its certificate to the client.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void SSLServerAuthentication(FdmsregisterSSLServerAuthenticationEvent e) {}
  ...
}

public class FdmsregisterSSLServerAuthenticationEvent {
  public byte[] certEncoded;
  public String certSubject;
  public String certIssuer;
  public String status;
  public boolean accept;
}

Remarks

During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.

When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.

SSLStatus Event (Fdmsregister Class)

Fired when secure connection progress messages are available.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void SSLStatus(FdmsregisterSSLStatusEvent e) {}
  ...
}

public class FdmsregisterSSLStatusEvent {
  public String message;
}

Remarks

The event is fired for informational and logging purposes only. This event tracks the progress of the connection.

Status Event (Fdmsregister Class)

Shows the progress of the FDMS/Datawire connection.

Syntax

public class DefaultFdmsregisterEventListener implements FdmsregisterEventListener {
  ...
  public void status(FdmsregisterStatusEvent e) {}
  ...
}

public class FdmsregisterStatusEvent {
  public String message;
}

Remarks

The event is fired for informational and logging purposes only. Used to track the progress of the connection.

Certificate Type

This is the digital certificate being used.

Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

Fields

Constructors

public Certificate();

Creates a Certificate instance whose properties can be set. This is useful for use with CERTMGR when generating new certificates.

public Certificate( certificateFile);

Opens CertificateFile and reads out the contents as an X.509 public key.

public Certificate( certificateData);

Parses CertificateData as an X.509 public key.

public Certificate( certStoreType,  store,  storePassword,  subject);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the class will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  store,  storePassword,  subject,  configurationString);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. ConfigurationString is a newline separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CryptoAPI option. The default value is True (the key is persisted). "Thumbprint" - an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to cstUser, cstMachine, cstPublicKeyFile, and cstPFXFile store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations. After the store has been successfully opened, the class will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  store,  storePassword,  encoded);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a file containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the class will load Encoded as an X.509 certificate and search the opened store for a corresponding private key.

public Certificate( certStoreType,  storeBlob,  storePassword,  subject);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. StoreBlob is a string (binary- or Base64-encoded) containing the certificate data. StorePassword is the password used to protect the store. After the store has been successfully opened, the class will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  storeBlob,  storePassword,  subject,  configurationString);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. StoreBlob is a string (binary- or Base64-encoded) containing the certificate data. StorePassword is the password used to protect the store. After the store has been successfully opened, the class will attempt to find the certificate identified by Subject . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN).

public Certificate( certStoreType,  storeBlob,  storePassword,  encoded);

CertStoreType identifies the type of certificate store to use. See StoreType for descriptions of the different certificate stores. Store is a string (binary- or Base64-encoded) containing the certificate store. StorePassword is the password used to protect the store. After the store has been successfully opened, the class will load Encoded as an X.509 certificate and search the opened store for a corresponding private key.

Proxy Type

The proxy the class will connect to.

Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the Server and the AuthScheme.

Fields

Constructors

public Proxy();

public Proxy( server,  port);

public Proxy( server,  port,  user,  password);

Config Settings (Fdmsregister Class)

FDMSRegister Config Settings

TCPClient Config Settings

SSL Config Settings

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw
...
eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w
F0I1XhM+pKj7FjDr+XNj
-----END CERTIFICATE-----
\r \n
-----BEGIN CERTIFICATE-----
MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp
..
d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA
-----END CERTIFICATE-----

Socket Config Settings

Base Config Settings

Trappable Errors (Fdmsregister Class)

FDMSRegister Errors

HTTP Errors

TCPClient Errors

SSL Errors

TCP/IP Errors