ABIQ API
ABIQ API
User Reference Manual
Version Control
VER. | DATE | BY | PAGE | NOTES |
1.0.0 | January 8, 2022 | IRC | Doc | Initial creation of document |
Table of Contents
3.2.6. Generating IBAN Check Digit
5.1.1. Example of REGISTER Request
6.1.1. REGISTER Response Example
1. Introduction
The document explains to developers how to design and integrate to the Avis Bank ABIQ API host server (fit.software) for the generation of ABIQ license codes (the equvalent of the SWIFT BIC code) and virtual IBAN (Inter Bank Account Numbers) and accounts ranges for a customers and financial institutions.
Note: The ABIQ host server does create the ABIQ license code and virtual IBAN account numbers generated to the customers core banking system. (Fintech Banks and financial industires)
The ABIQ host server accepts and returns messages to the client in the following formats:
· JSON
The exchange of messages is based on certain requirements. If these are not meet the request/response will fail. It is therefore imperative that the message parameter pairs (match) are formatted as required. The parameter elements are defined as follows:
· Mandatory – a mandatory (M) parameter is necessary to ensure the proper processing of the message. Any mandatory parameter not include in a request message will cause the request to be rejected.
· Conditional – a conditional © parameter must be included in some instances. The value and requirement of the parameter is usually conditional on the value passed in another parameter. If the conditional test fails, the request will be rejected.
· Optional – an optional (O) parameter may be included or disregarded at the discretion of the merchant. A transaction request will be processed if an optional parameter is not included in the request message.
Note: When processing response messages returned from the ABIQ API host server, the client server must process responses based on the same definition rules.
The following notations define the data type formats of message parameters:
Notation | Description |
a | Alphabetic character (A-Z; a-z) |
n | Numeric character (0-9) |
ans | Alphabetic, numeric and special characters |
f..7.2 | Variable length currency value with 2 bytes after the decimal point |
3 | Fixed length of 3 bytes |
..18 | A variable length value up to 18 bytes |
bol | Indicates boolen value |
CC | The century of the year. |
DD | Day of month (1 to 31) |
MM | Month of year (1 to 12) |
MMM | Month as alpha (JAN to DEC) |
YY | Year 00 – 99 |
YYYY | Year with CC (19-21) YY (00-99) |
hh | Hour (00 to 23) |
mm | Minute (00 to 59) |
ss | Second (00 to 59) |
The character set used is UTF-8, a compressed version of Unicode that uses a single byte for the ASCII 0-127 characters. A plain ASCII string is therefore a valid UTF-8 string. All field length values in this specification are byte values. The actual number of characters allowed in a field may be less than the given byte values as certain UTF-8 characters are represented using more than more than one byte.
When passing values for message fields certain ASCII characters (example spaces, +, &, /, unprintable characters, etc) must be replaced with the equivalent HTML Unicode (example a space with %20).
For every submitted transaction request, the W3ID Host Server API returns a response message, regardless of the outcome of the transaction process (one for a failed process and one for a successful process).
All text entered in the value pair for a request parameter must conform to the ASCII character codes 32 to 126 (except for code 39). The characters in this ASCII code range are known as printable characters, representing letters, digits, punctuation marks, and a few miscellaneous symbols. Code 32 denotes the space between words, as produced by the large spacebar of a keyboard. All other ASCII codes in the number range from 0 to 31 (known as control characters or non-printing character) are not supported.
2. References
The following documents are supplementary references:
· Description of ABIQ Formats provided courtesy of wikipedia.org
3. ABIQ Formats
This section of the document describes what is ABIQ and how a customer can use the ABIQ Code and virtual IBANS and accounts within the Avis Bank Network.
3.1. What is ABIQ Code
The ABIQ Code is similar in structure to the Swift/BIC code and conforms with the ISO 9362:2022, from year 2022 and is the current version that is valid.
The ISO 9362 is based on the industry standard created by SWIFT around 1975.
The ABIQ Code is similar to the SWIFT code and is 8 or 11 characters, made up of:
· 4 letters: institution code or bank code.
· 2 letters: ISO 3166-1 alpha-2 country code.,
· 2 letters ISIC code (ISIC is a standard classification of economic activities arranged so that entities can be classified according to the activity they carry out.)
· 3 letters or digits: branch code, optional ('XXX' for primary office)
Where an eight-digit code is given, it may be assumed that it refers to the primary (head) office of the business entity
3.2. What is the ABIQ IBAN
The ABIQ IBAN is similar to the standard bank IBAN.
The International Bank Account Number (IBAN) is an internationally agreed system of identifying bank accounts across national borders to facilitate the communication and processing of cross border transactions with a reduced risk of transcription errors. An IBAN uniquely identifies the account of a customer at a financial institution[citation needed]. It was originally adopted by the European Committee for Banking Standards (ECBS) and since 1997 as the international standard ISO 13616 under the International Organization for Standardization (ISO). The current version is ISO 13616:2020, which indicates the Society for Worldwide Interbank Financial Telecommunication (SWIFT) as the formal registrar.
Initially developed to facilitate payments within the European Union, it has been implemented by most European countries and numerous countries in other parts of the world, mainly in the Middle East and the Caribbean. As of May 2020, 77 countries were using the IBAN numbering system.
The IBAN consists of up to 34 alphanumeric characters comprising a country code; two check digits; and a number that includes the domestic bank account number, branch identifier, and potential routing information. The check digits enable a check of the bank account number to confirm its integrity before submitting a transaction.
Note: The ABIQ IBAN format is not registered in the IBAN Registry with Swift.
3.2.1. Structure
The IBAN consists of up to 34 alphanumeric characters, as follows:
· country code using ISO 3166-1 alpha-2 – two letters,
· check digits – two digits, and
· Basic Bank Account Number (BBAN) – up to 30 alphanumeric characters that are country-specific.
The check digits represent the checksum of the bank account number which is used by banking systems to confirm that the number contains no simple errors.
In order to facilitate reading by humans, IBANs are traditionally expressed in groups of four characters separated by spaces, the last group being of variable length as shown in the example below; when transmitted electronically however spaces are omitted.[1]
ABIQ IBAN | |
Human readable |
|
Machine readable | CW05AVIS01000978000002250 |
Permitted IBAN characters are the digits 0 to 9 and the 26 Latin alphabetic characters A to Z.[9] This applies even in countries where these characters are not used in the national language (e.g. Greece).
An IBAN (International Bank Account Number) is a standard format bank account number which shows the country the account is held in, as well as the basic bank account number (BBAN) for the account it’s only 16 - 34 alphanumeric characters long, but your IBAN contains much of the information needed to make sure you can send and receive international payments safely through the Avis Bank Network.
3.2.2. BBAN
The Basic Bank Account Number (BBAN) format is decided by the designated payment authority of each country (Avis Bank Limited). There is no consistency between the formats adopted. Avis Bank Limited has not register its BBAN format with SWIFT and is not obliged to do so. It may adopt IBAN without registration.
The BBAN must be of a fixed and comprise case-insensitive alphanumeric characters. It includes the virtual bank account number, branch identifier, and potential routing information.
3.2.3. Check Digit
The check digits enable the sending bank/ usines (or its customer) to perform a sanity check of the routing destination and account number from a single string of data at the time of data entry. This check is guaranteed to detect any instances where a single character has been omitted, duplicated, mistyped or where two characters have been transposed. Thus routing and account number errors are virtually eliminated
3.2.4. Processing
One of the design aims of the IBAN was to enable as much validation as possible to be done at the point of data entry.[10] In particular, the computer program that accepts an IBAN will be able to validate:
· Country code
· Number of characters in the IBAN correspond to the number specified for the country code
· BBAN format specified for the country code
· Account number, bank code and country code combination is compatible with the check digits
The check digits are calculated using MOD-97-10 as per ISO/IEC 7064:2003 (abbreviated to mod-97 ) which specifies a set of check character systems capable of protecting strings against errors which occur when people copy or key data. In particular, the standard states that the following can be detected:
· All single substitution errors (the substitution of a single character for another, for example 4234 for 1234)
· All or nearly all single (local) transposition errors (the transposition of two single characters, either adjacent or with one character between them, for example 12354 or 12543 for 12345)
· All or nearly all shift errors (shifts of the whole string to the left or right)
· High proportion of double substitution errors (two separate single substitution errors in the same string, for example 7234587 for 1234567)
· High proportion of all other errors
The underlying rules for IBANs is that the account-servicing financial institution should issue an IBAN, as there are a number of areas where different IBANs could be generated from the same account and branch numbers that would satisfy the generic IBAN validation rules. In particular cases where 00 is a valid check digit, 97 will not be a valid check digit, likewise, if 01 is a valid check digit, 98 will not be a valid check digit, similarly with 02 and 99
3.2.5. Validating ABIQ IBAN
An IBAN is validated by converting it into an integer and performing a basic mod-97 operation (as described in ISO 7064) on it. If the IBAN is valid, the remainder equals 1.[Note 1] The algorithm of IBAN validation is as follows:
1. Check that the total IBAN length is correct as per the country. If not, the IBAN is invalid
2. Move the four initial characters to the end of the string
3. Replace each letter in the string with two digits, thereby expanding the string, where A = 10, B = 11, ..., Z = 35
4. Interpret the string as a decimal integer and compute the remainder of that number on division by 97
If the remainder is 1, the check digit test is passed and the IBAN might be valid.
• IBAN: | CW05 AVIS 0100 0978 0000 0225 0 | ||
• Rearrange: | AVIS01000978000002250CW05 | ||
• Convert to integer: | 1031182801000978000002250123205 | ||
• Compute remainder: | 1031182801000978000002250123205 | mod 97 = 1 |
3.2.6. Generating IBAN Check Digit
According to the ECBS "generation of the IBAN shall be the exclusive responsibility of the bank/branch servicing the account".[ The ECBS document replicates part of the ISO/IEC 7064:2003 standard as a method for generating check digits in the range 02 to 98. Check digits in the ranges 00 to 96, 01 to 97, and 03 to 99 will also provide validation of an IBAN, but the standard is silent as to whether or not these ranges may be used.
The preferred algorithm is:
1. Check that the total IBAN length is correct as per the Avis Bank format. If not, the IBAN is invalid.
2. Replace the two check digits by 00 (e.g., CW00 for the UK).
3. Move the four initial characters to the end of the string.
4. Replace the letters in the string with digits, expanding the string as necessary, such that A or a = 10, B or b = 11, and Z or z = 35. Each alphabetic character is therefore replaced by 2 digits
5. Convert the string to an integer (i.e. ignore leading zeroes).
6. Calculate mod-97 of the new number, which results in the remainder.
7. Subtract the remainder from 98 and use the result for the two check digits. If the result is a single-digit number, pad it with a leading 0 to make a two-digit number.
Business entities who have first registered for an ABIQ Code can order ABIQ virtual accounts and IBANs.
4. API Functions
This section explains the operations (functions) that are to be supported by the fit.INTELECT ABIQ Host Server API.
Each function tells the fit.INTELECT ABIQ Host Server API to perform a specific type of operation. With the fit.INTELECT ABIQ Host Server API each of the functions have their own set of specific parameters that must be passed in the request message. The fit.INTELECT ABIQ Host Server API will return a set of parameters for each of the function requests.
FUNCTION | METHOD | DESCRIPTION |
REGISTER | POST | Allows a business entity (customer) to register and receive an ABIQ Code.
Note: A business entity (customer) must first register and receive an ABIQ Code before they can request an ABIQ IBAN or Account Number |
ORDER | POST | Allows a customer (business entity) who has been registered with an ABIQ Code to order a range of virtual ABIQ IBANs and virtual account numbers |
SEARCH | POST | Allows a business entity to to search the Avis Bank ABIQ Registry for details of a particular ABIQ Code. |
5. Request Messages
This section of the document explains each of the parameters in the API that are available to a client when sending a transaction request to the ABIQ (fit.INTELECT) host server application.
5.1. Register Request
A REGISTER function consists of a business entity (customer) wishing to register and obtain an ABIQ Code from Avis Bank.
ELEMENT | TYPE | SIZE | REQ | DESCRIPTION | ||||||
fitREQUEST |
|
| M | This is a collection of the request data elements and their values. It is the highest level of the JSON message string | ||||||
HEADER |
|
| M | This is a collection of standard parameters and their values common in each request | ||||||
requestID | ans | 6,33 | M | A unique identifier generated by the client for each request sent to the fit.INTELECT ABIQ Host Server application. | ||||||
function | a | 6,12 | M | Must be set to REGISTER. | ||||||
REGISTRATION_INFO |
|
| M | This is a collection of parameters and their values that relate to the the registration of the ABIQ Code with Avis Bank | ||||||
businessNAME | ans | 4,64 | M | The registered name of the business identity applying for the ABIQ Code | ||||||
businessADDRESS | ans | 6,128 | M | The address of the business head office or branch. | ||||||
businessCOUNTRY | a | 2 | M | The ISO 3166 2-character country code of the business. | ||||||
businessTYPE | n | 2 | M | The 2-digit ISIC Code that describes the business,
Refer Section 7 – Supported ISIC Codes | ||||||
branchCODE | an | 3 | M | The branch code for the business.
The following rules apply for the business branch code
| ||||||
5.1.1. Example of Register Request
{
“fitREQUEST”: {
“HEADER”: {
“requestID”: “string”,
“function”: “REGISTER”
},
“REGISTRATION_INFO”: {
“businessNAME”: “string”,
“businessADDRESS”: “string”,
“businessCOUNTRY”: “string”,
“businessTYPE”: “string”,
“branchCODE”: “string”
}
}
}
5.2. Order IBAN Request
Am ORDER function consists of a business entity (customer) placing an order for number of virtual ABIQ IBAN and account numbers based on the ABIQ Code.
ELEMENT | TYPE | SIZE | REQ | DESCRIPTION | |
fitREQUEST |
|
| M | This is a collection of the request data elements and their values. It is the highest level of the JSON message string | |
HEADER |
|
| M | This is a collection of standard parameters and their values common in each request | |
requestID | ans | 6,33 | M | A unique identifier generated by the client for each request sent to the ABIQ (fit.INTELECT)host server application. | |
function | a | 6,12 | M | Must be set to ORDER. | |
ORDER_INFO |
|
| M | This is a collection of parameters and their values that relate to the registration of the ABIQ Code with Avis Bank | |
abiqCODE | an | 8,11 | M | The business entities ABIQ Code registered in the Avis Bank ABIQ Registry. | |
numberIBANS | n | 1,4 | M | The number of virtual ABIQ IBAN and account numbers the business entity wishes to order | |
5.2.1. Example Order Request
{
“fitREQUEST”: {
“HEADER”: {
“requestID”: “string”,
“function”: “ORDER”
},
“ORDER_INFO”: {
“abiqCODE”: “string”,
“numberIBANS”: “string”
}
}
}
6. Response Messages
The section of the manual explains each of the response parameters that are returned from the ABIQ (fit.INTELECT) Host Server Application.
All responses from the ABIQ (fit.INTELECT) host server return one of the following HTTP Header Codes in the response header. The response message payload is based on these codes
CODE | MEANING |
200 | OK – indicates that the request has succeeded.
Note: The client application must parse the response message payload to see if the ABIQ (fit.INTELECT) host server application has successfully processed the request message. |
400 | Bad Request Error – indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing). |
401 | Unauthorized Error – indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource. |
403 | Forbidden Error – indicates that the server understands the request but refuses to authorize it. This status is similar to 401, but for the 403 Forbidden status code re-authenticating makes no difference |
404 | Not Found Error – indicates that the server cannot find the requested resource |
429 | Too Many Request Error – indicates the user has sent too many requests in a given amount of time |
500 | Internal Server Error – indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. |
For all HTTP Error Codes, ABIQ (fit.INTELECT) host server application will return the following parameters in the response payload. These parameters are included to aid those frameworks that have a hard time working with anything other than the body of an HTTP response.
Note: The ABIQ (fit.INTELECT) host server application returns a common set of response parameters for all the function types.
ELEMENT | TYPE | SIZE | REQ | DESCRIPTION |
fitRESPONSE |
|
| M | This is a collection of the response data elements and their values. It is the highest level of the JSON message string |
HEADER |
|
| M | This is a collection of standard parameters and their values common in each request |
requestID | ans | 6,33 | M | Echo’s back the value sent in the request message. |
Function | a | 6,12 | M | Echo’s back the value sent in the request message. |
RESPONSE_INFO |
|
| M | This is a collection of parameters and their values that relate to actual response returned from the ABIQ (fit.INTELECT) host server application. |
datePROCESSED | dmy | 12, 16 | M | The date and time the request was processed by the W3ID Host Server.
Must be in the format CCYY/MM/DD hh:mm:ss |
responseID | ans | 12,33 | M | The unique response identifier generated by the ABIQ (fit.SECPAY) host server application fir each request received |
responseCODE | n | 2 | M | The response code returned for processing the request.
Refer: Section 7 – Supported Response Codes |
responseMESSAGE | ans | 6,128 | M | The text message explaining the response code returned.
Refer: Section 7 – Supported Response Codes |
6.1. Register Response
A response to a REGISTER request returns the common response message with the special element and parameter
ABIQ_INFO |
|
| M | This is a collection of parameters and their values as an array that relate to each virtual IBAN and account generated for the ABIQ Code of the business entity. |
abiqCODE | an | 8,11 | M | The unique account identifier within the ABIQ (fit.SECPAY) and Core Banking System |
6.1.1. Register Response Example
{
“fitRESPONSE”: {
“HEADER”: {
“requestID”: “string”,
“function”: “string”
},
“RESPONSE_INFO”: (
“datePROCESSED”: “string”,
“responseID”: “string”,
“responseCODE”: “string”,
“responseMESSAGE””: “string”
}.
“ABIQ_INFO”: {
“abiqCODE”: “string”
}
}
}
6.2. Order Response
A response to an ORDER request returns the common response message plus the element that returns an array of IBAN accounts that are valid for the ABIQ Code sent in the request message.
ABIQ_INFO |
|
| M | This is a collection of parameters and their values that are returned for the successful registration of the ABIQ Code for a business identity |
abiqCODE | an | 8,11 | M | Echo’s back the value sent in the request message. |
IBAN000d |
|
| M | The actual elements and data that is passed for each parameter in the array |
abiqIBAN | an | 16,33 | M | The actual ABIQ virtual IBAN number |
abiqACCOUNT | an | 8,24 | M | The actual virtual account number that is generated. |
6.2.1. Order Response Example
{
“fitRESPONSE”: {
“HEADER”: {
“requestID”: “string”,
“function”: “string”
},
“RESPONSE_INFO”: (
“datePROCESSED”: “string”,
“responseID”: “string”,
“responseCODE”: “string”,
“responseMESSAGE””: “string”
}.
“ABIQ_INFO”: {
“abiqCODE”: “string”,
“IBAN0001”: {
“abiqIBAN”: “string”,
“abiqACCOUNT”: “string”
},
“IBAN0002”: {
“abiqIBAN”: “string”,
“abiqACCOUNT”: “string”
},
“IBAN000n”: {
“abiqIBAN”: “string”,
“abiqACCOUNT”: “string”
}
}
}
}
7. Supported Response Codes
This section of the document lists the responses codes that can be returned in a response message from the ABIQ (fit.INTELECT) host server.
CODE | DESCRIPTION |
00 | Request processed successfully |
09 | Processed successfully pending further processing |
06 | System Timeout |
12 | Invalid function sent in the request message |
25 | Unable to locate original transaction |
21 | No action taken cannot complete request |
30 | Format error parsing request message |
31 | Mandatory parameter [ parameter name ] missing in request |
32 | ABIQ Code already allocated |
33 | For [ parameter name ] Invalid value passed in |
34 | Invalid account identifier |
52 | No ABIQ Code found |
63 | Security violation – Invalid login / password |
92 | Unable to route to sending bank. |
93 | Transaction cannot be completed |
94 | Duplicate request identifier |
96 | System Malfunction |
8. Support ISIC Codes
This section of the document lists the ISIC (International Standard Industrial Classification) Codes that are supported within the ABIQ (fit.INTELECT) host server API..
CODE | DESCRIPTION |
01 | Crop and animal production, hunting and related service activities |
02 | Forestry and logging |
03 | Fishing and aquaculture |
05 | Mining of coal and lignite |
06 | Extraction of crude petroleum and natural gas |
07 | Mining of metal ores |
08 | Other mining and quarrying |
09 | Mining support service activities |
10 | Manufacture of food products |
11 | Manufacture of beverages |
12 | Manufacture of tobacco products |
13 | Manufacture of textiles |
14 | Manufacture of wearing apparel |
15 | Manufacture of leather and related products |
16 | Manufacture of wood and of products of wood and cork, except furniture; manufacture of articles of straw and plaiting materials |
17 | Manufacture of paper and paper products |
18 | Printing and reproduction of recorded media |
19 | Manufacture of coke and refined petroleum products |
20 | Manufacture of chemicals and chemical products |
21 | Manufacture of pharmaceuticals, medicinal chemical and botanical products |
22 | Manufacture of rubber and plastics products |
23 | Manufacture of other non-metallic mineral products |
24 | Manufacture of basic metals |
25 | Manufacture of fabricated metal products, except machinery and equipment |
26 | Manufacture of computer, electronic and optical products |
27 | Manufacture of electrical equipment |
28 | Manufacture of machinery and equipment n.e.c. |
29 | Manufacture of motor vehicles, trailers and semi-trailers |
30 | Manufacture of other transport equipment |
31 | Manufacture of furniture |
32 | Other manufacturing |
33 | Repair and installation of machinery and equipment |
35 | Electricity, gas, steam and air conditioning supply |
36 | Water collection, treatment and supply |
37 | Sewerage |
38 | Waste collection, treatment and disposal activities; materials recovery |
39 | Remediation activities and other waste management services |
41 | Construction of buildings |
42 | Civil engineering |
43 | Specialized construction activities |
45 | Wholesale and retail trade and repair of motor vehicles and motorcycles |
46 | Wholesale trade, except of motor vehicles and motorcycles |
47 | Retail trade, except of motor vehicles and motorcycles |
49 | Land transport and transport via pipelines |
50 | Water transport |
51 | Air transport |
52 | Warehousing and support activities for transportation |
53 | Postal and courier activities |
55 | Accommodation |
56 | Food and beverage service activities |
58 | Publishing activities |
59 | Motion picture, video and television programme production, sound recording and music publishing activities |
60 | Programming and broadcasting activities |
61 | Telecommunications |
62 | Computer programming, consultancy and related activities |
63 | Information service activities |
64 | Financial service activities, except insurance and pension funding |
65 | Insurance, reinsurance and pension funding, except compulsory social security |
66 | Activities auxiliary to financial service and insurance activities |
68 | Real estate activities |
69 | Legal and accounting activities |
70 | Activities of head offices; management consultancy activities |
71 | Architectural and engineering activities; technical testing and analysis |
72 | Scientific research and development |
73 | Advertising and market research |
74 | Other professional, scientific and technical activities |
75 | Veterinary activities |
77 | Rental and leasing activities |
78 | Employment activities |
79 | Travel agency, tour operator, reservation service and related activities |
80 | Security and investigation activities |
81 | Services to buildings and landscape activities |
82 | Office administrative, office support and other business support activities |
84 | Public administration and defence; compulsory social security |
85 | Education |
86 | Human health activities |
87 | Residential care activities |
88 | Social work activities without accommodation |
90 | Creative, arts and entertainment activities |
91 | Libraries, archives, museums and other cultural activities |
92 | Gambling and betting activities |
93 | Sports activities and amusement and recreation activities |
94 | Activities of membership organizations |
95 | Repair of computers and personal and household goods |
96 | Other personal service activities |
97 | Activities of households as employers of domestic personnel |
98 | Undifferentiated goods- and services-producing activities of private households for own use |
99 | Activities of extraterritorial organizations and bodies Not elsewhere classified |
9. URL Address Endpoints
This section of the documents explains the URL Addresses used to access the ABIQ (fit.INTELECT) host server running the application.
Requests to the ABIQ (fit.INTELECT) host server API must be sent using HTTP POST and secured over SSL on port number 443.
The (client) server must support as a minimum the TLS 1.2 protocol and associated cipher suites.
The HTTP header must contain at a minimum the following header parameter:
a. Content-Type – Must be set to application/json.
b. Content-Length – This must be set to the size of the request, in bytes.
9.1. Test Environment
The API messages should be posted to https://gateway.avisbank.com/t... and must use the port number 443 to communicate on. The server sending the request message must contain a valid SSL Certificate issued by an approved CA.
Note: You must provide the IP Address for each of the test sites you will be using to connect to the ABIQ (fit.INTELECT) host server.
9.2. Live Environment
The API messages should be posted to https://secure.avisbank.com/tf... and must use the port number 443 to communicate on. The server sending the request message must contain a valid SSL Certificate issued by an approved CA.
Note: You must provide the IP Address for each of the web sites you will be using to connect to the ABIQ (fit.INTELECTABIQ) host server.
