Effective as of iOS SDK 5.4, the WLW platform passes failure response data in the PDPaydiantError class, which identifies the unchanged HTTP code, along with a context-specific description and an instance of PDErrorInformation object, encapsulating the raw failure response body. The errorCode and errorDescription represent the event status, plus an external error code passed by a third-party entity through the connector framework, if applicable.
The following XML sample depicts the general structure of the server error object.
The PDErrorInformation is populated with the errorCode and errorDescription values defined in WLW’s platform. The following tables define each possible value within the code ranges that have been designated for specific operation types.
Note: Not all codes within each designated range have assigned definitions.
Payment status codes are not error codes in that they are not returned to the app in failure responses. Rather, they represent the outcome of a payment authorization request as it is returned to WLW by the processor and are returned to the app within the PaymentStatusCode attribute of a PDTransactionAccount instance returned in a success response at completion of a payment transaction. In transactions where one or more payment attempts failed before the transaction was ultimately successful, the previousPaymentResults attribute of the PDTransactionDetail object may include PDTransactionAccount instances populated with values from this list.
Authorization Status
Code
Status Message
Description
200
Approved Payment
Payment for the transaction has been approved.
201
Declined Payment
Payment for the transaction has been declined.
203
Insufficient Funds
The account from which the payment is being drawn does not have enough money to cover the amount due.
210
Auth_Approved
The authorization has been approved.
211
Auth_Failed
The authorization has not succeeded.
212
Partial_Pre_Auth_Success
The amount for pre-authorization was approved for an amount that was less than the approved pre-authorization amount.
Payment Status
Code
Status Message
Description
240
Duplicate Transaction
The transaction has already been submitted.
241
Processing Error
Approval of the payment authorization has failed.
242
Gateway Processing Error
An error has occurred in an external system while processing the payment.
243
Transaction Not Allowed
This transaction cannot be processed at the customer’s financial institution.
Payment Input Failures
Code
Status Message
Description
250
Invalid Inputs
The transaction contains one or more invalid parameter entries.
251
Invalid Amount
The amount entered is not a valid format (e.g., multiple decimal points may have been entered).
252
Invalid Card Number
The credit card number entered is not valid (e.g., too many or too few digits).
253
Invalid Expiry Date
The credit card expiration date is not a valid date.
254
Expired Card
The credit card expiration date has already passed.
255
Invalid ABA
The ABA code is not valid for the card.
256
Invalid Account Number
The account number is invalid.
257
AVS Mismatch
The transaction resulted in an AVS mismatch. The address provided does not match billing address of card holder.
258
Invalid Card Code
The card code (CVV2/CVC2/CID) is invalid.
Issuer Related Status
Code
Status Message
Description
500
Invalid Transaction
The transaction request is not valid; contact Issuer.
501
Suspected Fraud
A fraudulent transaction is suspected; contact Issuer.
Merchant Related Status
Code
Status Message
Description
550
Merchant Error
The data transmitting from the POS terminal has resulted in an error.
If you accept cookies, we’ll use them to improve and customize your experience and enable our partners to show you personalized PayPal ads when you visit other sites. Manage cookies and learn more