These scope of services are for informational purpose only. Solely our German scope of services are legally binding. Version 4.0 whatever mobile GmbH
Contents 1. Preamble... 4 2. Basics... 4 2.1. Types of payment...4 2.1.1. SMS Payment... 4 2.1.2. MMS Payment... 4 2.1.3. Web Payment... 4 2.1.4. Application Payment... 4 2.1.5. Voice Payment... 4 2.2. Types of transactions...5 2.2.1. Event-based single transactions... 5 2.2.2. Event-based subscription services... 5 2.2.3. Time-based services... 5 2.3. Technology...5 2.3.1. SMS short codes... 5 2.3.2. MMS short codes... 5 2.3.3. Voice short codes... 6 2.3.4. Possibility of usage... 6 2.3.5. Comparison shared vs. exclusive usage... 6 2.3.6. Keywords... 6 2.3.7. Billing systems... 7 2.3.8. Particularities of branded resellers / MVNOs / service providers... 7 3. Scope of services SMS Payment... 8 3.1. SMS Single Payment...8 3.1.1. Functionality... 8 3.1.2. Keyword-based order and pricing... 8 3.1.3. Handshake... 8 3.1.4. Sending of SMS with a premium short code as the sender s ID... 9 3.1.5. Particularities at Telekom... 9 3.1.6. Minimum turnover premium SMS at E-Plus... 9 3.1.7. Four-digit short codes... 9 3.1.8. Particularities for TV voting... 9 3.1.9. Auto-Response... 9 3.1.10. Delivery of SMS... 10 3.2. MMS Single Payment...10 3.2.1. Keyword-based order and pricing... 10 3.2.2. Handshake... 10 3.2.3. Delivery of messages... 10 3.3. SMS Subscription Payment...11 3.3.1. Keyword-based order and pricing... 11 3.3.2. Handshake... 11 3.3.3. Welcome messages... 11 3.3.4. Delivery... 11 3.3.5. Status information... 11 3.3.6. Cancellation of subscriptions... 11 3.3.7. SMS Subscription Payment without initial MO of the end customer... 12 3.3.8. Delivery of messages to existing subscription end customers without billing... 12 Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 2 of 25
4. Scope of services Web Payment...12 4.1. Availability...12 4.2. Ordering...12 4.3. Delivery...13 4.4. Cancellation of subscriptions...13 4.5. Webmaster capability...13 4.6. Registration...14 4.7. Fraud prevention mechanisms...14 4.8. Special revenue shares in the networks of Telekom, Vodafone, o2 and debitel...14 5. Scope of services Voice Payment...15 5.1. Functionality...15 5.2. Realisation of special regulations of the mobile network operators...16 5.3. Charging of Voice Payment services...16 5.4. Price announcements...16 5.5. VideoCall functionality in the network of O 2...16 5.6. Pulsing...16 5.7. Bill warnings...16 5.8. Forced disconnection...17 5.9. Particularities in the network of Telekom...17 5.10. Minimum payout O 2...17 6. Scope of services Application Payment...17 7. General functionalities and services...18 7.1. Bill warnings and information SMS...18 7.2. Individualised handshake messages...18 7.3. Optional prevention of duplicate orders...18 7.4. Forwarding of the MSISDN to the CP...18 7.5. Pre-check whether an MSISDN can be billed...18 7.6. Forwarding of billing results...18 7.7. Processing of re-authorising and re-billing...19 7.8. Optimising of content of automated messages...19 7.9. 3 rd party consumer support...19 7.10. Maintenance Reply...19 7.11. Debt claims towards end customers...19 8. Connection methods...20 9. Client Control Center...21 10. Fees...22 10.1. Set up fees, operation fees and transaction fees...22 10.2. Volume discount...22 11. Special regulations and requirements...22 11.1. Compliance to the National Regulations...22 11.2. Description of a service...22 11.3. End consumer hotline...23 12. Technical support...23 13. Glossary...24 Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 3 of 25
1. Preamble whatever mobile GmbH () is a Mobile Application Provider. whatever mobile owns a self-developed SMS & MMS message gateway with direct and indirect connections to the SMS and MMS centers of nearly all national and international mobile network operators and mobile service providers. These scope of services specify the product Mobile Payment, which enables the contractual partner (CP) of whatever mobile to bill single and subscription payments via the mobile phone invoice of the end customers. whatever mobile owns a technical platform (whatever mobilepay) that can access the payment interfaces of the national mobile network operators and mobile service providers. 2. Basics 2.1. Types of payment 2.1.1. SMS Payment SMS Payment refers to payment services that are initiated by the end customer through an order by SMS. Mobile related content and services. Both single and subscription payment is possible. The end customer uses various keywords to operate the subscription. 2.1.2. MMS Payment MMS Payment refers to payment services that are initiated by the end customer through an order by MMS. Mobile related content. MMS Payment can be used for single transactions only. 2.1.3. Web Payment Web Payment refers to payment services that are initiated by the end customer via the Internet, i.e. web portals. This product can be used to bill mobile content or the access to websites 1. The end customer manages his subscriptions through the website of the content provider. 2.1.4. Application Payment Application Payment refers to payment services that are initiated by the end customer through the application itself. This product can be used both for single and subscription payment. Particularly, it is recommended for JAVA applications charged with a basic fee in the context of a subscription service. 2.1.5. Voice Payment Voice Payment refers to payment services that are initiated by the end customer through a voice short code. When calling a voice shortcode, the end customer is charged a minute-based fee. Voice Payment is suitable for voice information services / portals as well as the realisation of MO video call services. 1 limited availability only Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 4 of 25
2.2. Types of transactions 2.2.1. Event-based single transactions A single payment is a one-off billing of a service that is used by the end customer. The end customer does not commit to a long-term contract when using single transactions. whatever mobile takes care of the receipt and the processing of the order, the communication with the billing interfaces of the mobile network operators, the handshake if necessary, and the one-time delivery of the content. The fees are billed directly with the mobile network operators. Please note that the processes, which are requested by the mobile network operators, may vary. 2.2.2. Event-based subscription services Subscription services (subscription payment) are used to regularly bill and deliver content. whatever mobile offers the same services as described in the paragraph about single transactions. Differing to this, the content is delivered and billed regularly until the service is terminated by the end customer. The end customer is informed about the offer and its terms within the framework of the handshake, which needs to be acknowledged by the end customer. By agreeing to the handshake the end customer enters into a legally binding contract with our CP. 2.2.3. Time-based services A time-based billing applies if the end customer is charged a base fee for a service per time unit. A time-based billing may also apply for voice payment services. However, the billing of all further services needs to be issued on event-basis according to the regulations of the mobile network operators. 2.3. Technology 2.3.1. SMS short codes SMS short codes are registered directly at the SMSC for the CP. Short codes are usually five digit numbers, i.e. 86000. German short codes can only be reached by German mobile users. In order to be reached from all German networks, a short code needs to be registered with all SMSC (and vsmsc). whatever mobile owns a pool of SMS short codes, which are already registered with all German networks (including mobile service providers). SMS short codes can be set up as standard short code (non-premium short code) or as a premium short code. When using premium short codes, telephone related value-added services can be billed via premium SMS. It needs to be distinguished between MO-billed and MT-billed premium short codes. On MO-billed premium short codes each incoming (mobile originated) message is charged, while on MT-billing each message sent to the end customer (mobile terminated) is billed. A separate premium SMS short code is necessary for each tariff class. Premium SMS-MO short codes are used for the product SMS Single Payment via Premium SMS. MT premium short codes are used when mobile network operators have no billing interfaces (see 2.4) in order to offer further payment services. Please note the technical documentation. 2.3.2. MMS short codes MMS short codes are registered directly at the MMSC of the mobile network operator by whatever mobile for the CP. Usually these numbers are five digit numbers, i.e. 84000. German MMS short codes can only be reached by German mobile users. In order to be reached from all German networks, an MMS short code needs to be registered with all four MMSC. Since the German mobile service providers use the MMSCs of the mobile network operators there is no need for a separate connection to the service providers (compare SMS short codes). whatever mobile owns a pool of MMS short codes, which are already registered with all German networks. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 5 of 25
2.3.3. Voice short codes Voice short codes are directly set up within the voice routing of the mobile network operators. A registration of the voice short code with the service providers is not necessary. 2.3.4. Possibility of usage The CP can choose between the exclusive usage of short codes / long numbers or the shared usage of existing short codes / long numbers of whatever mobile. When using exclusive dedicated short codes, these will be registered by whatever mobile with the mobile network operators and mobile service providers for the CP s exclusive use. All incoming SMS will be delivered immediately to the CP s (logic) message account. When using existing numbers of whatever mobile in shared mode, messages will be distinguished by the keyword prefix of the SMS. This prefix is used by the infrastructure of whatever mobile to allocate messages to the correct client. 2.3.5. Comparison shared vs. exclusive usage Feature Shared usage Exclusive usage Cost Low Relatively high Keywords Compulsory Not necessary Duration of setup At short notice Up to 8 weeks 2.3.6. Keywords Keywords will only be issued once per short code and are allocated by whatever mobile to the CP for the duration of the contract. Keywords can be applied for online via the Client Control Center. SMS, which are received on a short code with a keyword (standing alone or followed by space), which is registered to the CP, are forwarded to the Message Account of the CP or respectively to WMPay. The CP can generally choose keywords freely. whatever mobile recommends using keywords according to the guidelines below: Keywords should have at least 3 characters, and up to 8 characters maximum Keywords should be real words, preferable known to T9 spelling assistants (predictive text) Keywords should directly relate to the context of the service they are used for Keywords should not require particularly good spelling knowledge of the end customer Keywords should not hinder other applications Keywords should not entail special characters Suitable keywords Music Game1, Game2,... Sound1, Sound2,... Nina, Susanne, Peter,... Auto Non-suitable keywords XPT1 Sauerstoffflasche Hello Love?!w ü Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 6 of 25
whatever mobile also offers the possibility to set up tolerant keyword routing for the CP. This technology is able to search the entire text of the message for the keyword (the keyword does not need to be at the beginning of the message) or for specific character patterns (i.e. three numbers followed by a letter) or a combination of both. If required, whatever mobile checks if tolerant keyword routing is necessary and possible. whatever mobile offers the possibility of removing the keyword from the message. The keyword used for routing purpose is removed before the message text is forwarded to the message account. This feature is also available when using tolerant keyword routing. If the CP does no longer market one or more of his keywords, whatever mobile reserves the right to repossess these keywords 4 weeks after they were last marketed, and to allocate them to a new client. The CP can terminate the usage of a keyword with a period of one month to the end of the following month. Keywords that violate applicable law, any third party s rights or are capable of hindering or limiting the services of whatever mobile may not be issued. Further, whatever mobile reserves the right to repossess keywords that violate any of the regulations mentioned above. whatever mobile offers extensive statistics on the incoming messages per keyword via the Client Control Center at http://ccc.whatevermobile.com. 2.3.7. Billing systems Billing systems are operated by mobile network operators and are independent billing interfaces. Billing systems offer various advantages for the content provider and the end customer compared to premium short codes. It is not mandatory to send or receive messages in order to bill the service. Since there is no need for a separate short code for each price class, the pricing is flexible and can be amended promptly. Special mechanisms ensure that each reserved amount can be billed. Some systems offer additional functionalities like the automatic initiation of handshake messages to the end customers. Not all German mobile network operators offer billing systems at the moment. 2.3.8. Particularities of branded resellers / MVNOs / service providers When charging end customers of the so-called branded resellers such as debitel light and MVNOs such as Vistream as well as special constellations between network- and service providers such as The Phone House, constrictions on the part of the the mobile network operators billing interfaces may apply. These constrictions depend on the contractual relationship between the mobile network operator and the service provider. whatever mobile cannot influence the availability of this in advance. However, whatever mobile aims to provide the best possible billing of services by a complex process structure. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 7 of 25
3. Scope of services SMS Payment 3.1. SMS Single Payment 3.1.1. Functionality The content provider may offer mobile value-added services via premium SMS services. Any premium turnover generated in this manner is paid out by the network operators to whatever mobile after transportation and collection fees were deducted. whatever mobile pays distributes a revenue share of the CP s premium turnover to the CP. SMS Single Payment offers a high quality and cost efficient way of receiving SMS messages from mobile networks via the infrastructure of whatever mobile. whatever mobile sets up a (logic) Message Account on its platform for the CP. The options on how this account can be accessed are detailed in the section Connection methods within this document. Depending on the service offered, the payment transactions are usually conducted either via premium SMS short code or via the payment interface of the particular mobile network operator. The message account is usually configured to process 5 SMS per second and allows simultaneous access via the IP connection, which was specified by the CP. If the CP requires a higher bandwidth or needs to access the account via various IP addresses with multiple parallel connections, whatever mobile can configure this easily. All SMS received by whatever mobile are forwarded to the message account of the CP. Depending on the type of connection, the messages will then be forwarded on to the CP or will be made available for pickup by the CP (see whatever mobile API Specification ). whatever mobile ensures the quality management in association with the collection of SMS from the mobile network operators and mobile service providers, and guarantees a prompt delivery of these to the CP s Message Account. 3.1.2. Keyword-based order and pricing whatever mobile offers short codes that allow a keyword-based pricing. When using such flexible short codes, the payment transaction is initiated by the end customer sending an SMS to a standard tariffed short code (e.g. 86000). Based on the keyword sent, the identification and the tariff of the service is carried out. Thus, the tariff may vary from keyword to keyword. Offering services with an end customer tariff of more than 2.00, the usage of the described short codes is mandatory according to the regulations of the TKG. According to the TKG, the transport fee the end customer is charged for an SMS sent to a standard tariffed short code, is regarded as a price component. Services with an end customer tariff of 1.99 are billed including a transport fee due to the legal regulations of the TKG. By this procedure, a handshake becomes obsolete (see 3.1.3). In this case, the payment transaction is carried out via the billing interfaces of the mobile network operators. Depending on the particular service requirements and the interface being used, SMS Single Payment supports the billing of inbound SMS (SMS MO, if supported by the network operator) or the billing of outbound SMS (SMS MT). By using a keyword-based tariffing, the usage of different short codes per end customer tariff is not necessary. This allows a concentration of all services on a unique short code (portal number). 3.1.3. Handshake According to the regulations of the TKG, the end customer needs to be informed on the price per request incl. VAT and further price components when ordering a service of 2.00 or above. The price incl. all components needs to be displayed visible and legible for the end customer before he is charged for the premium service. The end customer needs to confirm this Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 8 of 25
information. When a service of 2.00 or above is requested by the end customer, the system of whatever mobile automatically issues a handshake according to the legal regulations. The fees for the delivery of these handshake messages - as far as not borne by the network operators themselves are charged to the CP according to the order sheet. Any changes to these regulations by the network operators or the legal framework are reserved explicitly. 3.1.4. Sending of SMS with a premium short code as the sender s ID Each SMS that carries a premium short code as sender s ID, which is registered as a whatever mobile short code with the mobile network operators must be sent via whatever mobile s infrastructure using the delivery type direct termination. 3.1.5. Particularities at Telekom In connection with content delivery, Telekom requests that only the delivery of the content can initiate a billing. The fees for the delivery of the SMS are not included in the revenue share mentioned above, and depend on the fees for direct termination into the network of Telekom (see also SMS Outbound). These technical particularities regarding the MT-billing are explained in detail in the whatever mobile API Specification. Telekom distinguishes premium SMS short codes into voting and factoring services. whatever mobile uses the short code 84000 for voting services, while all other short codes are registered for factoring services. Voting services are Telekom s own services. For factoring services Telekom takes care of the billing only, and refers to the content provider (whatever mobile) on the bills of the end customers. Varying price quotations in adverts result from these two models. When advertising factoring services via Telekom, the transportation fee needs to be stated in addition to the premium price. The National Regulations Germany, which are part of the contract, specify this in more detail. 3.1.6. Minimum turnover premium SMS at E-Plus For SMS short codes registered with E-Plus after April 1 st 2007, the minimum turnover has been changed to a monthly basic fee. For SMS short codes registered with E-Plus before April 1 st 2007, E-Plus requires a minimum end customer turnover of 2,000.00 plus VAT per month. If this is not reached, E-Plus claims the loss of E-Plus service and collection share as a contractual penalty. In case of a premium SMS short code priced at 0,29/SMS, this penalty is 1,160.00 ( 2,000.00 * 58% service and collection share), if there is no turnover at all. Since the E-Plus service and collection fee decreases as the tariff increases, the maximum contractual penalty decreases the higher the price of the premium SMS short code is. 3.1.7. Four-digit short codes The German network operators issue four-digit short codes, i.e. 1234 for high volume services. These short codes are subject to a different (expensive) price structure. In case you plan such a service, please get in touch with your contact at whatever mobile. We are happy to inform you of the possibilities and particularities regarding four-digit short codes. 3.1.8. Particularities for TV voting Since the beginning of 2005 almost all mobile network operators and mobile service providers offer increased revenue shares for TV voting applications at a price of 0.50 per SMS. In case you plan such a service, please get in touch with your contact at whatever mobile. We are happy to inform you of the possibilities and particularities regarding TV voting. 3.1.9. Auto-Response If the CP uses the SMS feedback tool (see Connection methods ), there is also the possibility of an automatic response to all incoming messages according to the keyword (SMS Inbound & Auto-Response). The CP can define standard response messages for each keyword. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 9 of 25
Further, it is possible to define a time frame, i.e. for raffles or voting, in which all incoming messages are being replied to with a text of the CP s choice. Messages received outside of the time frame are being replied to with a different message, also as defined by the CP. Special conditions for set up and utilization of the auto response tool can be found in the order sheet SMS Inbound. 3.1.10. Delivery of SMS The delivery of SMS needs to be carried out mandatorily via the direct connections of whatever mobile. The CP can choose between the delivery of SMS or MMS services. whatever mobile offers SMS Single Payment through standard tariffed short codes via current messaging protocols (see 8.11). Alternatively, whatever mobile provides the WMPay interface for Single Payment transactions to offer an easy technical implementation for users of the subscription interface. When using the WMPay interface, the content ordered must be delivered to the end customer after the order and the successful handshake (if necessary). whatever mobile communicates the successful request of a transaction to the CP, who transmits content to WMPay regularly. The payment platform of whatever mobile receives the content and forwards it to the end customer. If the delivery is successful, the content is billed with the end customer. 3.2. MMS Single Payment 3.2.1. Keyword-based order and pricing MMS Single Payment transactions are initiated by the end customer sending an MMS to a standard tariffed short code (e.g. 72000 ). Based on the keyword sent, the identification and the tariff of the service is carried out. The keyword is searched within the body and the subject of the MMS sent. Thus, the tariff may vary from keyword to keyword. The billing is issued via the payment interfaces of the mobile network operators. MMS Single Payment is based on the receipt of MMS (MMS-MO). By using a keyword-based tariffing the usage of different short codes per end customer tariff is not necessary. This allows a concentration of all services on a unique short code (portal number). According to the TKG, the transport fee the end customer is charged for an SMS sent to a standard tariffed short code, is regarded as a price component. Services with an end customer tariff of 1.99 are billed including a transport fee due to the legal regulations of the TKG. By this procedure, a handshake becomes obsolete (see 3.2.2). 3.2.2. Handshake According to the regulations of the TKG, the end customer needs to be informed on the price per request incl. VAT and further price components when ordering a service of 2.00 or above. The price incl. all components needs to be displayed visible and legible for the end customer before he is charged for the premium service. The end customer needs to confirm this information. When a service of 2.00 or above is requested by the end customer, the system of whatever mobile automatically issues a handshake according to the legal regulations. The fees for the delivery of these handshake messages - as far as not borne by the network operators themselves are charged to the CP according to the order sheet. Any changes to these regulations by the network operators or the legal framework are reserved explicitly. 3.2.3. Delivery of messages MMS Payment requires no explicit delivery of messages to be able to charge the end customer. This allows the realisation of votings or MMS2Screen services. If messages need to be delivered to the end customer for the successful provision of the service, the messages need to be delivered via the direct connection of whatever mobile. The CP can choose between the delivery via SMS or MMS. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 10 of 25
3.3. SMS Subscription Payment 3.3.1. Keyword-based order and pricing Offering SMS Subscription Payment, the payment transaction is initiated by the end customer sending an SMS to a standard tariffed short code (e.g. 86000). Based on the keyword sent, the identification and the tariffing of the service are carried out. Thus, the tariff may vary from keyword to keyword. Services can be distinguished between different contents, tariffing or the frequency of delivery. The payment transaction is carried out via the billing interfaces of the mobile network operators. By using a keyword-based tariffing, the usage of different short codes per end customer tariff is not necessary. A combination of subscription and SMS or MMS Single Payment services is possible. This allows a concentration of all services on a unique short code (portal number). 3.3.2. Handshake According to the regulations of the TKG, the end customer needs to be informed on the price per request incl. VAT and further price components when ordering a service. The price incl. all components needs to be displayed visible and legible for the end customer before he is charged for the premium service. The end customer needs to confirm this information. The system of whatever mobile automatically issues a handshake according to the legal regulations. The fees for the delivery of these handshake messages as far as not borne by the network operators themselves are charged to the CP according to the order sheet. Any changes to these regulations by the network operators or the legal framework are reserved explicitly. 3.3.3. Welcome messages After the handshake was successful, whatever mobile sends a confirmation message (welcome message) to end customers of Vodafone D2 and O 2. Welcome messages are mandatory in the networks mentioned above in order to finalise an order. The fees for the delivery of these welcome messages as far as not borne by the network operators themselves are charged to the CP according to the order sheet. 3.3.4. Delivery When using the WMPay interface, the content ordered must be delivered to the end customer after the order and the successful handshake (if necessary). whatever mobile communicates the successful request of a transaction to the CP, who transmits content to WMPay regularly. The payment platform of whatever mobile receives the content and forwards it to the end customer. If the delivery is successful, the content is billed with the end customer. The amount of content that can be provided is limited for subscription services. There is a configurable limit of content messages per subscription. Once this limit is reached each further content is rejected by whatever mobilepay. 3.3.5. Status information whatever mobile supports end consumer enquiries regarding their subscription. This may be initiated by submitting a short message with the content STATUS ( STATUSABO in the E-Plus network) to the short code used to conclude the subscription. The system of whatever mobile issues an SMS to the end customer including an overview of his subscriptions on this short code (E-Plus customers receive an overview of all their subscriptions over all short codes including their pricing). This functionality is accordant to the network operator s requirements. If possible the costs incurred by this process are charged to the content provider. 3.3.6. Cancellation of subscriptions whatever mobile supports the cancellation of subscriptions via SMS, or manually by the CP when processing consumer support enquiries. All cancellation mechanisms are according to the regulations of the mobile network operators. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 11 of 25
All end customers have the possibility to cancel single subscriptions by sending an SMS with STOP <Keyword>; STOPP<Keyword>; to the short code used to conclude the subscription. End customers of Vodafone D2 may submit an SMS with STOPALLE or STOP ALLE in order to cancel all their subscription services on the short code that the SMS is addressed to. E-Plus customers cancel all their subscriptions with whatever mobile when sending an SMS with STOPALLE. Customers of the mobile service provider debitel may cancel all subscriptions on a short code by sending in STOPALL, STOPP ALL, STOP ALLE or STOPP ALLE. The CP may cancel single subscriptions or all subscriptions of an end customer via a special interface. E-Plus customer s are informed automatically via SMS when their subscription is cancelled. 3.3.7. SMS Subscription Payment without initial MO of the end customer whatever mobile offers the possibility to have end customers subscript to subscription services without needing to send an initial SMS MO. Contrary to the procedure as described above, using this functionality the initial SMS MO becomes obsolete. The CP can initiate the handshake directly which solely needs to be confirmed by the end customer by sending just one SMS MO. Please note that such services require a special approval by the mobile network operators. Thus, this interface can be used only on special request and needs to be implemented seperately. To prevent end customers from any fraudulent misusage of the interface, the number of requests sent to a particular MSISDN can be limited in different manners. 3.3.8. Delivery of messages to existing subscription end customers without billing The payment interface of whatever mobile offers the possibility to deliver messages to existing subscription end customers without issueing a payment transaction. The CP may use the same technical interface which is also used for subscriptions as well as the delivery of payment transactions. This allows the delivery of cross-selling messages or of content as a gift. 4. Scope of services Web Payment 4.1. Availability Web Payment allows the billing of end customers of Telekom, Vodafone D2, E-Plus, O2, as well as the service provider debitel. End customers of other service providers are charged via the mobile network operators, as far as possible. Basically, all specific services need to be submitted to the mobile network operators for approval. Thus, whatever mobile cannot guarantee whether a service can be considered submitted or not. 4.2. Ordering The end customer chooses a particular content on the website of the CP and orders it. If WMPay receives a request from the CP, a TAN is generated and sent to the end customer. The interface is designed in a manner that no particular requests are necessary for the issuing of a subscription order. Only a single request is used for the content delivery in connection with the service ID. According to the service ordered, the type of order is identified. In case the service ordered is a subscription service, it is checked whether there is already a subscription service registered for this MSISDN. In case there is no subscription service registered yet, the type of order is being issued Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 12 of 25
according to the service ordered (initial handshake). Otherwise, the content is simply delivered and charged. Basically, orders need to be placed by the end customer. The TAN received by the end customer needs to be entered on the CP s website. The TAN is transmitted to the interface. If the TAN has been entered correctly, the subscription is completed respectively the single transaction confirmed. 4.3. Delivery The content provider requests the billing interface of whatever mobile (WMPay) to deliver content. Content can be delivered via SMS. WMPay automatically checks what kind of order method is present and if necessary initiates the required method. The amount of content that can be provided is limited for subscription services. There is a configurable limit of content messages per subscription. Once this limit is reached each further content is rejected by WMPay. It is possible to configure the maximum single transaction turnover per end customer, service area and day. This default is defined globally per services provider and can be amended per service area. Once this limit is reached, no further transactions can be carried out for this service area. 4.4. Cancellation of subscriptions Subscriptions are cancelled by special request of the content provider. The end consumer receives a confirmation SMS once the subscription is cancelled. whatever mobile charges the costs to the content provider. Cancellations of subscriptions via SMS are not intended. The content provider must ensure that the cancellation functionality is easily accessible and designed according to the current National Regulations. 4.5. Webmaster capability The Web Payment system of whatever mobile was developed to be capable of webmasters. In order to allow this the system is based on a special structure, which is explained in the following paragraphs. The CP of whatever mobile is the content provider. The content provider has the possibility to create as many webmasters as required. Webmasters run the website on behalf of the content provider. Webmasters identify themselves to whatever mobile with a webmaster ID and a webmaster password. Further, each website gets a unique identification number when it is installed. Websites may be pooled to service areas and are thereby interconnected. The interconnection offers the possibility for end customers to use the same login on various websites (see also 4.6 Registration). A newly set up website will be allocated to exactly one service area (1:1). Various websites can be pooled to one service area (1:n) on special request. Websites that are cared for by the same webmaster may be allocated to different service areas. The backend tool recognises the service area of a website automatically by the website ID submitted. To use payment transaction it is necessary to define services. Services are specified by their transaction type (single transaction, subscription) and a content category (i.e. logos, ringtones, or similar). The services are registered once per content provider. Once a service is registered it can be used on all registered websites of the content provider. Subscriptions use the same service IDs for all registered websites but get distinguished by the website ID. This ensures that a subscription that is concluded on one website does not trigger a subscription on another website, even though the same service ID is used. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 13 of 25
Service area 1 ( MSISDN - Password 1) Service area 2 ( MSISDN - Password 2) Website 1 Website 2 Website 3 Service 1 ( Subs. 4,99 Logos 1x / week) Service 2 ( Subs.1,99 Video 1x / month) Service 1 ( Subs. 4,99 Logos 1x / week) Service 2 ( Subs. 1,99 Video 1x / month) Service 1 ( Subs. 4,99 Logos 1x / week) Service 2 ( Subs. 1,99 Video 1x / month) Webmaster 1 Webmaster 2 Service provider 4.6. Registration Web Payment supports the automated registration of end customers on our system. An end customer needs to register at the whatever mobile system as requested by the content provider. The end customer is identified by his MSISDN. The content provider can submit the MSISND either in the format of 004917x or 017x to the interface. In order to register himself, the end customer receives a six-digit numeric PIN from whatever mobile, which he identifies himself to the content provider with at the whatever mobile infrastructure. The MSISDN and the corresponding PIN are the login details for the end customer. An initial registration activates the login and is mandatory for some ordering types. The end customer can amend the generated PIN with an according request from the content provider to the WMPay interface. In case the end customer cannot remember his PIN, it can be reissued to him via SMS. All cost incurred for SMS-MT messages sent within the registration process are charged to the content provider as laid out in the order sheet. 4.7. Fraud prevention mechanisms In order to prevent fraud, WMPay expects the submission of corresponding IDs and passwords for each request, which identify the requester distinctively. The utilisation of order functionalities without TAN is only possible, if the end customer registers with the password generated by WMPay. Orders without prior login are only possible when a TAN is used. This process prevents the utilisation of the services by third parties, which may not own the SIM card to the corresponding MSISDN. The number of deliveries for subscription and single transactions is limited. (see 4.3 Delivery) 4.8. Special revenue shares in the networks of Telekom, Vodafone, o2 and debitel In the networks of Telekom, Vodafone, o2 and debitel the payout amount depends on the service offered. The services are distinguished between web-based or mobile-based content. Basically, all services offered can be considered as mobile-based content. Especially, the services as follows are mobile content: Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 14 of 25
ringtones, logos, wallpapers, mobile games, mobile videos mobile navigation tools mobile TV SMS chat According to the definition of web content by the network operators/service providers stated above, web-based content are digital products that are not developed specifically for the usage on a handset and are not used in particular on a mobile handset. Exemplarily, Telekom refers to the following services as web content: editorial premium content (PDF files, test reports, prefessional articles) access to websites downloads of MP3s or of software web portals (partner market, premium functions) online TV At any rate, the service needs to be authorised by the mobile network operators/service providers to acquire the special revenue shares. Thus, this interface can be used only on special request and needs to be implemented separately. In the mobile network of o2, special branding guidelines need to be adhered to acquire the special revenue shares. Please see the National Regulations Germany for further details. For the billing of end customers in the network of Telekom, whatever mobile acts as the content provider for all value-added services that are ordered by the end customer through the internet. The CP offers concepts for telephone-related services to whatever mobile. whatever mobile appoints the CP as its vicarious agent with the supply of the services as ordered by the end customer. The CP ensures that the services are carried out to their full extent and according to the current scope of services and the current National Regulations. The CP passes all rights of the service to be provided to whatever mobile. The CP declares that the content, which is forwarded by himself to whatever mobile does not violate any law and/or rights of third parties (in particular copyrights, trademark rights, patent rights, personality rights or other protected rights of any third party). Further, the CP allows whatever mobile to act as content provider for the services provided to the end customer of Telekom Germany GmbH. Therefore a contract relationship is only established between the end customer of Telekom and whatever mobile. The CP receives a revenue share, which is dependent on the usage. The revenue share is granted for providing the services in whatever mobile s name and is paid as laid out in the current price list. Only those transactions that were successfully factored by Telekom, Vodafone, o2 and debitel and on whom whatever mobile received revenue share, will be paid out to the CP. 5. Scope of services Voice Payment 5.1. Functionality whatever mobile registers short codes capable for voice services with the mobile network operators. Please note that the approval of the short code chosen may be delayed by the network operators. The provision of the short code by whatever mobile is no provision in terms of 66 Telekommunikationsgesetz and 20 Telekommunikations-Kundenschutzverordnung. The assignment of the short code depends on the discretionary of the mobile network operators. whatever mobile orders the short code and the services to be offered according to the particular service description. Only after assignment of network operators, the services may be provided. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 15 of 25
The short code is forwarded to (a) domestic German number/s provided by the CP. There are up to ten domestic numbers that may configured per network operator. whatever mobile forwards incoming calls to the number(s) provided and charges them to the CP. Currently; whatever mobile offers the exclusive usage of voice short codes only. Basically, the charging of the services offered on the voice short codes is carried out depending on the duration of connection and according to the end customer tariff set up. Only those payouts distributed by the mobile network operator to whatever mobile are of crucial factor. The charging of event-based services on voice short codes is in preparation. Generally, MO video calls can also be reveiced on voice short codes. This functionality is not warranted by the mobile network operators. Due to technical restrictions, video call inbound services are not possible in the network of E-Plus. In the network of Telekom, the forwarding of video calls is only available using the Voice Access model. 5.2. Realisation of special regulations of the mobile network operators When using the product Voice Payment, please note that the CP needs to meet the National Regulations and any subsequent technical requirements in full. Especially, but not solely, the legal regulations of the TKG (e.g. 66b price announcement ) need to be fulfilled. Please see National Regulations for further legal requirements. 5.3. Charging of Voice Payment services Incoming calls on voice short codes are forwarded to domestic numbers operated by whatever mobile. Thereupon, the calls are forwarded to the technical systems of the CP who provides the service. Due to this interconnection, whatever mobile is able to monitor and record the call time on the particular domestic numbers. Furthermore, whatever mobile is able to charge the payouts towards the mobile network operators, respectively check the correctness of their invoices / credit notes. 5.4. Price announcements Basically, the end customer tariff per minute needs to be announced on the particular voice short code three seconds before the end customer initially gets charged. whatever mobile offers price announcement files on request. The fees for an individualisation of price announcements are charged to the CP based by prior agreement. For all services with an end customer tariff up to 1.99, the price announcement is carried out by the CP. For services with an end customer tariff of 2.49 or 2.99, the price announcement is made by O 2. 5.5. VideoCall functionality in the network of O 2 In the network of O 2, VideoCall services with an end customer tariff of 2.49 or 2.99 are not available. 5.6. Pulsing Inbound calls on voice short codes are charged differently to the end customer by the mobile network operators depending on the particular pulsing. Also, the payouts are made according to the pulsing. In the networks of Telekom and E-Plus the charging bases upon a 60/1 pulsing, while in the networks of Vodafone and O 2 the charging bases upon an 1/1 pulsing. Any processing fees charged to the CP also base upon the gross end customer turnover and the pulsing of the particular mobile network operator. 5.7. Bill warnings According to the regulations of the mobile network operators, a bill warning SMS free of charge needs to be issued when reaching a gross turnover of 20.00 or a multiple. The service provider is obligated to deliver those bill warnings to the end customer. To be able to issue bill warning SMS, the set-up of a logic Mobile Message Account at the technical systems of Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 16 of 25
whatever mobile is necessary. All cost incurred for SMS-MT messages sent within the bill warning process are charged to the service provider as laid out in the order sheet. 5.8. Forced disconnection To protect end customers from any misusage, the TKG demands an automatic forced disconnection when reaching a call time of 60 minutes. This disconnection is carried out by whatever mobile. 5.9. Particularities in the network of Telekom The mobile network operators offer two different products to provide voice services. Using the Voice Access model, the service provider does not receive any payouts. However, the end customer is charged a transportation fee which needs to be communicated. In the future, the Voice Access model may also be used for event-based services. The Voice Factoring model can be used for time-based payment services. The transportation fee is included in the total end customer price. Voice short codes that are used within the Voice Factoring model, cannot be used for inbound Video Calls. A combination of Voice Factoring and event-based charging is not allowed. 5.10. Minimum payout O 2 In the network of O 2, the minimum payout per voice short code and per month is 1,000.00. If this payout is not reached, no payout of the revenue share generated will be issued. 6. Scope of services Application Payment To offer Application Payment, whatever mobile uses the technical logics of SMS Payment and the payment interfaces of the mobile network operators. Basically, the payment transaction is initiated by the end customer using an application or any other data medium on his mobile device. E.g. Application payment may be used for the charging of licence fees or additional features or contents. Thereupon, the service provider sends a request to the payment platform of whatever mobile. According to the particular service parameters, an SMS handshake is issued. If the end customer confirms his order, the payment or the subscription is approved and whatever mobile delivers the content, if applicable. The service provider receives a notification on the successful payment transaction. Please see SMS Subscription Payment for further scope of services (3.3). Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 17 of 25
7. General functionalities and services 7.1. Bill warnings and information SMS Bill warnings are information for the end consumer that are automatically generated by the Mobile Payment system of whatever mobile, when certain turnover limits that were set by the mobile network operators and mobile service providers, are reached by the end customer. End customers of E-Plus, O 2, and of the mobile service provider Victorvox also receive an information SMS when a subscription is concluded. The content of bill warnings and information SMS is designed according to the specifications of the mobile network operators. The cost incurred by such messages are billed to the content provider according to the order sheet. 7.2. Individualised handshake messages whatever mobile supports the individualisation of handshake texts. The contents of those handshake texts need to be designed according to the requirements of the network operators and the legal regulations. In the networks of Vodafone and O 2 special interfaces need to be used to be able to issue individual handshakes. Particularly, the usage of the special interface of Vodafone requires the setup of a separate Vendor ID per service (e.g. also per URL). The fees for these Vendor IDs are passed on according to the order sheet. To use those interfaces, a particular assignment and technical implementation by the network operators is necessary and may incur additional costs. The content of handshake messages and information SMS is designed according to the specifications of the mobile network operators. The cost incurred by such messages are billed to the content provider according to the order sheet. 7.3. Optional prevention of duplicate orders The Mobile Payment system recognises whether the same MSISDN already holds a subscription. In such cases the system sends an SMS to the end customer notifying him that the subscription is not possible. In order to offer credit subscription services, the repeated ordering can be forwarded to the CP if required. This functionality allows the content provider to detect that the end customer would like to receive content for his prepaid credits. 7.4. Forwarding of the MSISDN to the CP whatever mobile supports the forwarding of the end customer s MSISDN to the content provider as allowed by the mobile network operators / mobile service providers. This functionality enables the content provider to run his own statistics, support the consumers in their enquiries and offer additional services within the legal framework. The forwarding of the MSISDN is mandatory in order to realise credit subscription services, since the CP needs the MSISDN to know which credit account the content ordered needs to be charged to. 7.5. Pre-check whether an MSISDN can be billed The pre-checking whether an MSISDN can be billed prevents the delivery of content to the end customer, when the end customer cannot be billed. This functionality is only available if supported by the mobile network operators. If a prepaid customer orders content while his prepaid funds are not sufficient, the delivery would be cancelled by the system. This functionality cannot be offered for customers of E-Plus or Victorvox, since their MT-billing procedure does not allow this technically. 7.6. Forwarding of billing results whatever mobile informs the CP of the status of a payment transaction and the associated delivery of content by forwarding the billing results. Detailed error messages allow the CP to realise why a delivery was not successful. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 18 of 25
7.7. Processing of re-authorising and re-billing The whatever mobile platform initiates an automated repetition if the billing pre-check or the billing itself failed. This may happen if an end customer does not have sufficient funds on his prepaid card or if the content could not be delivered because the end customer s device was switched off and the content could not be billed. The number of re-billings and their time intervals depends on the regulations of the mobile network operators and mobile service providers. These parameters can be set to individual requirements, if necessary. 7.8. Optimising of content of automated messages whatever mobile optimises automated messages to the end customer according to the regulations of the mobile network operators and services providers to ensure that the end customer receives clear information and gets led to the conclusion of the contract without complications. 7.9. 3 rd party consumer support whatever mobile offers the Client Control Center for administering end customer s subscriptions of payment products. This tool can be used to contract external call centers with the consumer support without granting them access to any other functionality. 7.10. Maintenance Reply In case the contractual partner connects to whatever mobile with one of the following protocols UCP, SMEP, http or SMTP (see Connection methods ) he has the possibility to reply to each incoming message automatically, i.e. when maintenance work is carried out on the system. Incoming messages are not forwarded but trashed. This functionality can be activated or deactivated via the CCC once the feature is enabled. Further, it is possible to schedule maintenance work for a predefined time window. The reply message can be worded individually. 7.11. Debt claims towards end customers The CP authorises whatever mobile to enforce judicially as well as extrajudicially any debt claims towards end customers on whatever mobile s own behalf for services provided via the technical interfaces of whatever mobile. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 19 of 25
8. Connection methods Depending on the product, various protocols and tools can be used to connect to the infrastructure of whatever mobile. Both, our technical documentation, the whatever mobile Mobile API Specification and our technical support team (see Technical Support) are at the CP s disposal. SMS Feedback Tool SMS Single Payment - EMI/UCP EMI/UCP (SSL) SMS Single & Subscription Payment - MMS Payment Web & Payment http http (SSL) SMTP MM7 (http-based) SMS/Web: https Webservice Method of connectio n Via access to the Client Control Center of whatever mobile Via protocol Connection via the technical systems of the CP Via protocol Connection via the technical systems of the CP Via protocol Connection via the technical systems of the CP Via protocol Connection via the technical systems of the CP via protocol Connection via the technical systems of the CP Advantages Easy to use Protocol based connection not necessary Standard protocol of the network operator Suited for high volumes Simple to monitor SMS Outbound SMS Inbound SMS Outbound SMS Inbound MMS Outbound MMS Inbound MMS Outbound MMS Inbound whatever mobile Payment Interface to realise services that require a connection to the billing systems and further functionalities Please note! SMS Broadcast Tool: Delivery Notifications are not available Complex, requires extended programming skills Only usable for SMS Widely used Easiest connection Widely used Easiest connection Possibility to send messages from the email client Standard protocol according to 3GPP Widely used Easy connection Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 20 of 25
9. Client Control Center The CP gets access to our Java Virtual Machine (JVM) based Client Control Center (CCC). Through the CCC the CP can access various analysis and statistics and configure his connection to whatever mobile. In order to access the CCC to its full potential, whatever mobile provides extensive manuals to the CP. The scope of services offered in the CCC is depending on the solution that was chosen by the CP. When additional products are chosen from the product portfolio of whatever mobile the scope of services within the CCC may increase. The following functions are available at the time of setup: Change of password Since each usage of the CCC is allocated to the CP after he authenticated himself with his login and password, all passwords and logins need to be stored in a safe manner. whatever mobile recommends changing passwords on a regular basis by using the option Change password. Search for messages The CP can check which message was sent to or received from which MSISDN, by using the search for messages tool. Further, the CP can check the message texts as well as the log time. Operator statistic The CP can access a detailed breakdown of how many messages were received from which network or were sent to which network via his whatever mobile Message Account by using the operator statistic tool. Account statement All credits and debits (i.e. termination costs or processing fees) are usually booked on the client s account in real time in order to enable the CP to keep up to date on his account statement. The time frame for the account statement can be chosen individually. Keyword statistic If the CP receives messages via a keyword, he also gets access to the keyword statistic. The success of a keyword can be monitored individually or as a whole. The keyword statistic offers various time levels, and therefore offers insight into the time of the day when the CP s services get used most often. Further, the keyword statistic offers statistics on new customers and on the average number of SMS/end customer (=MSISDN). Keyword administration If the CP receives messages via a keyword, he also gets access to the keyword administration. The keyword administration allows the CP to reserve, order and amend (depending on the application) keywords on short codes already registered to him. After the request was submitted to whatever mobile successfully, the request needs to be approved by whatever mobile. This procedure whatever mobile! Requests are processed by whatever mobile Monday to Friday 9 am to 5 pm. Especially for orders for weekends the CP needs to schedule his requests accordingly. Search for transactions The search for transactions is a tabular statistic of all transactions processed by whatever mobilepay during a definable time frame. Individual transactions may be monitored by transaction ID or an end customer s MSISDN, to detect errors and offer high quality end consumer support. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 21 of 25
Customer statistics The customer statistics analyze all transactions processed by whatever mobilepay within a definable time frame. The analysis can be based on turnover or on the number of transactions. Further, a selection per MNO or billing type can be used. Subscription support form The subscription support form offers information on all concluded, active or terminated subscriptions within a definable time frame. Further, the service provider can terminate subscriptions here manually. When a subscription is terminated, a confirmation SMS may be issued to the end customer. The subscription support form is only available for SMS Payment. When using Web Payment, the management of the subscriptions is the duty of the service provider. 10. Fees 10.1. Set up fees, operation fees and transaction fees All fees, whether for set up, operation or subject to transactions, and the revenue shares are specified in the order sheet. When deciding on the set up of an exclusive short code, the contractual partner selects the mobile network operators and service providers that are to be used. Set up fees and monthly operation fees are due per short code and mobile network provider/service provider. If some networks are not to be used, this will decrease these fees accordingly. Set up fees and operational fees of whatever mobile are charged independently from the fees mentioned above, and do not depend on the number of networks connected. Shall the mobile network operators increase their fees; whatever mobile will communicate this to the contractual partner immediately. whatever mobile charges a processing fee for the receipt of necessary messages (SMS-MO). Further, a fee is payable for the termination of all outgoing messages (SMS-MT). 10.2. Volume discount When more than one short code, long number or keywords are to be set up, volume discounts are possible, which will be forwarded on to the CP. If multiple set-ups are required, please contact our sales department in order to check the possibilities for volume discounts. 11. Special regulations and requirements 11.1. Compliance to the National Regulations The CP ensures to communicate all cost that may be incurred by the end customer by the usage of his short codes explicitly, visually clear and in a manner that is understood by the end customer. Further details regarding advertising guidelines for Germany and the contractual penalties resulting from non-compliance to them, are lined out in the National Regulations, which also form part of the contract. 11.2. Description of a service The MNO and service provider must approve each payment service in advance. The service description must be submitted by the CP to whatever mobile prior to the start of the service. whatever mobile does not guarantee the approval of a service by the MNO or service providers. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 22 of 25
11.3. End consumer hotline The CP must name a hotline number, which is reachable from Germany on working days during office hours. whatever mobile will forward any end consumer to this hotline for their enquiries. Further, the CP must provide a fax number and email address to which end customers can address their enquiries. 12. Technical support whatever mobile offers a round the clock technical support, in order to be reached by his CPs in case of any technical problems. If the technical problem is caused by an error in the infrastructure of whatever mobile, the CP will not be charged for the support time. In order to support the CP in connection with new setups of SMS and MMS products, three trouble tickets will be issued free of charge. These can be used on working days during normal office hours and within 30 days after the contract is signed. In all other cases whatever mobile s support is subject to a fee. Support - Per support event (incl. 20 min talk time): 59.00 - Further support time: 29.00 / 10 min. Support telephone: +49 (40) 88 88 08 88 Support email*: support@whatevermobile.com *Email only applicable during normal office hours. Outside of our office hours, please contact our support team by phone! Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 23 of 25
13. Glossary Term Meaning Explanation Billing Successful booking of billing transactions in the billing systems (i.e. at the network operators or at whatever mobile) CCC Client Control Center Administration and statistic tool of whatever mobile Content provider Contractual partner Is responsible for the content and functionality of a (mobile) service. Usually the provider of the services. He purchases services of whatever mobile. dedicated exclusive I.e. the exclusive usage of a short code, so that all incoming SMS / MMS will be forwarded to the contractual partner s message account Delivery Type Device Determines the internal routing at the message gateway of whatever mobile I.e. mobile phone or PDA IP address Internet address I.e. 111.110.12.58 Keyword Is used to allocate incoming messages to a Message Account or to the applications of the contractual partner MMS Multimedia Message Service Mobile message service for transmitting bigger and more complex messages. The end customer does not (!) need to pay for the receipt of MMS. MMS short code Short code, i.e. 12345, to which MMS can be sent MNO Mobile network operators Owns a license for operating a mobile network including all necessary network components. MO-MMS Mobile Originated MMS MMS sent from the end customer (device) MO-SMS Mobile Originated SMS SMS sent from the end customer (device) MSISDN Mobile Subscriber Integrated Services Digital Network Number Also called mobile number MT-MMS Mobile Terminated MMS MMS sent to the end customer (device) MT-SMS Mobile Terminated SMS SMS sent to the end customer (device) MVNO Mobile Virtual Network Operator Message Uses the infrastructure of an MNO in order to operate an own mobile network. He also maintains own active network components (i.e. Virgin Mobile in the UK) A message can consist of various SMS Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 24 of 25
Premium numbers Routing Numbers to which SMS or MMS can be sent. Messages sent to a premium number are usually charged at a higher (premium) rate than messages, which are sent to another mobile phone Refers to the sending of SMS/MMS via special connections (i.e. via foreign network operators) Service Provider Shared Uses the infrastructure of an MNO in order to operate an own mobile network. He does not maintain own active network components (i.e. Talkline) Shared use of existing short codes / long numbers via keywords SMS Short Message Service Short message, up to 160 characters SMS short code SMS long numbers Short code, i.e. 12345, to which SMS can be sent Long numbers, i.e. 0176-888 00 88, to which SMS can be sent SMSC Short Message Center Each network operator maintains an own SMSC in order to send and receive SMS. On the SMSC i.e. short codes are registered. The SMSC are the interface of whatever mobile into the respective mobile network. Termination Sending of SMS to a device (mobile phone) vsmsc Virtual Short Message Center Various service providers maintain their own vsmsc, on which i.e. short codes are registered. The vsmsc are the interface of whatever mobile to the respective service provider. Author: PM D Mobile Payment v4.0.doc from 29/06/2011 Page 25 of 25