1. Browsing user presses the link that directs user to the Vero system's service purchasing environment.
2. The user is asked whether he agrees to pay for the service.
3. After user agrees to pay Vero system charge money from user.
4. About successful payment Vero system informs partner via link (URL) that now has additional payment parameters.
5. The user is returned to the partner site.
The service is used to pay for services via mobile Internet. If user is connected via Wireless he won't be able to pay for the service - the system does not recognize the user's phone number and can not charge the money.
We recommend to use an identification service before registration or when user visits partner's project. This way you can find out detailed user information (country, language, operator, phone number and so on.), and you will be able to form a payment page.
More about identifying users read in "User identification"
Operator Telia Lithuania users, while trying to make a payment, falls in standby site with the info text: "We are trying to charge. After you get an SMS, press this link: proceed >>". The user gets a successful payment message with the service name and a link to a paid service. Even if user leaves one-click service page, he can proceed with the registration by clicking a link in the SMS.
If the partner receives a billing errors, but they are not processed correctly (HTTP status is not 200), a Telia Lithuania Consumers billing will not work.
1. FORWARDING USER TO VERO SYSTEM
To charge the user, it must be directed to the Vero system's address http://bill.vero.lt/wap/register with the formed GET parameters:
Example of address where the user will be redirected (it is used signature security password "test"):
http://bill.vero.lt/wap/register?session_id=debaf588e8ebadfe97a6ae38ff95beef&after_register=yes&
s=2&si=&i=1255530969&u=http%3A%2F%2Fmbs.vero.lt%2Fsimple%2Fwap_register.php&s1=01cb763307dd28851
f8ccf3192b5fcbfd8ccd858
In addition you can add any number of parameters. Later they will be added to the address to which user will return to the project, together with payment information. However, parameters can not be with these titles: 's', 'si', 'i', 'p', 'pc', 'u', 'un', 's1', 's2', because these parameters are used to transfer the main information.
In order to avoid double payments, it is not enough just to generate a payment link, when the purchase button is pressed. In this case, pressing the same button 2 times in a row, you will generate 2 different purchase requests, and they both will be paid. We recommended that the purchase button would be generated as the unique purchase link with a unique parameter i.
If you are using a WAP purchase initiation via SOAP, a detailed definition how to start the purchasing event see in "Remote method description" page.
Single-payment/register GET parameters to make a request to Vero system
Title |
Type |
Mandatory |
Description |
Example |
s |
int |
yes |
Service ID |
2 |
si |
string |
no |
User identificator in subscription service (eg. nickname).
Can be used, if same user can register to the service
with different accounts. |
- |
i |
string |
yes |
External system unique identifier that describes the ongoing payment event (transaction). Parameter also is used to avoid double payments, thats why it should be unique each time for the service or at least for the user. If you do not save payment events in your side, you can specify the time when link was generated. |
1255530969 |
p |
int |
no |
Registration (first period) price, indicated with cents. It is required when registration has several prices. |
- |
pc |
string |
no |
Registration currency (ISO 4217 standard). Required when indicating parameter p. |
- |
u |
string |
no |
Encoded ( urlencode ) URL, where the user should be redirected after registration. If this parameter is not indicated, user will be redirected to service URL, indicated during creating service. |
http%3A%2F%2F mbs.vero.lt%2F simple%2Fwap_register.php |
un |
string |
no |
Encoded ( urlencode ) URL, if user should be directed to other link after unssuccesful registration. If this parameter is not indicated, user will be redirected to service URL, indicated in parameter u |
- |
s1 |
string |
yes |
Security signature (lower credibility) |
- |
2. RETURNING USER TO PARTNER SYSTEM
So after a successful or an unsuccessful registration user will be directed to the service address. There will be attached those parameters that external system has requested during event.
Example (there is a password „test“ used in security signature):
http://mbs.vero.lt/simple/wap_register.php?session_id=debaf588e8ebadfe97a6ae38ff95beef&after_reg
ister=yes&s=2&si=&sr=active&srs=active&i=1255530969&t=2331494&a=1&s1=dfbb0af21a09516b73946bb9945
8499f1ef6b081&s2=HpwXNO%2Fr5Yhd3g00yIeHKEnZsuYJ7UdGTHnj06n5T%2FJQ%2BDGZG8tPaMYH6rCI9Febv8UDtNgQL
eXi7h21diQUxEirxNjb1AqdvSOi%2FbO3IqCvuvGS65t7EIom5E9tGL77wdtorKpwgNkbfszQAgBEjard7scWiwt0Jbhut9E
CDik%3D
Title |
Type |
Mandatory |
Description |
Example |
s |
int |
yes |
Registration service ID |
2 |
si |
string |
no |
User identifier in subscription service (eg. nickname). Is used if user can register to the same subscription many times with different identificators. |
- |
sr |
string |
yes |
Main subscriber status (status), which indicates user activity in subscription. You can find a list of all possible values in "Subscriber status" |
active |
srs |
string |
yes |
Additional subscriber status (state), which specifies a reason of failed payment. You can find a list of all possible values in "Subscriber status" |
active |
i |
string |
yes |
External system unique identifier that describes the ongoing payment event (transaction). |
1255530969 |
t |
int |
yes |
Unique identifier of payment event (transaction) in MBS system. |
2331494 |
a |
int |
yes |
Unique identifier of successfuly billed user in MBS system (account_id) |
1 |
s1 |
string |
yes |
Security signature (lower credibility) |
- |
s2 |
string |
yes |
Security signature (highest credibility) |
- |
Attention!
It is necessary to check security signature after user comes back to service address (parameters 's1' or 's2'). This ensures that an appeal was made by the MBS.
It is necessary to check subscriber status (parameters 'sr' or 'srs'). This ensures that user will not get service for expired registration.
After user gets back to the site you can check whether or not the same user is registered and browsing the service (the parameter 'a'). This ensures that you will not provide service even after imitating foreign registration return.
EXAMPLE (REFERENCE LIBRARY)
PHP library used to connect to the Vero system, you can download here: MBS library