Session Error Codes

1. Partial authorization not allowed for authorizeCard = false

Sample Request:

Partial Auth Request

{
  "payment":{
      "partialAuth":true,
      "authorizeCard": false
  }
 }

Sample Response:

Partial Auth Failed Response

{
  "title": "INVALID_REQUEST",
  "status": 400,
  "detail": "Partial authorization not allowed for authorizeCard = false",
  "errorDetails": null
 }

2. WS2 Verification Failure:

During the session creation process, a WS2 check is conducted to verify agent information, such as MSID. If this check fails, the session is invalidated, leading to a BAD REQUEST response.

Sample Response:

WS2 Check Failed Response

{
  "title": "INVALID_REQUEST",
  "status": 400,
  "detail": "Card WS2 check has failed.",
  "errorDetails": null
 }

3.Payment Method Configuration Not Found:

A session is invalidated during its creation phase if the payment method type is either not configured for the merchant or if it is not correctly specified in the session request.

Sample Response:

Missing Payment Method Type Configuration Response

{
  "title": "INVALID_REQUEST",
  "status": 400,
  "detail": "Payment method type is not configured.",
  "errorDetails": null
}

4. Unavailability of Payment Methods for Capture:

A session becomes invalid if the channels available for the configured payment methods are absent. This absence could be due to either a lack of configuration at the merchant level or an invalid session request.

Applicable Session Modes:

PAYMENT_METHOD_ENTRY, PAYMENT

Sample Response:

Missing Payment Method Channels Response

{
  "title": "INVALID_REQUEST",
  "status": 400,
  "detail": "You have no capture methods available.",
  "errorDetails": null
}

5. Absence of Consent in Payment Request Leads to Failure:

Payment requests are validated against the consent object, and if the consent is not found within the request, the payment request will be invalidated.

If an invalid Consent text is provided, the session will fail with an invalid request. Below special characters are not allowed in the consent text:

[ ] { } + = * ^ % # ~ ` < > ? | \

Applicable Session Modes:

PAYMENT

Sample Response:

Payment Failed Response When Consent Not Found

{
  "title": "INVALID_REQUEST",
  "status": 400,
  "detail": "Consent is required!",
  "errorDetails": null
 }

Session Failed Response When Consent text not valid

{
    "title": "INVALID_REQUEST",
    "status": 400,
    "detail": "Consent is invalid",
    "errorDetails": null
}