getPdfMandate
To search in the page use Ctrl+F on your keyboard
This operation allows to recover an exising mandate in PDF. The PDF is serialized in Base64. The string must be decoded and converted to a PDF file to allow reading or downloading.
Recommended interfaceVersion: MR_WS_2.55
It is advised to read the following documents before
-
Recommended
SDD
Functional, technical documentation and user guides to help you to integrate Mercanet online payment solution.
Open in new tab SDD
Endpoints
-
- PROD
-
https://office-server.mercanet.com/rs-services/v2/mandate/getPDFMandate
- method
- POST
-
- TEST
-
https://office-server-mercanet.test.sips-services.com/rs-services/v2/mandate/getPDFMandate
- method
- POST
-
- PROD
-
https://office-server.mercanet.com/services/v2/mandate?wsdl
- method
- POST
-
- TEST
-
https://office-server-mercanet.test.sips-services.com/services/v2/mandate?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
MR_WS_2.
- Office (M2M) (SOAP/JSON) interface for mandate management.
-
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).
-
mandateId
- presence
- Required
- Interface version
- 2.0
Mandate number.
-
merchantId
- presence
- Required
- Interface version
- 2.0
Identifier of the shop, this value is provided to the merchant by Mercanet during the shop registration.
-
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.0
Identifier of the Service used by the merchant for the exchanges with the Mercanet platform.
-
sealAlgorithm
- presence
- Optional
- Interface version
- 2.0
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
-
acquirerResponseCode
- presence
- Optional
- Interface version
- 2.0
Response code returned by the acquirer during an authorisation request.
List of values
00
- Transaction approved or processed successfully
02
- Contact payment mean issuer
03
- Invalid acceptor
04
- Keep the payment mean
05
- Do not honour
07
- Keep the payment mean, special conditions
08
- Approve after identification
12
- Invalid transaction
13
- Invalid amount
14
- Invalid PAN
15
- Unknown payment mean issuer
17
- Payment aborted by the buyer
20
- Invalid response (error in server domain)
24
- Operation not authorised
25
- Transaction not found
30
- Format error
31
- Id of the acquiring organisation unknown
33
- payment mean expired (Paypal / Cofidis)
34
- Fraud suspicion
40
- Function not supported
41
- Payment mean lost
43
- Payment mean stolen
51
- Insufficient or exceeded credit
54
- Payment mean expired (CB / Visa / MC / WLAcq / BCMC)
55
- Wrong PIN
56
- Payment mean missing from the file
57
- Transaction unauthorised for this payment mean holder
58
- Transaction forbidden to the terminal
59
- Fraud suspicion
60
- The payment mean acceptor must contact the acquirer
61
- Exceeds the amount limit
62
- Transaction awaiting payment confirmation
63
- Security rules not complied with
65
- Allowed number of daily transactions has been exceeded
68
- Response not received or received too late
75
- Exceeded number of PAN attempts
87
- Terminal unknown
90
- System temporarily stopped
91
- Payment mean issuer inaccessible
92
- The transaction does not contain enough information to be routed to the authorizing agency
93
- Transaction cannot be completed: violation of law
94
- Duplicated transaction
96
- System malfunction
97
- Request time-out; transaction refused
98
- Server unavailable; network routing requested again
99
- Incident with initiator domain
A1
- Transaction refused because the 3-D Secure authentication data is missing
A4
- Transaction refused because the 3-D Secure authentication exemption is misused
R1
- the cardholder (or his bank) has revoked recurring payments made at a merchant
R3
- the cardholder (or his bank) has revoked all recurring payments
-
errorFieldName
- presence
- Optional
- Interface version
- 2.21
Error field name of the incoming request. Present when responseCode = 12 or 30.
-
mandatePdf
- presence
- Optional
- Interface version
- 2.0
Pdf of mandate encoded in base64.
-
mandateResponseCode
- presence
- Optional
- Interface version
- 2.0
Response code returned by the mandate management service.
List of values
00
- Mandate operation accepted
03
- Invalid merchant contract
05
- Process is refused
12
- Invalid mandate, check the request parameters
17
- Buyer cancellation
25
- Unknown mandate
30
- Format error
34
- Fraud suspicion (erroneous seal)
40
- Function not supported: the operation that you wish to perform is not part of the operation type for which you are authorised
99
- Temporary problem at the Mercanet server level
Response sample
Changelog
Interface version | Data | Attendance | Container |
---|---|---|---|
2.0 |
intermediateServiceProviderId
|
Request | |
2.0 |
sealAlgorithm
|
Request | |
2.0 |
interfaceVersion
|
Request | |
2.0 |
keyVersion
|
Request | |
2.0 |
mandateId
|
Request | |
2.0 |
merchantId
|
Request | |
2.0 |
seal
|
Request/Response | |
2.0 |
acquirerResponseCode
|
Response | |
2.21 |
errorFieldName
|
Response | |
2.0 |
mandatePdf
|
Response | |
2.0 |
mandateResponseCode
|
Response |