This document is intended to provide all technical information you require in order to use our Shortcode Provisioning services.
We will make technical staff available to answer questions that you may have during the installation process. Certain technical specifications about the client system will be necessary to ensure that the most appropriate setup is used to achieve the desired commercial results. The setup coding is very simple and easy to implement.
Step 1 - An US Mobile Phone Owner (MPO) wants to buy mobile content using the services you offer. In order to do this, the MPO will have to send an SMS text message to the shortcode 31285. This message will have to comply with the the following format:
Keyword OrderID
Where the parameters have the following semnification:
Keyword
The keyword that FasPay will assign to you. Not case-sensitive. E.g.: "BUY"
OrderID
Any string (with no spaces) that will be forwarded to your systems in order to identify what the MPO has ordered (see below)
Assuming that you have been assigned the "BUY" keyword, a valid SMS text message that can be sent to 31285 will look like:
Buy 123456
Step 2 - Following the Phone -> Carrier -> Gateway -> FasPay route, the message gets to the FasPay systems. If this message starts with the keyword assigned to you (say BUY), FasPay will need to ask your systems for the Content WAP Download Link (CWDL) that will be sent to the MPO.
This link should point to the actual content file so when the MPO access this link using their phone, the download process starts automatically.
In order to get the CWDL, FasPay is making an HTTP request to your systems as follow:
Where the parameters have the following semnification:
OrderID
The string that the MPO has sent in the SMS text message after the keyword (123456 in the example above)
PhoneNumber
The mobile phone number that the SMS text message was sent from. E.g.: 10123456789
NetworkOperator
A string identifying the network operator that the MPO is subscribed to. The possible values this parameter may have are: ATTUS, CINGULARUS, TMOBILEUS and SPRINTUS
TranzactionID
A string that uniquely identifies the order within the FasPay systems (see below)
As a result of the above HTTP request, you will have to respond with the CWDL that will be sent to the MPO. An example of a valid download URL address is:
http://www.yourserver.com/WapDownload.php?XXXXX
If the HTTP request we make is incorrect (or something else goes wrong), instead of the CWDL that points to the content file (as shown above), you will have to reply with a detailed error message. In this case, the response you will send must invariably start with the word ERROR (first 5 characters).
Step 3.1 - For all MPO that are AT&T (Cingular Blue) or Cingular subscribers the following actions are executed:
Step 3.1.1 - FasPay sends an non-premium (bulk) SMS text message to the MPO asking to confirm that they want to continue with the order.
Step 3.1.2 - The MPO replies with an SMS text message sent to 31825 that contains the "YES", "OK", etc keywords.
Step 3.1.3 - FasPay sends the CWDL to the MPO in an premium (billed) SMS text message reading "To download your item go here: CWDL".
Step 3.1.4 - Following the link in the SMS text message they receive, the MPO downloads the content to their mobile phone (from your systems).
Step 3.2 - For all MPO that are Sprint or T-Mobile subscribers the following actions are executed:
Step 3.2.1 - FasPay sends the CWDL to the MPO in an non-premium (bulk) SMS text message reading "To download your item go here: CWDL".
Step 3.2.2 - Following the link in the SMS text message they receive, the MPO downloads the content to their mobile phone (from your systems).
Step 3.2.3 - Your systems notify FasPay that the content has been downloaded/accessed. To do this, you systems have to make the following HTTP request after the content has been successfully downloaded to the MPO phone:
http://mecst.com/exdwnotify.php?TranzactionID
Where the parameters have the following semnification:
TranzactionID
The string that uniquely identifies the order within the FasPay systems (as described in Step 2)
Note: Your systems will have to cross-reference the CWDL with this TranzactionID, so when the MPO access a certain CWDL, your systems will notify FasPay using the approriate TranzactionID.
As the result of a successful HTTP transaction, you will be returned with a body that reads: App OK.
As the result of a failed HTTP transaction, you will be returned with a body that reads: ERROR: Error Description.
Step 3.2.4 - FasPay sends "Thank you. You have been billed $XXX" premium (billed) SMS text message to the MPO.
Step 1 - An UK Mobile Phone Owner (MPO) wants to buy mobile content using the services you offer. In order to do this, the MPO will have to send an SMS text message to the shortcode 88600. This message will have to comply with the the following format:
Keyword OrderID
Where the parameters have the following semnification:
Keyword
The keyword that FasPay will assign to you. Not case-sensitive. E.g.: "BUY"
OrderID
Any string (with no spaces) that will be forwarded to your systems in order to identify what the MPO has ordered (see below)
Assuming that you have been assigned the "BUY" keyword, a valid SMS text message that can be sent to 88600 will look like:
Buy 123456
Step 2 - Following the Phone -> Carrier -> Gateway -> FasPay route, the message gets to the FasPay systems. If this message starts with the keyword assigned to you (say BUY), FasPay will need to ask your systems for the Content WAP Download Link (CWDL) that will be sent to the MPO.
This link should point to the actual content file so when the MPO access this link using their phone, the download process starts automatically.
In order to get the CWDL, FasPay is making an HTTP request to your systems as follow:
Where the parameters have the following semnification:
OrderID
The string that the MPO has sent in the SMS text message after the keyword (123456 in the example above)
PhoneNumber
The mobile phone number that the SMS text message was sent from. E.g.: 44123456789
NetworkOperator
A string identifying the network operator that the MPO is subscribed to. The possible values this parameter may have are: BTCELLNETUK, ORANGEUK, TMOBILEUK and VODAFONEUK
TranzactionID
A string that uniquely identifies the order within the FasPay systems (can be ignored, this parameter is used only for United States Shortcode Provisioning)
As a result of the above HTTP request, you will have to respond with the CWDL that will be sent to the MPO. An example of a valid download URL address is:
http://www.yourserver.com/WapDownload.php?XXXXX
If the HTTP request we make is incorrect (or something else goes wrong), instead of the CWDL that points to the content file (as shown above), you will have to reply with a detailed error message. In this case, the response you will send must invariably start with the word ERROR (first 5 characters).
Step 3 - FasPay sends the CWDL to the MPO in an premium (billed) SMS text message reading "To download your item go here: CWDL".
Step 4 - Following the link in the SMS text message they receive, the MPO downloads the content to their mobile phone (from your systems).
Please note that FasPay is not responsible with the content download to the MPO phone. FasPay will just make sure that the CWDL gets to the MPO phone. The actual WAP download is then handled by your systems.
We will make technical staff available to answer questions that you may have during this installation process. For further information, don't hesitate to contact our technical department at support@faspay.com.
Thank you for your interest in our Shortcode Provisioning services!
Printable version