Errors

Contains all error messages and codes that returned by SDK methods.

To retrieve the return code (OPPErrorCode) use the code attribute of the NSError object:

error.code;

To retrieve the error description look to localized description:

(NSString *)error.localizedDescription;

User info dictionary keys

This key may exist in the user info dictionary, in addition to those defined for NSError.

NSString *const OPPErrorTransactionFailureDetailsKey

Constants

OPPErrorTransactionFailureDetailsKey The corresponding value is an NSDictionary containing the detail transaction failure information.

Error codes

Below you can find all currently supported error codes. See also separate page with OPPErrorCode enum definition.

Payment params errors:

• 1000: Unsupported transaction payment params.
• 1010: Transaction checkoud ID is not valid.
• 1011: Brand doesn’t match payment params class.
• 1090: The token identifier is invalid. Must be alpha-numeric string of length 32.
• 1091: Tokenization is not supported for chosen payment brand.

Card errors:

• 1110: Holder must at least contain first and last name.
• 1111: Invalid card number. Does not pass the Luhn check.
• 1112: Unsupported card brand.
• 1113: Month must be in the format MM.
• 1114: Year must be in the format YYYY.
• 1115: Card is expired.
• 1116: CVV invalid. Must be three or four digits.

Bank account errors:

• 1130: Holder of the bank account is not valid.
• 1131: IBAN is not valid.
• 1132: The country code of the bank is invalid. Should match ISO 3166-1 two-letter standard.
• 1133: The name of the bank which holds the account is invalid.
• 1134: The BIC (Bank Identifier Code (SWIFT)) number of the bank account is invalid.
• 1135: The code associated with the bank account is invalid.
• 1136: The account number of the bank account is invalid.

Apple Pay errors:

• 1150: The Apple Pay payment token data is invalid. To perform this type of transaction a valid payment token data is needed.

Transaction errors:

• 2000: Checkout info cannot be loaded.
• 2001: There are no available payment methods in checkout.
• 2002: Payment method is not available.
• 2003: The transaction was aborted.

• 2004: Brand validation rules cannot be loaded from.

• 2010: The transaction was declined. Please contact the system administrator of the merchant server to get the reason of failure.

• 2020: The сheckout configuration is not valid.

Request errors:

• 3000: Unexpected connection error. Please contact the system administrator of the server.
• 3001: Invalid input parameters for the request.
• 3002: Invalid response from the Server.

Security errors:

• 4000: File loaded from resources does not have valid checksum. Make sure you installed the framework correctly and no one has been tampering with the application.

Klarna Payments errors:

• 5001: Klarna Payments specific error.

Bancontact Link errors:

• 5002: Bancontact Link specific error.

Vipps errors:

• 5003: Vipps specific error.

3-D Secure 2 errors:

• 6000: 3-D Secure 2 transaction error.
• 6001: 3-D Secure 2 transaction was cancelled.

Credit card number scanning error:

• 7000: Card Scanning general error.

Copy and Pay web loading error:

• 8000: OPPErrorCodeCopyAndPayGeneralError.

Custom Components general error:

• 9000: OPPErrorCodeCustomComponentGeneralError.

@interface OPPErrors : NSObject

class OPPErrors : NSObject

An enumeration for the various types of error that resulted in an operation’s failure.

See more

enum OPPErrorCode : NSInteger {}

enum OPPErrorCode : Int, @unchecked Sendable

The error domain for specific errors associated with the ready-to-use UI or SDK API.

extern NSString *const OPPErrorDomain

let OPPErrorDomain: String

The corresponding value is the error.userInfo dictionary containing the detail transaction failure information.

extern NSString *const OPPErrorTransactionFailureDetailsKey

let OPPErrorTransactionFailureDetailsKey: String