Please note that I have very little to no experience with SOAP programming.

I bought the "West Wind Web Service Proxy" but I do not think that it is going to be any help since it is the WSDL requests that are making the program crash.

Basically they have removed them from the web site and we are suppose to just 'Hard Code' The entire thing.

I spent 2 days getting the SOAP program to run without the WSDL requests.

We also upgraded to Visual Foxpro 9. which I am keeping regardless because all the 'Bugs' in the Editor have been fixed.

Anyway.

Unless I am missing something there is really only 3 things that have to be configured

The URL
The SOAP REQUEST
The XML Page

Please review the letter that I sent them

I have a feeling that their code samples were not updated since they are pointed back to the same URLs.

Dear Sirs:
This is Edward from Realty Information Systems (203-869-8954) SUPPORT@RISSOFT.COM writing.
We have been having problems with the SOAP requests to your web site and would like to request some help.
I have removed the WSDL requests to your web site as per your request
As announced in November (November 4, 2014 email), a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.
You will need to point the system that you use to create transactions to the WSDLs that are attached.
Please let me know if you have any questions or require additional information.
I have reviewed the code samples that have been provided and have attempted the following changes. 
************************************************************
I end up with the following Error:
“Server did not recognize the value of HTTP Header SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
************************************************************

Please see below setting and please suggest a solution.
“SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
this.cServerUrl = "https://ssl.selectpayment.com/PV/PaymentVault.asmx"
XMLPAGE 
<?xml version="1.0" encoding="utf-8"?
<soap:Envelope xmlns:s="http://www.w3.org/2001/XMLSchema"
 mlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:tns="https://ssl.selectpayment.com/PV"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="https://ssl.selectpayment.com/PV"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<soap:Body>
<AuthorizeTransactionWithCustomer xmlns="https://ssl.selectpayment.com/PV" >
	<storeId>208889</storeId>
	<storeKey>8hzrqteh90D0rsualF/0VBLi0yyk</storeKey>
	<customer>
	<EntityId>64433</EntityId>
	<IsCompany>0</IsCompany>
	<CustomerNumber>CARM-2015-3797903-NON-TENANT_DEPOSIT</CustomerNumber>
	<FirstName>NON-TENANT-DEPOSIT</FirstName>
	<LastName>UNKOWN</LastName>
	</customer>
	<createCustomerIfDoesNotExists>1</createCustomerIfDoesNotExists>
	<updateCustomerIfExists>1</updateCustomerIfExists>
	<transaction>
	<EntityId>64433</EntityId>
	<LocationId>934289</LocationId>
	<PaymentOrigin>Mailed_In</PaymentOrigin>
	<AccountType>Checking</AccountType>
	<OperationType>Sale</OperationType>
	<EffectiveDate>2015-03-01T16:00:57</EffectiveDate>
	<TotalAmount>1.00</TotalAmount>
	<BatchNumber/>
	<TransactionNumber>3797903</TransactionNumber>
	<CheckMICRLine>t021101108t1040088576683o 1477</CheckMICRLine>
	<CheckMICRSymbolSet>TOAD ?</CheckMICRSymbolSet>
	<RoutingNumber>021101108</RoutingNumber>
	<AccountNumber>1040088576683</AccountNumber>
	<CheckNumber>1477</CheckNumber>
	<NameOnAccount>NON-TENANT-DEPOSIT</NameOnAccount>
	<NotificationMethod>Merchant_Notify</NotificationMethod>
	<FaceFeeType>Face</FaceFeeType>
	<CheckFrontImageBytes_TiffG4>SUkqAPYlA …..AAIAA=</CheckFrontImageBytes_TiffG4>
	<CheckRearImageBytes_TiffG4>8CQA….. …AAAGQAAIAA=</CheckRearImageBytes_TiffG4>
	</transaction>
</AuthorizeTransactionWithCustomer>
</soap:Body>
</soap:Envelope>

Sounds to me they sent you the WSDL files as attachments. You can copy those to disk and then import them with the WSDL generator. Click the browse button and navigate to the file system to get them in there.

+++ Rick ---

Dear Sirs:
This is Edward from Realty Information Systems (203-869-8954) SUPPORT@RISSOFT.COM writing.
We have been having problems with the SOAP requests to your web site and would like to request some help.
I have removed the WSDL requests to your web site as per your request
As announced in November (November 4, 2014 email), a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.
You will need to point the system that you use to create transactions to the WSDLs that are attached.
Please let me know if you have any questions or require additional information.
I have reviewed the code samples that have been provided and have attempted the following changes. 
************************************************************
I end up with the following Error:
“Server did not recognize the value of HTTP Header SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
************************************************************

Please see below setting and please suggest a solution.
“SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
this.cServerUrl = "https://ssl.selectpayment.com/PV/PaymentVault.asmx"
XMLPAGE 
<?xml version="1.0" encoding="utf-8"?
<soap:Envelope xmlns:s="http://www.w3.org/2001/XMLSchema"
 mlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:tns="https://ssl.selectpayment.com/PV"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="https://ssl.selectpayment.com/PV"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<soap:Body>
<AuthorizeTransactionWithCustomer xmlns="https://ssl.selectpayment.com/PV" >
	<storeId>208889</storeId>
	<storeKey>8hzrqteh90D0rsualF/0VBLi0yyk</storeKey>
	<customer>
	<EntityId>64433</EntityId>
	<IsCompany>0</IsCompany>
	<CustomerNumber>CARM-2015-3797903-NON-TENANT_DEPOSIT</CustomerNumber>
	<FirstName>NON-TENANT-DEPOSIT</FirstName>
	<LastName>UNKOWN</LastName>
	</customer>
	<createCustomerIfDoesNotExists>1</createCustomerIfDoesNotExists>
	<updateCustomerIfExists>1</updateCustomerIfExists>
	<<span class="commands">transaction>
	<EntityId>64433</EntityId>
	<LocationId>934289</LocationId>
	<PaymentOrigin>Mailed_In</PaymentOrigin>
	<AccountType>Checking</AccountType>
	<OperationType>Sale</OperationType>
	<EffectiveDate>2015-03-01T16:00:57</EffectiveDate>
	<TotalAmount>1.00</TotalAmount>
	<BatchNumber/>
	<TransactionNumber>3797903</TransactionNumber>
	<CheckMICRLine>t021101108t1040088576683o 1477</CheckMICRLine>
	<CheckMICRSymbolSet>TOAD ?</CheckMICRSymbolSet>
	<RoutingNumber>021101108</RoutingNumber>
	<AccountNumber>1040088576683</AccountNumber>
	<CheckNumber>1477</CheckNumber>
	<NameOnAccount>NON-TENANT-DEPOSIT</NameOnAccount>
	<NotificationMethod>Merchant_Notify</NotificationMethod>
	<FaceFeeType>Face</FaceFeeType>
	<CheckFrontImageBytes_TiffG4>SUkqAPYlA …..AAIAA=</CheckFrontImageBytes_TiffG4>
	<CheckRearImageBytes_TiffG4>8CQA….. …AAAGQAAIAA=</CheckRearImageBytes_TiffG4>
	</transaction>
</AuthorizeTransactionWithCustomer>
</soap:Body>
</soap:Envelope>

I struggled with this all day yesterday and today and was about to give up hope.

Then I got your latest email and it worked and now there is hope.

You get the official "Your the Man" for today

Dear Sirs:
This is Edward from Realty Information Systems (203-869-8954) SUPPORT@RISSOFT.COM writing.
We have been having problems with the SOAP requests to your web site and would like to request some help.
I have removed the WSDL requests to your web site as per your request
As announced in November (November 4, 2014 email), a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.
You will need to point the system that you use to create transactions to the WSDLs that are attached.
Please let me know if you have any questions or require additional information.
I have reviewed the code samples that have been provided and have attempted the following changes. 
************************************************************
I end up with the following Error:
“Server did not recognize the value of HTTP Header SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
************************************************************

Please see below setting and please suggest a solution.
“SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
this.cServerUrl = "https://ssl.selectpayment.com/PV/PaymentVault.asmx"
XMLPAGE 
<?xml version="1.0" encoding="utf-8"?
<soap:Envelope xmlns:s="http://www.w3.org/2001/XMLSchema"
 mlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:tns="https://ssl.selectpayment.com/PV"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="https://ssl.selectpayment.com/PV"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<soap:Body>
<AuthorizeTransactionWithCustomer xmlns="https://ssl.selectpayment.com/PV" >
	<storeId>208889</storeId>
	<storeKey>8hzrqteh90D0rsualF/0VBLi0yyk</storeKey>
	<customer>
	<EntityId>64433</EntityId>
	<IsCompany>0</IsCompany>
	<CustomerNumber>CARM-2015-3797903-NON-TENANT_DEPOSIT</CustomerNumber>
	<FirstName>NON-TENANT-DEPOSIT</FirstName>
	<LastName>UNKOWN</LastName>
	</customer>
	<createCustomerIfDoesNotExists>1</createCustomerIfDoesNotExists>
	<updateCustomerIfExists>1</updateCustomerIfExists>
	<<span class="commands">transaction>
	<EntityId>64433</EntityId>
	<LocationId>934289</LocationId>
	<PaymentOrigin>Mailed_In</PaymentOrigin>
	<AccountType>Checking</AccountType>
	<OperationType>Sale</OperationType>
	<EffectiveDate>2015-03-01T16:00:57</EffectiveDate>
	<TotalAmount>1.00</TotalAmount>
	<BatchNumber/>
	<TransactionNumber>3797903</TransactionNumber>
	<CheckMICRLine>t021101108t1040088576683o 1477</CheckMICRLine>
	<CheckMICRSymbolSet>TOAD ?</CheckMICRSymbolSet>
	<RoutingNumber>021101108</RoutingNumber>
	<AccountNumber>1040088576683</AccountNumber>
	<CheckNumber>1477</CheckNumber>
	<NameOnAccount>NON-TENANT-DEPOSIT</NameOnAccount>
	<NotificationMethod>Merchant_Notify</NotificationMethod>
	<FaceFeeType>Face</FaceFeeType>
	<CheckFrontImageBytes_TiffG4>SUkqAPYlA …..AAIAA=</CheckFrontImageBytes_TiffG4>
	<CheckRearImageBytes_TiffG4>8CQA….. …AAAGQAAIAA=</CheckRearImageBytes_TiffG4>
	</transaction>
</AuthorizeTransactionWithCustomer>
</soap:Body>
</soap:Envelope>

You know if you're still stuck it might help to spent hour on consulting time with me to get this set up. I can take a look and make sure it'll work the way you expect it to and get you over the hump to start using the service instead of struggling with getting the calls to go through.

Web Services tend to be finicky and it can be tricky at times, especially if you're unfamiliar with the terminology. And to be sure some services just don't work period due to vendor incompatibilities. However seeing this is a .NET service on the other end I'm pretty sure this service will work jsut fine.

http://west-wind.com/contact.aspx

+++ Rick ---

Dear Sirs:
This is Edward from Realty Information Systems (203-869-8954) SUPPORT@RISSOFT.COM writing.
We have been having problems with the SOAP requests to your web site and would like to request some help.
I have removed the WSDL requests to your web site as per your request
As announced in November (November 4, 2014 email), a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.
You will need to point the system that you use to create transactions to the WSDLs that are attached.
Please let me know if you have any questions or require additional information.
I have reviewed the code samples that have been provided and have attempted the following changes. 
************************************************************
I end up with the following Error:
“Server did not recognize the value of HTTP Header SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
************************************************************

Please see below setting and please suggest a solution.
“SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
this.cServerUrl = "https://ssl.selectpayment.com/PV/PaymentVault.asmx"
XMLPAGE 
<?xml version="1.0" encoding="utf-8"?
<soap:Envelope xmlns:s="http://www.w3.org/2001/XMLSchema"
 mlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:tns="https://ssl.selectpayment.com/PV"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="https://ssl.selectpayment.com/PV"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<soap:Body>
<AuthorizeTransactionWithCustomer xmlns="https://ssl.selectpayment.com/PV" >
	<storeId>208889</storeId>
	<storeKey>8hzrqteh90D0rsualF/0VBLi0yyk</storeKey>
	<customer>
	<EntityId>64433</EntityId>
	<IsCompany>0</IsCompany>
	<CustomerNumber>CARM-2015-3797903-NON-TENANT_DEPOSIT</CustomerNumber>
	<FirstName>NON-TENANT-DEPOSIT</FirstName>
	<LastName>UNKOWN</LastName>
	</customer>
	<createCustomerIfDoesNotExists>1</createCustomerIfDoesNotExists>
	<updateCustomerIfExists>1</updateCustomerIfExists>
	<<span class="commands">transaction>
	<EntityId>64433</EntityId>
	<LocationId>934289</LocationId>
	<PaymentOrigin>Mailed_In</PaymentOrigin>
	<AccountType>Checking</AccountType>
	<OperationType>Sale</OperationType>
	<EffectiveDate>2015-03-01T16:00:57</EffectiveDate>
	<TotalAmount>1.00</TotalAmount>
	<BatchNumber/>
	<TransactionNumber>3797903</TransactionNumber>
	<CheckMICRLine>t021101108t1040088576683o 1477</CheckMICRLine>
	<CheckMICRSymbolSet>TOAD ?</CheckMICRSymbolSet>
	<RoutingNumber>021101108</RoutingNumber>
	<AccountNumber>1040088576683</AccountNumber>
	<CheckNumber>1477</CheckNumber>
	<NameOnAccount>NON-TENANT-DEPOSIT</NameOnAccount>
	<NotificationMethod>Merchant_Notify</NotificationMethod>
	<FaceFeeType>Face</FaceFeeType>
	<CheckFrontImageBytes_TiffG4>SUkqAPYlA …..AAIAA=</CheckFrontImageBytes_TiffG4>
	<CheckRearImageBytes_TiffG4>8CQA….. …AAAGQAAIAA=</CheckRearImageBytes_TiffG4>
	</transaction>
</AuthorizeTransactionWithCustomer>
</soap:Body>
</soap:Envelope>

Consulting is sounding better and Better

Please disregard last message

The latest Findings are

FUNCTION AuthorizeTransactionWithCustomer(...... as created by the '.NET Web Service Proxy Generator'

Is displaying the following Error

Method 'TransactionProcessing.TransactionProcessing.AuthorizeTransactionWithCustomer' not found

This Error message was found the documentation and Clearly States that the Fields are not being formated properly

From the .NET Reflector

AuthorizeTransactionWithCustomer(Int64, String, WSCustomer, Boolean, Boolean, WSTransaction, WSOwnerApplication):WSResponceMessage

*Disassembler
[SoapDocumentMethod("https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer", RequestNamespace="https://ssl.selectpayment.com/PV", ResponseNamespace="https://ssl.selectpayment.com/PV", Use=SoapBindingUse.Literal, ParameterStyle=SoapParameterStyle.Wrapped)]
public WSResponseMessage AuthorizeTransactionWithCustomer(long storeId, string storeKey, WSCustomer customer, bool createCustomerIfDoesNotExists, bool updateCustomerIfExists, WSTransaction transaction, WSOwnerApplication ownerApplication)
{
return (WSResponseMessage) base.Invoke("AuthorizeTransactionWithCustomer", new object[] { storeId, storeKey, customer, createCustomerIfDoesNotExists, updateCustomerIfExists, transaction, ownerApplication })[0];
}

THe Code that I am using is

LOCAL mSCSTORID AS Long
LOCAL mSCSORKEY AS String
LOCAL mCUSTOMER_NUMER AS WSCustomer
LOCAL lcText AS WSTransaction
LOCAL mAPP AS WSOwnerApplication

lvResult = loProxy.AuthorizeTransactionWithCustomer(mSCSTORID,mSCSORKEY,mCUSTOMER_NUMER,1,1,lcText,mAPP)

Also

lvResult = loProxy.AuthorizeTransactionWithCustomer(mSCSTORID,mSCSORKEY,mCUSTOMER_NUMER,.T.,.T.,lcText,mAPP)

Please Advise

Dear Sirs:
This is Edward from Realty Information Systems (203-869-8954) SUPPORT@RISSOFT.COM writing.
We have been having problems with the SOAP requests to your web site and would like to request some help.
I have removed the WSDL requests to your web site as per your request
As announced in November (November 4, 2014 email), a security update has been implemented for our Web Services users that eliminates the ability to access EPS Web Service endpoints in a browser.
You will need to point the system that you use to create transactions to the WSDLs that are attached.
Please let me know if you have any questions or require additional information.
I have reviewed the code samples that have been provided and have attempted the following changes. 
************************************************************
I end up with the following Error:
“Server did not recognize the value of HTTP Header SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
************************************************************

Please see below setting and please suggest a solution.
“SOAPAction: https://ssl.selectpayment.com/PV/AuthorizeTransactionWithCustomer”
this.cServerUrl = "https://ssl.selectpayment.com/PV/PaymentVault.asmx"
XMLPAGE 
<?xml version="1.0" encoding="utf-8"?
<soap:Envelope xmlns:s="http://www.w3.org/2001/XMLSchema"
 mlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
 xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
 xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
 xmlns:tns="https://ssl.selectpayment.com/PV"
 xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
 xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
 targetNamespace="https://ssl.selectpayment.com/PV"
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" >
<soap:Body>
<AuthorizeTransactionWithCustomer xmlns="https://ssl.selectpayment.com/PV" >
	<storeId>208889</storeId>
	<storeKey>8hzrqteh90D0rsualF/0VBLi0yyk</storeKey>
	<customer>
	<EntityId>64433</EntityId>
	<IsCompany>0</IsCompany>
	<CustomerNumber>CARM-2015-3797903-NON-TENANT_DEPOSIT</CustomerNumber>
	<FirstName>NON-TENANT-DEPOSIT</FirstName>
	<LastName>UNKOWN</LastName>
	</customer>
	<createCustomerIfDoesNotExists>1</createCustomerIfDoesNotExists>
	<updateCustomerIfExists>1</updateCustomerIfExists>
	<<span class="commands">transaction>
	<EntityId>64433</EntityId>
	<LocationId>934289</LocationId>
	<PaymentOrigin>Mailed_In</PaymentOrigin>
	<AccountType>Checking</AccountType>
	<OperationType>Sale</OperationType>
	<EffectiveDate>2015-03-01T16:00:57</EffectiveDate>
	<TotalAmount>1.00</TotalAmount>
	<BatchNumber/>
	<TransactionNumber>3797903</TransactionNumber>
	<CheckMICRLine>t021101108t1040088576683o 1477</CheckMICRLine>
	<CheckMICRSymbolSet>TOAD ?</CheckMICRSymbolSet>
	<RoutingNumber>021101108</RoutingNumber>
	<AccountNumber>1040088576683</AccountNumber>
	<CheckNumber>1477</CheckNumber>
	<NameOnAccount>NON-TENANT-DEPOSIT</NameOnAccount>
	<NotificationMethod>Merchant_Notify</NotificationMethod>
	<FaceFeeType>Face</FaceFeeType>
	<CheckFrontImageBytes_TiffG4>SUkqAPYlA …..AAIAA=</CheckFrontImageBytes_TiffG4>
	<CheckRearImageBytes_TiffG4>8CQA….. …AAAGQAAIAA=</CheckRearImageBytes_TiffG4>
	</transaction>
</AuthorizeTransactionWithCustomer>
</soap:Body>
</soap:Envelope>