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

Endpoints

json
soap

PROD

https://office-server.sogenactif.com/rs-services/v2/mandate/getPDFMandate

method

POST
TEST

https://office-server-sogenactif.test.sips-services.com/rs-services/v2/mandate/getPDFMandate

method

POST

PROD

https://office-server.sogenactif.com/services/v2/mandate?wsdl

method

POST
TEST

https://office-server-sogenactif.test.sips-services.com/services/v2/mandate?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

MR_WS_2.

Sogenactif Office Serveur (SOAP/JSON) interface for mandate management.
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).
mandateId

presence

Required

Interface version

2.0

Format

AN35

Mandate number.
merchantId

presence

Required

Interface version

2.0

Format

N15

Identifier of the shop, this value is provided to the merchant by Sogenactif during the shop registration.
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.0

Format

AN30

Identifier of the Service used by the merchant for the exchanges with the Sogenactif platform.
sealAlgorithm

presence

Optional

Interface version

2.0

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

            {
  "interfaceVersion": "MR_WS_2.20",
  "keyVersion": "1",
  "mandateId": "000000000000000677",
  "merchantId": "011223344550000",
  "seal": "fc24b9e6bd7a433d258a1df1a8af2698b917d1632aaa1bc12c5c8f45adbeba11"
}

                  <urn:getPDFMandate>
         <urn:input>
            <urn:interfaceVersion>MR_WS_2.18</urn:interfaceVersion>
            <urn:merchantId>011223344550000</urn:merchantId>
            <urn:mandateId>000000000000000667</urn:mandateId>
            <urn:keyVersion>1</urn:keyVersion>
            <urn:seal>ae13163cfb5c7c8adb39c032876323f6d34d22d378f95d3e05ef774af7f0a720</urn:seal>
         </urn:input>
      </urn:getPDFMandate>

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

acquirerResponseCode

presence

Optional

Interface version

2.0

Format

AN2(restricted values)

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

Format

ANS50

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

presence

Optional

Interface version

2.0

Format

ANS10240

Pdf of mandate encoded in base64.
mandateResponseCode

presence

Optional

Interface version

2.0

Format

N2

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 Sogenactif server level

Response sample

json
soap

            {
  "mandateResponseCode": "00",
  "acquirerResponseCode": "00",
  "mandatePdf": "JVBERi0xLjQdqzdzqdqzdqzhcnR4cmVmCjIxNzA2CiUlRU9GCg\u003d\u003d",
  "seal": "df97074b81e534d70cccbff5446b71d36c4d4de6d995fe630c8077d6fa85c0a3"
}

            <getPDFMandateResponse xmlns="urn:sips:cn:contract:office:mandatemanagement:v2">
         <output>
            <responseCode>00</responseCode>
            <acquirerResponseCode>00</acquirerResponseCode>
            <mandatePdf>JVBERi0xLjQKJeLjz9MKNSAwIG9iaiA8PC9MZW5ndGggMjA5MzkvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0KeJztvcuWJMeRJbjPr/DdgNWkl9vbrFeDR7IOeIoAmEhWT7HQi0BGJBDNeCTjATbqa+Yj+oNq2dlfMaauoiJyRUQzzHrOmdWQh/QUDZHrV+91F1fzMNX426sv3r46Hea+MjE3MDIKJSVFT0YK</mandatePdf>
            <seal>bf3055b267483d68c9b192915433dd5c7b07b42af38b8c1b00b1b66eea108728</seal>
         </output>
</getPDFMandateResponse>

Changelog

Filter

Interface version	Data	Attendance
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

getPdfMandate

Endpoints

Request

Required

`interfaceVersion`

`keyVersion`

`mandateId`

`merchantId`

`seal`

Optional

`intermediateServiceProviderId`

`sealAlgorithm`

Request sample

Response

Required

`seal`

Optional

`acquirerResponseCode`

`errorFieldName`

`mandatePdf`

`mandateResponseCode`

Response sample

Changelog

Need help?