Archive
SWS FIUValidateExport Method
Displays a credit and corresponding debit and indicates whether they are balanced and available for non-export via FIU (Financial Integration Utility) for the specified organization, sites and dates.
Parameters
Name | DataType | Is Required |
---|---|---|
EndDate | DateTime | Optional |
Description | The date to end a process. If start date is provided, then it is the end date of a range of dates. Technically, it’s one day beyond the end date. If ‘Null’, it defaults to today’s date. | |
OrgID | Long | Required |
Description | The organization’s ID number. | |
Path | String | Not Used |
Description | Not used for this SWS method as no data is exported. | |
SiteList | Long | Optional |
Description | A collection of limited site details for a specified site. If ‘Null’, will return all sites within the organization. | |
StartDate | DateTime | Required |
Description | The date to start a process. If end date is provided, then it is the start date of a range of dates. This date cannot be greater than today. |
Returned Parameters
Name | DataType |
---|---|
Balanced | Boolean |
Description | “True” if the credit and debit amounts balance, “False” if they do not. |
CreditTotal | Decimal |
Description | The total amount for credits for the non-exported transaction data for the specified organization, sites and dates. |
DebitTotal | Decimal |
Description | The total amount for debits for the non-exported transaction data for the specified organization, sites and dates. |
Example
As with every method we need to pass in credentials. We do this with the LookupUser request object.
We’ll assume you’ve got a web reference, let’s name it SWS, in your Visual Studio project. At this point we need to our objects. We’ll need the standard service object, a FIU_Request request object and a FIUValidateExport_Response response object. We can define and create those like this:
// Create a request and response objects
SWS.WSSoapClient service = new SWS.WSSoapClient();
SWS.FIU_Request request = new SWS.FIU_Request();
SWS.FIUValidateExport_Response response;
Here’s my sample code of the Request object.
// Populate request object
request.OrgID = 123456;
request.SiteList = new long[] { 123456, 456789 };
request.StartDate = DateTime.Today.AddDays(1);
request.EndDate = DateTime.Today;
Finally we can call the method and pass across the login object and the request object to update our previously exported financial information. It’s a good idea to do this in a Try Catch block.
// Call the method that will load the response object
try
{
response = service.FIUValidateExport(user_request,request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You’ll want to take a look at that message returned in that exception so it can be debugged.
For a full list of methods see SWS Methods.
SWS WaiveFee Method
Allows you to waive a fee that has been assess to an account, but that has not yet been paid. This will allow you to remove a fee even if it has gone through nightly processing, but it will count towards the waived count or amount set by the site admin in the site rules.
Parameters
Name | DataType | Is Required |
---|---|---|
Amount | Decimal | Required |
Description | The amount of the fee that will be waived. | |
AssessmentID | Long | Required |
Description | The assessment’s ID number. This can be retrieved using the GetAssessments method. It can also be retrieved using the GetRentalLedger method. | |
OrgID | Long | Required |
Description | The organization’s ID number. | |
Reason | String | Optional |
Description | The reason for waiving the fee. | |
RentalID | Long | Required |
Description | The rental item’s ID number. This is returned when using the MakeReservation method or can be searched for using the SearchBy method. | |
SiteID | Long | Required |
Description | The site’s ID number. This can be found using the GetSiteList method. |
Returned Parameters
Name | DataType |
---|---|
Succeeded | Boolean |
Description | Indicates if the fee waiver was successful (“True”) or not (“False”). |
Example
As with every method we need to pass in credentials. We do this with the LookupUser request object.
We’ll assume you’ve got a web reference, let’s name it SWS, in your Visual Studio project. At this point we need to our objects. We’ll need the standard service object, a WaiveFee request object and a WaiveFee response object. We can define and create those like this:
// Create a request and response objects
SWS.WSSoapClient service = new SWS.WSSoapClient();
SWS.WaiveFee_Request request = new SWS.WaiveFee_Request();
SWS.WaiveFee_Response response;
Here’s my sample code of the Request object.
// WaiveFee Request
request.OrgID = 123456;
request.SiteID = 123546;
request.AssessmentID = 123456;
request.RentalID = 123456;
request.Amount = 55.26m;
request.Reason = "Was charged the fee because of a misunderstanding";
Finally we can call the method and pass across the login object and the request object to waive our fee. It’s a good idea to do this in a Try Catch block.
// Call the method that will load the response object
try
{
response = service.WaiveFee(user_request, request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You’ll want to take a look at that message returned in that exception so it can be debugged.
For a full list of methods see SWS Methods.
SWS ReversePayment Method
Reverses payments associated with a rental item. The given transaction will be reversed entirely, including payment on all rental items and retail items. Use the GetPreReversePayDetails method to determine what items are affected by the reversal and if it can be reversed based on the site rules.
Parameters
Name | DataType | Is Required |
---|---|---|
TranReversalInfo:AccountID | Long | Required |
Description | The account’s ID number. This is returned when you use the CreateNewAccount method or can be retrieved with the SearchBy method. | |
TranReversalInfo:DontCreditCard | Boolean | Optional |
Description | Indicates if the reversal should be sent back to the card (“False”) or if it should be reversed in Store but not have a credit go back to the card (“False”). This is used for externally processed cards, NSFs on debit card transactions and for charge-backs on cards due to disputes. | |
TranReversalInfo:RentalID | Long | Required |
Description | The rental item’s ID number. This is returned when using the MakeReservation method or can be searched for using the SearchBy method. | |
TranReversalInfo:TranDates | TransactionDate | Required |
Description | An array or TransactionDate objects, one for each transaction needing to be reversed. | |
TransactionDate:TranDate | DateTime | Required |
Description | The date of the occurrence for the transaction being reversed. | |
TransactionDate:TranID | Long | Required |
Description | The transaction ID that is being reversed. | |
SiteID | Long | Required |
Description | The site’s ID number. This can be found using the GetSiteList method. |
Returned Parameters
Name | DataType |
---|---|
ErrorMessage | String |
Description | Provides details as to why the reversal of the transaction failed. |
ReversedTran | Long |
Description | The transaction’s ID number. Transaction IDs are system generated for each payment transaction that occurs in the system. |
ReversingTran | Long |
Description | The transaction’s ID number. Transaction IDs are system generated for each payment transaction that occurs in the system. A null or “0” response indicates the transaction failed. |
Example
As with every method we need to pass in credentials. We do this with the LookupUser request object.
We’ll assume you’ve got a web reference, let’s name it SWS, in your Visual Studio project. At this point we need to our objects. We’ll need the standard service object, a ReversePayment request object and a ReversePayment response object. We will also need a TranReversalInfo object and a TransactionDate object. We can define and create those like this:
// Create a request and response objects
SWS.WSSoapClient service = new SWS.WSSoapClient();
SWS.ReversePayment_Request request = new SWS.ReversePayment_Request();
SWS.ReversePayment_Response response;
SWS.TranReversalInfo tranInfo = new SWS.TranReversalInfo();
SWS.TransactionDate tranData = new SWS.TransactionDate();
Here’s my sample code of the Request object.
// Request
tranData.TranID = 123456;
tranData.TranDate = new DateTime(2017, 3, 9);
tranInfo.AccountID = 123456;
tranInfo.RentalID = 123456;
tranInfo.TranDates = new SWS.TransactionDate [] { tranData };
tranInfo.DontCreditCard = false;
request.SiteID = 123456;
request.ReversalDetails =new SWS.TranReversalInfo[] { tranInfo };
Finally we can call the method and pass across the login object and the request object to reverse our payment. It’s a good idea to do this in a Try Catch block.
// Call the method that will load the response object
try
{
response = service.ReversePayment(user_request, request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You’ll want to take a look at that message returned in that exception so it can be debugged.
For a full list of methods see SWS Methods.
SWS VoidTransaction Method
Allows you to void a payment for a rental and/or retail items. A void can only be done the same day as the original transaction and prior to nightly processing.
Parameters
Name | DataType | Is Required |
---|---|---|
AccountID | Long | Required |
Description | The account’s ID number. This is returned when you use the CreateNewAccount method or can be retrieved with the SearchBy method. | |
AccountName | String | Required |
Description | The name on the account. This may differ from the primary contact’s name in some instances, such as a business account or a guardianship account. | |
Amount | Decimal | Required |
Description | The amount of the payment to be voided. | |
Ledger | LedgerType | Optional |
Description | Indicates if the transaction was for rental or retail. Available values:
|
|
OrgID | Long | Required |
Description | The organization’s ID number. | |
SiteID | Long | Required |
Description | The site’s ID number. This can be found using the GetSiteList method. | |
TransactionDate | DateTime | Required |
Description | The date the transaction occurred. For a void transaction it must always have been done current day. | |
TransactionID | Long | Required |
Description | The transaction’s ID number. Transaction IDs are system generated for each payment transaction that occurs in the system. If there is no transaction ID the transaction failed. The transaction ID is returned when any MakePayment method is used. It can also be retrieved using the GetRentalLedger method. |
Returned Parameters
Name | DataType |
---|---|
Successful | Boolean |
Description | Indicates if the transaction was voided successfully (“True”) or not (“False”). |
Example
As with every method we need to pass in credentials. We do this with the LookupUser request object.
We will assume you have a web reference, let us name it SWS, in your Visual Studio project. At this point we need to define our objects. We will need the standard service object, a VoidTransaction request object, and a VoidTransaction response object. We can define and create those like this:
// Create a request and response objects
SWS.WSSoapClient service = new SWS.WSSoapClient();
SWS.VoidTransaction_Request request = new SWS.VoidTransaction_Request();
SWS.VoidTransaction_Response response;
Here is a sample code of the request object:
// VoidTransaction Request
request.OrgID = 123456;
request.SiteID = 123546;
request.AccountID = 123456;
request.AccountName = "Doe, John";
request.Amount = 55.26m;
request.TransactionID = 123546;
request.TransactionDate = new DateTime(2016, 2, 3);
request.Ledger = SWS.LedgerType.Rental;
Finally we can call the method and pass across the login object and the request object to retrieve our requested information. It’s a good idea to do this in a Try Catch block.
// Call the method that will load the response object
try
{
response = service.VoidTransaction(user_request, request);
}
catch (Exception ex)
{
MessageBox.Show(ex.Message);
}
Note that if something goes wrong the service will respond with an exception. You will want to capture the message in the exception so it can be debugged.
For a full list of methods see SWS Methods.