Properties   Methods   Events   Configuration Settings  

The FDMSRegister component is an 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 component is also used to find the appropriate url's to which authorizations and settlements will be posted.

NOTE: What follows is a very short description of the component interfaces. For more information, please consult the help files that come with the respective package.

Remarks

This component 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 components 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. 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.TransactionNumber = "1" 'any unique number will do. FDMSRegister.URL = "https://stagingsupport.datawire.net/staging_expresso/SRS.do" FDMSRegister.Register()

If the registration was successful, the DatawireResponseStatus 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 = 2 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 DatawireResponseStatus will be "OK". The ServiceProviderCount will contain the total number of transaction URLs returned, and the URLs will be listed in the ServiceProvider array property. At this time, you should ping each of those URLs to find the URL with the shortest PingResponseTime.

For i = 0 To FDMSRegister.ServiceProviderCount - 1 FDMSRegister.Ping(FDMSRegister.ServiceProvider[i]) Debug.Print(FDMSRegister.ServiceProvider[i] & " = " & FDMSRegister.PingResponseTime) Next

You may now use the DatawireId and the Service Provider URLs retrieved by this component to submit transactions using the FDMSECOMMERCE, FDMSRETAIL, and FDMSSETTLE components.

Method List

Event List

Configuration Settings