V1
Add a bank card
2.1 Send the details of the card registration request to the S-money server
To add a bank card, these are the mandatory parameters : "card", "appcardid" and also "urlReturn".
These are the optional parameters "name", "availableCards", "extraparameters", "profilename", and "systempaylanguage".
Please have a look at the example in the right margin of this page.
The "href" parameter includes the url, to which the third-party application should redirect the client’s browser to complete a card registration.
2.2 Send the details of the card registration to the third-party server
The third-party server should provide the S-money server with an url server allowing the S-money server to communicate the result of the payment execution.
The HTTP POST method is used to invoke the S-money server
These are the HTTP request parameters :
| Parameter | Type | Description |
|---|---|---|
| id | Long | Card ID |
| error | Int | Error code for failed card details, 0, if no errors. 1 = The merchant should contact the bank of the holder 2 = Payment refused 3 = Payment cancelled by the client 4 = Holder not 3D-Secure enrolled 5 = 3D-Secure authentication error 6 = SystemPay technical error |
| type | Int | Operation type 5 =card registration |
| userid | String | User identification in the third-party application |
2.3 Redirection at the end of a card registration
The third-party server should provide the S-money server with an url allowing the S-money to redirect the client to the third-party environment.
The url can be either associated to a web scheme (http/https) or a private scheme when a request is made by a third-party mobile application.
The HTTP POST method is used to invoke the S-money server.
These are the parameters of the HTTP request :
| Parameter | Type | Description |
|---|---|---|
| Id | Long | Bank card ID |
| Type | Int | Operation type 5 = card registration |
| Result | Int | Transaction status 0 = Error 1 = O |