Overview
The Server 2 server API exposes some core functionality via an industry standardised REST endpoint. Please refer to Server 2 Server API integration section for details information on this
GetTransactionStatus
The Charge method provides the ability for the merchant to determine the status of a billing transaction.
StopSubscription
The StopSubscription method allows a merchant to stop the subscription of an end user
SendMessage
The SendMessage method provides the ability for the merchant to send a free to user SMS message to the end user.
HLRLookup
This API method allows a variety of carrier or non-carrier loop options so that a merchant can identify a mobile users identity and netowrk details
PersonaliseAPI
Personalise API allows merchants so send customSMS similar to the SendMessageAPI. however personalise is specifically setup to add the feature of being able to insert a access short-link (generated by T2B) to the message. granting user access back to the site even if they are unidentified on WIFI
GetAlias
This allows the merchant to provide a users msisdn and be returned T2B alias for this number. The primary use of this is for Customer service calls so that whgen a user querys with there raw MSISDN, the merchant can convert this to a T2B Alias, and trace it via the portal
Notifications
The notifications are sent as a HTTP GET to a preconfigured notification URL. They provide status information on all transactions completed via PFI payment pages for all flows.
This is not a exposed API for clients to call like the above API's. this will be us calling you, the client with the relevant infomation