1Pay - Quick Connect, Pay Flexible | SMSplus Payment Policy

Payment Policy

News, company info, and communications

REGUALATIONS ON THE POLICY OF SMS PLUS SERVICE

ARTICLE 1: TERMS

-       SMS plus Charging: Party A shall provide Party B with the Payment Gateway to connect with content charge of Game services and Social Network, etc. The payment amount will be credited to the bill (for postpaid subscribers) or deducted directly on the main account (for prepaid subscribers) of client's mobile phone number.

-       First digit: 9029

-       Payment methods:

o   Payment according to each transaction.

o   Cyclic automatic payment (subscription): after charging extension, notification message will be sent to clients.

-       Payment channels: 3 payment channels

o   SMS MO: Clients send a message with the specified syntax to service first digit (9029) to make a payment.

o   Website (SMS OTP): When clients request to payment through mobile payment gateway of Telcos, they will receive transaction authentication code (OTP) via SMS. Clients enter the OIP code correctly on the website to make transaction payment.

o   API: It's similar to make a payment via the website but the entire payment process will take place entirely on the system of Party B (website, wapsite, client). Party B will be provided an API to integrate into its system.

-       MO message (Mobile Originated): is a message sent from clients using the Service.

-       MT message (Mobile Terminated): is a message sent to clients via the system of 1PAY. The MT messages are defined for each Service code on each first digit.

-       Charging data record (CDR): is the service bulletin that Party B provides for clients.

-       API (Application Programming Interface): is the Application Programming Interface

-       The ratio of permitted data difference: Temporary specified by 1%. The regular 06-month per time, Party A and Party B will consider adjusting this ratio to suitable with reality.

-       Error message: is repeated message (sent by the same number and the period of time between at the end of the previous messages and the beginning of the later message under 5 seconds) resulted in asynchronous fault between the SMSC of Telcos and Party A and the application system of Party B.

-       Network service providers: Party A is providing services of Mobifone and Viettel providers. As soon as the other network providers using this service, Party A will provide for Party B.

ARTICLE 2: CHARGE

v  Price unit charging from clients based on the distribution and regulation on MT (inclusive of VAT)

No.

Collection from client

(Inclusive of VAT)

(VND/ transaction)

Collection from client

 (Excluding VAT)

(VND/ transaction)

Price unit is paid for Party A

(Symbol DG Part A charged (With 01 MT free of charge))

Viettel

(60%)

MobiFone

(65%)

VinaPhone

(65%)

1

0

0

0

0

0

2

1.000

909

600

650

650

3

2.000

1.818

1.200

1.300

1.300

4

3.000

2.727

1.800

1.950

1.950

5

4.000

3.636

2.400

2.600

2.600

6

5.000

4.545

3.000

3.250

3.250

7

10.000

9.091

6.000

6.500

6.500

8

15.000

13.636

9.000

9.750

9.750

9

20.000

18.181

12.000

13.000

13.000

10

30.000

27.272

18.000

19.500

19.500

11

50.000

45.454

30.000

32.500

32.500

12

100.000

90.909

60.000

65.000

Not available

 

(The above price unit table may be adjusted in the collaborative process as required by the telcos)

v  Regulations on other costs

In addition, Party A and Party B will pay the other costs (if any) (Promotional costs of network providers if any, customer care costs, loss cost) according to charge control which Party B sends Party A monthly.

Therefore:

Total revenues of Party A DT A = DT + DT AVMS,AVTM, AVNP

In which:

·       Revenue from Viettel network provider

DT AVTM = CDR VTM x DG VTM A charged - Other expenses (if any)

·       Revenue from Mobifone network provider

DTAVMS = CDRVMS x DG VMS A charged Other expenses (if any)

·       Revenue from Vinaphone network provider

DTAVNP = CDRVNP x DG VNP A charged Other expenses (if any)

 

 

ARTICLE 3: REVENUE SHARING

Total revenue Part B charged is calculated by the following formula

Total revenue shared from cooperation services (DT)

(Not including VAT)

Portion of revenue

Party B charged (DTB)

(Not including VAT)

DT = DTA /1,1

DTB = TLB * DT

  In which:

+ DT: total revenue shared from services cooperated between the two Parties is calculated as the above formula.

+ TL B: the rate which Party B is entitled. TL B rate is specified as the list below:

a) In case of monthly payment cycle.

       No.

Total revenue shared from services

cooperated between the two Parties (million)

  Rate %

(TL B)

1

DT

88%

 

b) In case of 15-day payment cycle

No.

Total revenue shared from services

cooperated between the two Parties (million)

  Rate %

(TL B)

1

DT

87%

 

In which:

-       The revenue division rate can be adjusted on the collaborative process as required by the telcos, or agreement between the two parties.

 

ARTICLE 4: REGULATIONS ON FEES AND APPLIED SANCTIONS

            1. Regulations on applied sanctions

-       In the process of censoring content, if Party A discovers their partner sending a different or improper content with registration scenario to clients, party A will execute the applied sanctions by not making revenue division or may terminate the Contract.

-       With the partner violated the error content in excess of 10 errors per month: Cutting the service and liquidation contract.

-       The violated contents are prohibited contents such as predicting lottery's result, football betting, or content hot images/ stories/ clips The keywords are banned in both the code and the returned MT such as: SOICAU, LO, LODE, XOI, SOI, LOC, THAMKHAO, TUVAN, CAU, Pair of lucky number on a day/ month, CA CUOC, NONG, HOT, SEX, SEXY, SOCK, SOC, QUAY LEN, CHUP TROM, SHOCK, etc.

2. Regulation on content

General overview:

-       Party A shall manage command code on the command code script which the partner declared. The partner shall take full responsibility for detail content, and Party A will check again to compare with original script. In case of declared script is incorrect, sanction of no charging control will be applied and terminate the contract to prevent spam dissemination or bad content.

-       Contents provided by the partner must ensure legitimate, healthy, not violate the culture, habits and customs, as well as other provisions of the law. The partner must bear all responsibilities for any arising issue related to contents provided before legislation, public opinion and users.

-       Party A shall only approve command codes with detail content script.

-       If the partner meets the requirement of command code declaration without specific script, Party A can still refuse to provide service or fine content the partner.