Overview of API connectors:
This Session is only meant for authorised parties.
Abuse is punishable in the court of law.
https://apitest.FTAssetManagement.com ....: test and sandbox environment
https://api.FTAssetManagement.com ....: live and production environment. We will give you access after approvals.

Please see the complete overview in one PDF: API_Communications_Specifications.pdf

Account holders placed their transfers and prepared them for collection.
This process corrects these transfers.
All these processes exchange messages in the agreed JSON format.
/Reservation.asp?key=(Key_code)&Reservation=(Res_code)&account=(account)
Where:
[Key_code] (required) is the specific code for the institution
[Res_code] (optional) is for a specific transaction. (Reservation code)
[Account] (optional) is for a specific account.
[Res_code] or [Account] needs to be supplied


An outgoing transfer has been confirmed to be accepted by the receiving financial entity.
This completes the transfer on our end.
/Reservation_confirmation.asp

A financial entity sends us a cash transfer for our acceptance.
/receiving.asp?key=(Key_code)
[Key_code] (required) is the specific code for the institution


We send cash transfers to a financial entity for our acceptance.
The page name (send.asp) is not relevant. You will receive the agreed message in JSON format.
/send.asp?key=(Key_code)
[Key_code] (required) is the specific code for the institution.