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.58
Endpoints
- 
        
- PROD
 - 
                
https://office-server.mercanet.com/rs-services/v2/wallet/updatePaymentMean - method
 - POST
 
 - 
        
- TEST
 - 
                
https://office-server-mercanet.test.sips-services.com/rs-services/v2/wallet/updatePaymentMean - method
 - POST
 
 
- 
        
- PROD
 - 
                
https://office-server.mercanet.com/services/v2/wallet?wsdl - method
 - POST
 
 - 
        
- TEST
 - 
                
https://office-server-mercanet.test.sips-services.com/services/v2/wallet?wsdl - method
 - POST
 
 
Request
Required
- 
interfaceVersion- presence
 - Required
 - Interface version
 - 2.0
 
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: Office (M2M) (SOAP/JSON) interface for Wallet functions.
 
 - 
keyVersion- presence
 - Required
 - Interface version
 - 2.0
 
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
 
Identifier of the shop, this value is provided to the merchant by Mercanet during the shop registration.
 - 
merchantWalletId- presence
 - Required
 - Interface version
 - 2.0
 
Customer’s Wallet identifier.
 - 
paymentMeanId- presence
 - Required
 - Interface version
 - 2.0
 
Payment mean rank in Mercanet wallet.
 - 
seal- presence
 - Required
 - Interface version
 - 2.0
 
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
 
Identifier of the Service used by the merchant for the exchanges with the Mercanet platform.
 - 
paymentMeanAlias- presence
 - Optional
 - Interface version
 - 2.0
 
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, BNP Paribas 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 BNP Paribas via the fields provided for this purpose (see data dictionary).
 - All other personal data not listed in the DPA must not be transmitted to BNP Paribas.
 
 - 
sealAlgorithm- presence
 - Optional
 - Interface version
 - 2.12
 
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
Response
Required
- 
seal- presence
 - Required
 - Interface version
 - 2.0
 
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
 
Error field name of the incoming request. Present when responseCode = 12 or 30.
 - 
walletActionDateTime- presence
 - Optional
 - Interface version
 - 2.0
 
Date and time of the action on the wallet, in Mercanet system at the merchant’s local time (in the merchant’s time zone)
 - 
walletResponseCode- presence
 - Optional
 - Interface version
 - 2.0
 
Mercanet 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 Mercanet
 30- Format error
 40- merchantId not allowed to access this wallet service
 94- Duplicated wallet / payment mean
 99- Temporary problem at the Mercanet server level
 
 
Response sample
Changelog
| Interface version | Data | Attendance | Container | 
|---|---|---|---|
| 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 |