All BankVal web services are available on both the main and backup servers at our primary data centre. This configuration is mirrored at our secondary data centre. The two data centres are geographically independent. Using this configuration, the BankVal web service has been available continuously since launch in 2003.
In general:
1 GetABADetails - REST implementation
where:
If aba is valid:-
Sample valid response in xml format :-
<aba>
</aba>
Sample valid response in json format :-
Sample valid response in csv format :-
If routing number is not valid or if an error occurs:-
Error messages :-
INVALID - The supplied ABA Routing Number in not valid.
INVALID - Result Format - Problem, with format field in URI.
ERROR - Invalid User ID/PIN - The User ID or PIN has not been recognised.
ERROR - UserID Expired - Trial user ID has expired.
ERROR - Insecure Connection - An attempt was made to access BankVal's GetABADetails method using insecure HTTP protocol instead of HTTPS.
2 GetABADetails - SOAP
There are two main ways of implementing SOAP, Document Literal and RPC. For help choosing the best solution for your implementation, please contact support@unifiedsoftware.co.uk.
2.1 GetABADetails - SOAP Document Literal
The WSDL file on the primary data centre is at https://www.unifiedservices.co.uk/services/bankvalint/getabadetails.php?wsdl
The WSDL file on the backup data centre is at https://www.unifiedsoftware.co.uk/services/bankvalint/getabadetails.php?wsdl
Parameters |
Description |
|---|---|
userid |
BankVal UK User ID. |
pin |
5 digit PIN. |
aba |
9 digit routing number. |
Field |
Description |
|---|---|
result |
Result string contains on of the following messages:- |
routingnumber |
Routing Number |
bankname |
Name of bank |
bankaddress |
Address of bank - part 1 |
city |
Address of bank - part 2 |
state |
Address of bank - part 3 |
zipcode |
Address of bank - part 4 |
telephone |
Contact telephone number - part 1 |
areacode |
Contact telephone number - part 2 |
fips |
Contact telephone number - part 3 |
timezone |
timezone |
dst |
Daylight saving adjustment |
latitude |
Location |
longitude |
Location |
msa |
|
pmsa |
|
county |
2.2 GetABADetails - SOAP RPC
ReturnMessage = getabadetails(QueryString)
where
QueryString is a " | " delimited string of the format "userID|PIN|ABA Routing Number"
ReturnMessage is either the string "INVALID" OR "ERROR - ..." OR
a 17 field string that is delimited by " | " characters in the format :-
VALID | Routing Number | Bank Name | Bank Address | City | State | ZIP Code | Phone Number | Area Code | FIPS | Time Zone | DST | Latitude | Longitude | MSA | PMSA | County
All possible ReturnMessage values are shown below
17 field string as described above. - This is returned as a " | " delimited character string.
INVALID - The supplied ABA Routing Number in not valid.
ERROR - Invalid User ID/PIN - The User ID or PIN has not been recognised.
ERROR - UserID Expired - Trial user ID has expired.
ERROR - Insecure connection - An attempt was made to access BankVal International's GetABADetails service using insecure HTTP protocol instead of HTTPS.
The WSDL file on the primary data centre is at https://www.unifiedservices.co.uk/BankValinternationalall.wsdl
The WSDL file on the backup data centre is at https://www.unifiedsoftware.co.uk/BankValinternationalall.wsdl
Social Media