WyWallet
WyWallet SMS Payment API Version 0.4
Issued 2017-01-05
Table of contents
1Introduction 4
1.1Purpose 4
1.2Requirements 5
1.3Definitions and abbreviations 5
2API - Overview 6
2.1WSDL URL 6
2.2Method overview 6
2.3Synchronous Payment overview 7
2.4Asynchronous Payment overview 8
3API – details 8
3.1General 8
3.1.1Header 8
3.1.2Status 9
3.1.3Footer 10
3.2 Status codes 11
3.2.1Transaction status codes 11
3.2.2Operation status codes 14
3.3SmsPaymentService 15
3.3.1Purchase 15
3.3.2Reversal 18
3.3.3Credit 20
3.3.4CheckOrder 21
3.3.5Ping 23
23
3.4Postback service 24
3.4.1PostbackRequest 24
4ProductID 26
5Appendix A 27
5.1Hash description 27
5.1.1SHA1 Hash .Net 27
5.1.2SHA1 Hash – JAVA 27
5.2Postback service examples 31
5.2.1Java JSP postback 31
5.2.2ASP.net postback service 32
6Appendix C: Simulator for API development 33
6.1URL 33
6.2Valid request parameters 33
6.3Response codes 33
6.4Frequently asked questions 34
6.5Merchant support 35
Version history
Version
|
Date
|
Comment
|
Name
|
0.1
|
2012-07-25
|
First draft
|
Jonas Jansson
|
0.2
|
2012-07-27
|
General updates, added payment sequence diagrams
|
Jonas Jansson
|
0.3
|
2012-08-28
|
Updated simulator and postback examples
|
Jonas Jansson
|
0.4
|
2012-11-13
|
Fixed error in MAC calculation for credit/reversal.
Updated transaction statuses.
|
Jonas Jansson
|
1Introduction 1.1Purpose
This document (WyWallet SMS Payment API) describes how merchants, content providers and aggregators can implement the functionality for premium SMS (and other CPA services) payments via the end-user WyWallet account.
This API is a Server-to-Server API built on the operating system independent technology webservices and the API is very similar to the WyWallet Online Payment API which is more targeted for Web/Mobile Web and “in-app” payments. Online payments have higher security and therefor also has higher amount limits. There are also some technical differences between the interfaces:
-
SMS payments only supports 1 phase billing and Authorize / Capture are combined in the same request, purchase().
-
The SMS API only requires MSISDN (phone number) to identify the account and no end-user interaction is needed to authorize the payment.
-
Only the SMS API allows end-customers to use the mobile invoice or prepaid subscription as payment method.
There are two different merchant account types (configured by WyWallet), synchronous and asynchronous payments.
-
Synchronous (Default)
-
Asynchronous
-
Asynchronous requests are used for merchants with very high performance requirements
-
All payments requests are accepted but set in an unconfirmed payment status and put in an internal queue for further processing.
-
When the payments are processed the final status of the payment is sent in a XML to the merchant using HTTPS POST to the postbackURL set in the initial request.
-
The post-back requires the merchant to implement online receiver / listener..
-
Please not that all post-backs are sent via HTTPS/SSL and that you therefore need a SSL certificated installed (from a trusted CA e.g. www.thawte.com or others)
The MAP service will perform a lookup and identify the operator and preferred account.
This service is based upon an asynchronous design.
This means users of the API must implement a “postback service”, in order to receive the final transaction status. The “postback service” is based on HTTP POST and XML.
In periods of high load and lengthy operations, the response is asynchronous.
1.2Requirements
Share with your friends: | 
