updatePaymentMean

To search in the page use Ctrl+F on your keyboard

This function allows you to update one of the payment means contained in the client’s wallet. If the account or the payment mean do not exist, a 01 response code is returned. If the update works, 00 response code is returned and the date of update.

Recommended interfaceVersion: WR_WS_2.55

PROD

https://sherlocks-office-server.secure.lcl.fr/rs-services/v2/wallet/updatePaymentMean

method

POST
TEST

https://office-server-sherlocks.test.sips-services.com/rs-services/v2/wallet/updatePaymentMean

method

POST

PROD

https://sherlocks-office-server.secure.lcl.fr/services/v2/wallet?wsdl

method

POST
TEST

https://office-server-sherlocks.test.sips-services.com/services/v2/wallet?wsdl

method

POST

Request

Required

interfaceVersion
presence

Required

Interface version

2.0
Format
AN20(restricted String)
Version of the interface used. It is composed of a prefix that varies according to the function used and a version number (e.g. IR_WS_2.47).

Please refer to the function page for the value to use. Use the latest interface version number.

List of values

WR_WS_2.

WR_WS: Sherlock’s Office (SOAP/JSON) interface for Wallet functions.
keyVersion

presence

Required

Interface version

2.0

Format

N10

Version of the merchant’s secret key used to calculate the imprint of the message (key stored by the merchant to verify the imprint of the automatic and manual notifications).
merchantId

presence

Required

Interface version

2.0

Format

N15

Identifier of the shop, this value is provided to the merchant by Sherlock’s during the shop registration.
merchantWalletId
presence

Required

Interface version

2.0
Format
AN21(restricted String)
Customer’s Wallet identifier.
paymentMeanId

presence

Required

Interface version

2.0

Format

N6

Payment mean rank in Sherlock’s wallet.
seal

presence

Required

Interface version

2.0

Format

ANS128

Message seal used to ensure the integrity of the request and the authentication of sender / receiver of the message.

Optional

intermediateServiceProviderId

presence

Optional

Interface version

2.12

Format

AN30

Identifier of the Service used by the merchant for the exchanges with the Sherlock’s platform.
paymentMeanAlias
presence

Optional

Interface version

2.0
Format
ANU20(restricted String)
Payment mean alias defined by the Buyer and used in the Buyer’s wallet.

Attention: use this free field only for the intended purpose, and therefore do not insert any personal data, especially cardholder data

As a subcontractor, Crédit Lyonnais processes personal data in accordance with the Data Processing Agreement (DPA), appended to all contracts.

Thus:
- The personal data specified in the DPA must only be transmitted to Crédit Lyonnais via the fields provided for this purpose (see data dictionary).
- All other personal data not listed in the DPA must not be transmitted to Crédit Lyonnais.
sealAlgorithm

presence

Optional

Interface version

2.12

Format

ANS20(restricted values)

Algorithm applied to calculate the seal encryption.

List of values

HMAC-SHA-256

The encryption algorithm applied is HMAC-SHA-256

HMAC-SHA-512

The encryption algorithm applied is HMAC-SHA-512

SHA-256

The encryption algorithm applied is SHA-256

Request sample

json
soap

            {
  "interfaceVersion": "WR_WS_2.3",
  "keyVersion": "1",
  "merchantId": "011223344550000",
  "merchantWalletId": "walId011",
  "paymentMeanAlias": "myAlias",
  "paymentMeanId": "2",
  "seal": "1e26289499d5f6104e6300291f272d7b994a111eecf8feedccf934560de26e5d"
}

                  <urn:updatePaymentMean>
         <urn:input>
            <urn:merchantId>011223344550000</urn:merchantId>
            <urn:interfaceVersion>WR_WS_2.2</urn:interfaceVersion>
            <urn:merchantWalletId>walId011</urn:merchantWalletId>
            <urn:paymentMeanId>2</urn:paymentMeanId>
            <urn:paymentMeanAlias>myAlias</urn:paymentMeanAlias>
         </urn:input>
      </urn:updatePaymentMean>

Response

Required

seal

presence

Required

Interface version

2.0

Format

ANS128

Message seal used to ensure the integrity of the request and the authentication of sender / receiver of the message.

Optional

errorFieldName

presence

Optional

Interface version

2.0

Format

ANS50

Error field name of the incoming request. Present when responseCode = 12 or 30.
walletActionDateTime

presence

Optional

Interface version

2.0

Format

ANS25 (ISO8601)

Date and time of the action on the wallet, in Sherlock’s system at the merchant’s local time (in the merchant’s time zone)
walletResponseCode

presence

Optional

Interface version

2.0

Format

N2(restricted values)

Sherlock’s server response code for wallet Management.

List of values

00

Successful operation

03

Invalid Merchant contract

12

Invalid data, verify the request

25

Wallet / payment mean unknown by Sherlock’s

30

Format error

40

merchantId not allowed to access this wallet service

94

Duplicated wallet / payment mean

99

Temporary problem at the Sherlock’s server level

Response sample

json
soap

            {
  "walletActionDateTime": "2014-05-19T23:19:54-12:00",
  "walletResponseCode": "00",
  "seal": "4d40a4af0fe8ceaf1370ab5e434c6ba939973bcacf33f202c72c47a8ab622c19"
}

                  <updatePaymentMeanResponse xmlns="urn:sips:cn:contract:office:wallet:v2">
         <output>
            <walletActionDateTime>2012-10-17T23:50:44-12:00</walletActionDateTime>
            <walletResponseCode>00</walletResponseCode>
            <errorFieldName />
         </output>
      </updatePaymentMeanResponse>

Changelog

Filter

Interface version	Data	Attendance
2.12	`intermediateServiceProviderId`	Request
2.0	`paymentMeanAlias`	Request
2.12	`sealAlgorithm`	Request
2.0	`interfaceVersion`	Request
2.0	`keyVersion`	Request
2.0	`merchantId`	Request
2.0	`merchantWalletId`	Request
2.0	`paymentMeanId`	Request
2.0	`seal`	Request/Response
2.0	`errorFieldName`	Response
2.0	`walletActionDateTime`	Response
2.0	`walletResponseCode`	Response

updatePaymentMean

Endpoints

Request

Required

`interfaceVersion`

`keyVersion`

`merchantId`

`merchantWalletId`

`paymentMeanId`

`seal`

Optional

`intermediateServiceProviderId`

`paymentMeanAlias`

`sealAlgorithm`

Request sample

Response

Required

`seal`

Optional

`errorFieldName`

`walletActionDateTime`

`walletResponseCode`

Response sample

Changelog

Need help?