Error Handling

PXP Financial Payment Service will return a paymentServiceException message in case an unexpected error occurs. For example, an initiatePaymentRequest message is answered with an initiatePaymentResponse in case of successful execution, and with a paymentServiceException message if the call experienced validation or technical errors. The client application must be able to parse the paymentServiceException message and react accordingly to the error returned.

Example paymentServiceException message with errorCode=202:

<paymentServiceException xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <id>50f83699-07bb-4c22-8393-b1b3c5ec645f</id>
  <errorCode>202</errorCode>
  <errorMessage>Shop with ID 'XXXX' was not found for merchant with ID 'YYYY'.</errorMessage>
</paymentServiceException>

Example paymentServiceException message with errorCode=800:

<paymentServiceException xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <id>2e6bff78-7a4f-42a6-b364-fbce79184a5d</id>
  <errorCode>800</errorCode>
  <errorMessage>Error validating request against:
    CQRPayments.PaymentService.ServiceContracts.PaymentServiceTypes.xsd 

    !InnerException: The element 'initiatePaymentRequest' in namespace 'http://www.cqrpayments.com/PaymentProcessing' has invalid child element 'merchantTransactionID' in namespace 'http://www.cqrpayments.com/PaymentProcessing'. List of possible elements expected: 'shopID' in namespace 'http://www.cqrpayments.com/PaymentProcessing'.</errorMessage>
</paymentServiceException>

Example paymentServiceException message with errorCode=205:

<paymentServiceException xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
                         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <id>28614c95-7196-4384-89b9-c0724018e173</id>
  <errorCode>205</errorCode>
  <errorMessage>Currency with code 'JUR' was not found.</errorMessage>
</paymentServiceException>

The list with possible error codes is below:

Error Code

Reason

100

A general validation error occurred. For details see message field of the paymentServiceException

201

The specified merchant was not found.

202

The specified shop was not found.

203

The specified use was not found.

204

The specified country was not found.

205

The specified currency was not found.

206

The specified language was not found.

207

The specified payment method was not found.

208

The payment account was not found.

209

The payment was not found.

210

The payment limit was not found.

211

The Payment Recurrence was not found

212

The VAN (Virtual Account Number, usually used for Offline Bank Transfer Deposits) was not found.

213

The payment batch type was not found.

301

The user has been already registered.

302

The user has been already registered.

303

The payment account has been already registered.

309

The currency provided is not allowed, e.g. currency for a refund is not equal to the currency of the original payment.

401

The provided username and/or password in the BasicAuthentication header are wrong

500

A technical error occurred while processing the request.

501

The payment account is not valid.

502

The credit card number has a wrong format or number is not valid for the payment method’s card scheme or CVC not provided.

503

The specified credit card has been expired.

504

Not all necessary fields for processing the request have been provided.

505

The currency provided is not supported by the PXP Financial Payment Service.

506

Currency was not provided.

600

Permission denied.

700

The payment action is not allowed for the current state the payment is.

800

Schema validation error. The request is not valid according to the xml schema.

900

Invalid credentials. The provided username and/or password are wrong.

903

An argument was out of allowed range.

1002

The provided amount is incorrect.

1003

The supplied original payment is not valid.

1004

Invalid Payment Method

1005

The Payment Recurrence cannot be stopped.

1006

The bank account data could not be retrieved.

1007

Missing user detail

1008

Invalid email token

1009

Partner not found.

1010

Partner update error

1011

The partner is already registered.

1012

Invalid AVS data

1013

User email is null.

1014

Mismatch between merchant and shop

1015

Provider technical error

1016

Missing parameter

1017

Not supported transaction type

1018

Not supported Transaction Plan type

1019

Not supported Schedule Unit

1020

Not supported Payment Provider

1021

Invalid Transaction Plan interval

1022

Invalid Transaction Plan count

1030

The MID for the merchant was not found.

1031

Cancel Action is not allowed.

1033

The Voucher was not found.

See paymentServiceException for additional information.