3.4Postback service
Please note that the Postback service only is activated (manually by WyWallet) when the merchant needs high performance (e.g. tv voting) and the merchant account is configured as an Asynchronous account. The default setting for a merchant account id Synchronous where postbacks are not used.
In order to receive a receipt from an asynchronous request (transaction), each merchant (or aggregator/PSP) must implement a Postback service.
The WyWallet MAP system will send out payment status as soon as the transaction is processed.
The system will send an ordinary XML over HTTP POST over SSL with a single parameter named PostbackRequestWrapper that contains an XML document (se example below).
We strongly recommend you to verify the MAC code in the XML using your shared key and the submitted data to authenticate the request before delivering the purchased service/goods.
PostbackRequestWrapper
Header -> see section 3.1.1
PostbackRequest ->
Footer -> see section 3.1.3
PostbackResponseWrapper
Header -> see section 3.1.1
Status -> see section 3.1.2
3.4.1PostbackRequest
Name
|
Type
|
Description
|
Mandatory /
Optional
|
Operation
|
String (30)
|
Specifies the operation. One of
|
Mandatory
|
OrderID
|
String (60)
|
OrderID of the original request
|
Mandatory
|
TransactionID
|
String
|
Payment transaction ID
|
Optional
|
BatchID
|
Int
|
ID used for reconciliation, stored on all financial transaction. The batch ID is changed on regular intervals, typically once per day.
|
Optional
|
Amount
|
Int
|
Amount of money (cent/öre) to reverse, including VAT
|
Optional
|
MAC implementation:
The MAC sent in the footer of the XML document is computed the same way as in the requests. The following parameters are used to compute the hash:
AcquirerID+AgreementID+TransmissionTime+ PostbackURL+ Operation+ OrderID+SharedSecret
|
The post back service should validate the MAC sent by the MAP service to protect against fraud.
Sample PostbackWrapper XML sent by MAP:
string
string
string
string
string
string
int
string
string
int
int
string
string
string
The Postback service should return an XML document in the HTTP BODY in the response to acknowledge that the postback XML has been received. Sample reply message:
string
string
string
string
string
0
OK
0
OK
4ProductID
This is the list of valid productID:s that needs to specified for each purchase. The productID are used for end-customer that has selected payment method is via the operator subscription and these productID will render specific descriptions on the invoice.
Product id
|
Description
|
1
|
Lottery
|
2
|
WiFi
|
3
|
Personal Ring Back Tone
|
4
|
Tickets
|
5
|
Business
|
6
|
Charity
|
7
|
Parking
|
8
|
Ring Back Tone
|
10
|
Charging
|
12
|
Auction
|
13
|
Vending machine
|
14
|
Adult content (All adult content regardless of type)
|
15
|
Positioning
|
16
|
Security product
|
17
|
Mobile Entertainment (Music, Music videos, Games, Wallpapers, animations, Themes, Videos)
|
18
|
News (Access to news sites or content bought on a news site)
|
19
|
Mobile TV (Mobile TV services)
|
20
|
Applications (software for mobile, any applications that don’t fall under any other categories. Includes content bought through a free application, for example an audiobook client)
|
21
|
Voting (Voting for TV shows or other competitions)
|
22
|
Betting & gambling
|
23
|
Classified ads
|
24
|
Mobile marketing
|
25
|
Internet Portals (Access to Internet portals that is not news, community or adult)
|
26
|
Chat (Chatting services, for example dating chats)
|
27
|
Personal ad (Dating ads, contact ad, dating-sites)
|
28
|
Location Based Services
|
29
|
Information Service (Charging for weather services,snow reports etc)
|
30
|
Coupons (For example mobile gift vouchers (ice cream, magazines etc))
|
31
|
M-Payment (For example e-school, mobile dictionaries etc)
|
32
|
Physical goods (Physical goods like, books, drinks, food etc)
|
Share with your friends: |