OK here is part of what is in some of the excel sheets that I received, since I am not sure 100% if I am alowed to disclose this information I am changing some of the names.
The notes on the first sheet named General Specifications for API I see the following note:
"All calls to billing API will be made over HTTPS and using client SSL certificates. Refer to document titled 'Install_Use_Certificates_into_Server.pdf' for instructions on installing the certificates on a web server running IIS. Sample code written using C# is provided in the same document."
I am also noticing that this is not Visual Basic it is on C#, my guess it that this is going to be a problem, right?
This is part of the sample Code:
class makeBillingServerCall {
public static void Main() {
string BillingCompnayClientSerialNum = "<BillingCompnay Client Cert Serial #>";
string BillingCompnayServerURL = "
string BillingCompnayACX = "<BillingCompnay ACX>";
string BillingCompnayKEY ="<BillingCompnay Key>";
string BillingCompnayClient = "<Client Access Code>";
string BillingCompnayClientIP = "127.0.0.1";
string mode = "TEST";
string impdata = "<Billing Object with ACX, KEY, Client & Mode>";
string postData = String.Format(BillingCompnayServerURL+"?acx={0}&key={1}&impdata={2}&mode={3}"
, HttpUtility.UrlEncode(BillingCompnayACX)
, HttpUtility.UrlEncode(BillingCompnayKEY)
, HttpUtility.UrlEncode(impdata)
, HttpUtility.UrlEncode(mode));
HttpWebRequest req = (HttpWebRequest) WebRequest.Create(postData);
req.Method = "GET";
req.ContentType = "application/x-
req.KeepAlive = true;
req.AllowAutoRedirect = false;
X509Store store = new X509Store(StoreName.My,
StoreLocation.LocalMachine);
store.Open(OpenFlags.ReadOnly);
X509Certificate2Ccollection certs = store.Certificates.Find(X509FindType.FindBySerialNumber,BillingCompnayClientSerialNum, true);
X509Certificate cert = new X509Certificate();
try {
cert = certs[0]; // or loop through the certificates you find and
determine which one to use
} catch(Exception e) {
// there is a problem
}
req.ClientCertificates.Add(cert);
req.PreAuthenticate = true;
using (Stream reqStream = req.GetRequestStream()) {
reqStream.Write(buffer, 0, buffer.Length);
}
string respString = String.Empty;
try {
using (WebResponse resp = req.GetResponse()) {
Stream responseStream = resp.GetResponseStream();
using (StreamReader responseStreamReader = new
StreamReader(responseStream, new ASCIIEncoding())) {
respString = responseStreamReader.ReadToEnd();
}
}
}
catch(Exception ex) {
// there is a problem
}
Console.WriteLine(String.IsNullOrEmpty(respString) ? null : respString);
Under the Make Payment API I have a list of about 30 input fields such as Customer_FirstName, Field Length=50, Filed Attribute=Required
Under responses I sample filed is ProcStatus, If Empty string then Success, Else contains the exception msg, N-Error processing payment, see PorcStatus for additional messages, E-Error processing payment; see APP_MSG for details, Y-Success; see CONF_MSG for confirmation data; has conf # in html sting - parse to get details.
It see a Sample & Mapping, this is part of what I see
"Data: [
{
PAY: [
{
""SCHED_TYPE"" :""C""
,""SCHED_PAY_AMOUNT"" :""0.50""
,""CARD_NO"" :""111112222222222111111""
,""ACCT_NO_CODE"":""123""
,""CARD_TYPE"" :""Visa""
,""CUST_FIRSTNAME"" :""Test""
,""CUST_LASTNAME"" :""user""
I think I know how the process works and if I had to do this like six million years ago when I was in collage I can probably do it in a heart beat in C++ but I am having a hard time visualizing this happening in Voicemail Pro. I understand what I need to do to capture the information, that should be rather simple although I am having a hard time understanding why the Customer First Name and last name is required and how they heck the billing company expects the customer to punch in their name on the key pad. I am not very sure how do you use the variables when running the script from a VBScript but I think I can figure that one out, however I cannot visualize how I am going to receive the Data and parse it to obtain the confirmation number as an example.
RE
APSS - SME
ACIS - SME