refuseChallenge

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

This function allows a merchant to refuse the challenge on a transaction with orange fraud score. Once the challenge is refused, the transaction is refused.

Recommended interfaceVersion: CR_WS_2.55

Endpoints

json
soap

PROD

https://office-server.sips-services.com/rs-services/v2/cashManagement/refuseChallenge

method

POST
TEST

https://office-server.test.sips-services.com/rs-services/v2/cashManagement/refuseChallenge

method

POST

PROD

https://office-server.sips-services.com/services/v2/cashManagement?wsdl

method

POST
TEST

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

CR_WS_2.

Sips Office (SOAP/JSON) interface for Cash Management 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 Worldline Sips 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.12

Format

AN30

Identifier of the Service used by the merchant for the exchanges with the Worldline Sips platform.
operationOrigin
presence

Optional

Interface version

2.0
Format
AN20(restricted String)
Origin of an operation (for example: name of the program), set by the sender of the request (merchant or Worldline Sips).This field will be present in the operations log sent to the merchant on a daily basis.
s10TransactionReference

presence

Optional

Interface version

2.6

Format

Container

Contains the identification of the transaction (to be compliant with Worldline Sips 1.0).Contains the data pair (s10TransactionId, s10TransactionIdDAte) which ensures the uniqueness of the transaction 1.0.
Contains
- s10TransactionId
  
  presence
  
  Optional
  
  Interface version
  
  2.6
  
  Format
  
  N6
  
  The merchant can choose between transactionId and transactionReference (by default) to identify his transactions.s10TransactionId is an alternative identifier for the transaction to be compliant with Worldline Sips 1.0. The couple s10TransactionId/s10TransactionIdDate ensures the unicity of the transaction.
- s10TransactionIdDate
  
  presence
  
  Optional
  
  Interface version
  
  2.6
  
  Format
  
  N8(YYYYMMDD)
  
  Date of the transaction (expressed in the Worldline Sips server time zone).The couple s10TransactionId/s10TransactionIdDate ensures the unicity of the transaction 1.0.The use of this couple instead of transactionReference depends on an option in the merchant configuration.
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
transactionReference

presence

Optional

Interface version

2.0

Format

AN35

The merchant can choose of referencing his transactions by a transactionId or a transactionReference.transactionReference uniquely identifies a transaction throughout the life of the shop.

            {
  "comment": "bad id",
  "interfaceVersion": "CR_WS_2.6",
  "keyVersion": "1",
  "merchantId": "011223344550000",
  "operationOrigin": "SIPS-SIM",
  "transactionReference": "SIM20140121510382",
  "seal": "c36bcfaf3c05ef257795149686c53022f212e05c6fac98d0169c5e9313941444"
}

                  <urn:refuseChallenge>
         <urn:input>
            <urn:comment>testing</urn:comment>
            <urn:interfaceVersion>CR_WS_2.6</urn:interfaceVersion>
            <urn:merchantId>000000000000012</urn:merchantId>
            <urn:operationOrigin>SIPS</urn:operationOrigin>
            <urn:transactionReference>SIPS</urn:transactionReference>
         </urn:input>
      </urn:refuseChallenge>

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.21

Format

ANS50

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

presence

Optional

Interface version

2.0

Format

ANS20(restricted values)

Status of the transaction updated after a checkout operation. The status of a transaction is described by different keywords which change during the operations it undergoes.

List of values

ABORTED

Transaction totally aborted

CANCELLED

Transaction totally cancelled

CAPTURED

Transaction sent to the bank

CAPTURE_REFUSED

Capture refused

CREDITED

Transaction totally refund

ENDED

Transaction ended

EXPIRED

Transaction expired

PENDING

Transaction waiting for the authorisation request response

PREPROD

Transaction of a merchant which is in the pre-production mode. It cannot be settled.

REFUSED

Transaction refused

TO_AUTHORIZE

Transaction waiting for the authorisation request

TO_CAPTURE

Transaction to send to the bank to debit the user

TO_CHALLENGE

Transaction with a fraud suspicion

TO_CONFIRM_AUTHOR

Transaction waiting for confirmation of authorization.

TO_CONFIRM_CAPTURE

Transaction waiting for confirmation of settlement

TO_CONFIRM_CREDIT

TO_CREDIT

Transaction to send to the bank to credit the user

TO_REPLAY

Transaction waiting for a validation with authorization request

TO_VALIDATE

Transaction waiting for a validation

UNDEFINED

Transaction status not defined

WAITING_AUTHOR

Technical status for transaction in a temporarily state waiting for a authorisation batch response
operationDateTime

presence

Optional

Interface version

2.0

Format

ANS25(ISO8601)

Date and time calculated by Worldline Sips on which the transaction has been completed.
responseCode

presence

Optional

Interface version

2.0

Format

N2(restricted values)

Worldline Sips server response code.
List of values
00

Operation accepted

01

For panToToken and tokenToPan methods, partial success

02

Request of authorized on via telephone with the issuer because of exceeding the card authorization threshold

03

Invalid merchant contract

05

Refused authorization

11

Used for differed check. The PAN is blocked

12

Invalid transaction. Please check the request parameters

14

Invalid PAN or payment mean data check is failed (e.g. card number or the visual cryptogram of the card or AVS address)

17

Customer cancellation
24
In response to a cash management operation: operation not authorized. The operation you wish to perform is not compliant with the transaction status or another operation is in progress at the same time

In response to a payment creation: operation rejected, request already carried out with the same data and the same parameters
25

Transaction unknown by Worldline Sips

30

Format error

34

Fraud suspicion (seal erroneous)

40

Function not supported: the operation that you wish to perform is not part of the operation type for which you are authorized

51

Amount too high

54

Payment mean expiry date is past

55

Merchant doesn’t accept prepaid cards

57

Refund operation refused because the original transaction was subject of an unpaid

60

Transaction pending

62

Waiting the confirmation for the transaction (used by PayPal 1.0)

63

Security rules not observed, transaction stopped

75

Number of attempts to enter the data of the payment mean from Sips Paypage is exceeded

90

Service temporarily not available

94

Duplicated transaction: the transactionReference has been used previously

97

Session expired (no action from the user during 15 minutes), transaction refused

99

Temporarily problem with the payment server

Response sample

json
soap

            {
  "operationDateTime": "2014-10-16T23:51:42-12:00",
  "responseCode": "00",
  "newStatus": "REFUSED",
  "seal": "919b544bfb60539c8979992bc469e0b4229030ee2462a51f62c9cbd3510b3647"
}

                  <refuseChallengeResponse xmlns="urn:sips:cn:contract:office:cashmanagement:v2">
          <output>
            <newStatus>REFUSED</newStatus>
            <operationDateTime>2014-12-12T17:00:39+01:00</operationDateTime>
            <responseCode>00</responseCode>
         </output>
      </refuseChallengeResponse>

Changelog

Filter

Interface version	Data	Attendance	Container
2.12	`intermediateServiceProviderId`	Request
2.0	`operationOrigin`	Request
2.6	`s10TransactionReference`	Request
2.6	`s10TransactionId`	Container	`s10TransactionReference`
2.6	`s10TransactionIdDate`	Container	`s10TransactionReference`
2.12	`sealAlgorithm`	Request
2.0	`transactionReference`	Request
2.0	`interfaceVersion`	Request
2.0	`keyVersion`	Request
2.0	`merchantId`	Request
2.0	`seal`	Request/Response
2.21	`errorFieldName`	Response
2.0	`newStatus`	Response
2.0	`operationDateTime`	Response
2.0	`responseCode`	Response

Need help?

Consulting the faq

WL SIPS DOCS

refuseChallenge

Endpoints

Request

Required

`interfaceVersion`

`keyVersion`

`merchantId`

`seal`

Optional

`intermediateServiceProviderId`

`operationOrigin`

`s10TransactionReference`

`s10TransactionId`

`s10TransactionIdDate`

`sealAlgorithm`

`transactionReference`

Request sample

Response

Required

`seal`

Optional

`errorFieldName`

`newStatus`

`operationDateTime`

`responseCode`

Response sample

Changelog

Need help?