LogoLogo
GitHubFeedback Form
EN
EN
  • GETTING STARTED
    • Welcome
    • Preliminaries
      • Sandbox
      • Authentication
        • HMACSHA256 Auth
      • Postman Collections
      • Live vs Sandbox
      • Idempotency
      • Limiters
  • Payment Methods
    • PayWithiyzico (PWI)
      • PWI Implementation
        • PWI-Initialize
        • PWI-Retrieve
        • PWI Sample Imp.
    • Direct Charge
      • Non-3DS
        • NON-3DS Implementation
          • Create Payment
          • Retrieve
      • 3DS
        • 3DS Implementation
          • Init 3DS
          • Auth 3DS
      • Checkout Form (CF)
        • CF Implementation
          • CF-Initialize
          • CF-Retrieve
          • CF Sample Imp.
    • PreAuth & Capture
      • Non-3DS
        • Non-3DS Implementation
          • Create PreAuth Payment
          • Create PostAuth Payment
  • Products
    • Online Payment
    • Marketplace
      • Marketplace Implementation
        • Submerchant
          • Submerchant Update
          • Retrieve Submerchant
          • Submerchant Price / Item Update
        • Online Payment
        • Approval
    • Subscription
      • Subscription Implementation
        • Subscription Product
        • Payment Plan
        • Subscription Transactions
        • Subscriber Transactions
    • Bank Transfer
      • Bank Transfer Implementation
        • Bank Transfer Init
        • Bank Transfer Retrieve
      • Bank Transfer FAQ
    • iyzilink
      • iyzilink API
    • Shopping Credit
      • Shopping Credit Implementation
        • Initialize Shopping Credit
        • Retrieve Shopping Credit
        • Shopping Credit Sample Imp.
  • Advanced
    • Card Storage
    • Reporting Service
    • Refund & Cancel
    • Webhook
    • SFTP
    • Settlement Files
    • Fraud Notifications
    • Installment & BIN Service
    • Refund to Balance
    • Retrieve Payment
    • Response Signature Validation
  • Platforms
    • Woocommerce
    • Opencart
    • Prestashop
    • Magento
    • IdeaSoft
    • Ticimax
    • T-Soft
    • Shopify
    • WIX
  • Add-ons
    • Error Codes
    • Test Cards
    • Integration Checklist
    • iyzico Logo Pack
Powered by GitBook
LogoLogo

Company

  • About
  • Career
  • Social
  • Youtube

Community

  • Github
  • Medium

Integration

  • Brand Guide
  • Solution Partners
  • Open Source

Contact

  • Contact Us
  • Support Center
On this page
  • Bank Error Codes
  • General Error Codes
  • Authentication Error Codes
  • Onboarding Error Messages
  • Card Storage Validation Errors
  • Validation Errors
  • Marketplace Payout Errors
  1. Add-ons

Error Codes

PreviousAdd-onsNextTest Cards

Last updated 13 days ago

Error Codes

When you make a request to the iyzico API, and there are issues with the request or the payment, iyzico informs you of the error, along with the numeric code and a description of the error. The numeric code of the relevant error is returned in the errorCode variable, and the message explaining the error is in the errorMessage variable.

When an error occurs, indicated by the status parameter having a value of "failure," the iyzico payment API returns the relevant variables as follows:

  • errorCode: e.g., 10051

  • errorGroup: e.g., NOT_SUFFICIENT_FUNDS

  • errorName: e.g., Error

  • errorMessage: e.g., Insufficient card limit, insufficient balance.

Some key/value pairs may provide insufficient responses depending on the bank.

iyzico groups error codes. start with 10000, while Card Storage Error Messages start with 3000.

If you encounter the same error more than 5 times within 1 minute, please contact your account manager or reach out to our support team via entegrasyon@iyzico.com.

The error categories below include commonly encountered error messages. To access the full list of error codes:

Bank Error Codes

When the relevant request is successfully made and the payment is initiated, errors that include payment responses returned from the bank are evaluated in this group. The error codes and explanations of this group are as follows.

Error Code
Description
Error Code
Description
Details

DO_NOT_HONOUR

Transaction not approved

10005

An error occurred during the payment process, please contact your bank.

This is a card-related error; the cardholder must contact their bank.

INVALID_TRANSACTION

Invalid transaction

10012

An error occurred during the payment process, please contact your bank.

This is a card-related error. It is recommended that the card holder contact their bank.

FRAUD_SUSPECT

Payment failed to pass security check

10034

The transaction was not permitted by the bank.

Fraud precaution. The transaction is not permitted by the bank. The customer may be the person committing fraud; it is recommended not to provide information to the customer and to direct them to the bank.

PICKUP_CARD

Lost card, seize the card

10041

The PIN attempt limit has been exceeded, the transaction is not permitted by the bank.

This occurs when the user enters the PIN incorrectly multiple times, leading the bank to place a restriction on the card. The customer may be the person committing fraud; it is recommended not to provide information to the customer and to direct them to the bank.

LOST_CARD

Lost card, seize the card

10043

The transaction is not permitted by the bank.

Notification of lost/stolen card. The transaction is not permitted by the bank. The customer may be the one committing fraud; it is recommended not to inform the customer and direct them to the bank.

NOT_SUFFICIENT_FUNDS

Insufficient card limit, insufficient balance

10051

Insufficient card limit, insufficient balance.

This error occurs when the card limit is insufficient.

EXPIRED_CARD

Expiry date incorrect

10054

Expiry date incorrect. Your card has expired.

This error occurs when the card has expired.

NOT_PERMITTED_TO_CARDHOLDER

Cardholder cannot perform this transaction

10057

Your card is restricted for this transaction, please contact your bank.

This error occurs when there is a restriction placed on the card by the issuing bank. The cardholder should contact their bank for more information.

NOT_PERMITTED_TO_TERMINAL

Terminal not authorized for this transaction

10058

Error occurred during payment, please contact the company representative.

This error is received from the POS bank and could be card-related. Please contact iyzico for transaction-specific issues.

INVALID_CVC2

Incorrect CVC2 information

10084

The entered CVV value is incorrect or invalid.

This error occurs when the CVV value sent in the payment request is incorrect or invalid according to the bank. The user can try the transaction again, and if the error persists, they should contact their bank.

RESTRICTED_BY_LAW

Your card is closed for online shopping. You can contact your bank to enable it.

10093

Your card is closed for online shopping, please contact your bank.

This error occurs when the card is closed for internet banking. The cardholder can contact their bank or, if supported, enable internet banking through their bank’s mobile application.

CARD_NOT_PERMITTED

Card did not permit the transaction

10201

The card did not permit the transaction, please contact your bank.

The cardholder should contact their bank for more details.

UNKNOWN

A general error occurred during the payment process

10202

Error occurred during the payment process, please contact the company representative.

This error can occur due to an expected request structure error from the bank. Please contact iyzico for transaction-specific issues.

INVALID_XML_END_TAG

A general error occurred during the payment process

10204

Error occurred during the payment process, please contact the company representative.

Please contact iyzico for transaction-specific issues.

INVALID_CHARS_IN_EMAIL

Email is not in a valid format

10205

The email address is not in a valid format, please check your email address.

Please contact iyzico for transaction-specific issues.

REFER_TO_CARD_ISSUER

Please get approval from your bank

10207

Please get approval from your bank.

This is a card-related error, and the cardholder needs to contact their bank.

INVALID_MERCHANT_OR_SP

Invalid merchant category code

10208

Error occurred during payment, please contact the company representative.

Please contact iyzico for transaction-specific issues.

BLOCKED_CARD

Card is blocked

10209

Card is blocked, please contact your bank.

The cardholder should contact their bank for more details.

INVALID_CAVV

Incorrect CAVV information

10210

Incorrect CVC information, please try again.

This error occurs when the CVV value sent in the payment request is incorrect or invalid according to the bank. The user can try the transaction again, and if the error persists, they should contact their bank.

INVALID_ECI

Incorrect ECI information

10211

Error occurred during the payment, please contact your bank.

This is a card-related error, and the cardholder needs to contact their bank.

CVC2_MAX_ATTEMPT

Exceeded the maximum number of CVC2 attempts

10212

Exceeded the maximum number of incorrect CVC attempts, please contact your bank.

The cardholder should contact their bank for more details.

BIN_NOT_FOUND

BIN not found

10213

BIN not found, please contact the company representative.

Please contact iyzico for transaction-specific issues.

COMMUNICATION_OR_SYSTEM_ERROR

Communication or system error

10214

Error occurred at the bank, please try again later.

This error occurs due to temporary or transaction-specific issues at the bank. Please contact iyzico for transaction-specific issues.

INVALID_CARD_NUMBER

Invalid card number

10215

Invalid card, incorrect card number, please check your card number.

The card number entered in the payment form should be checked by the user. If the error persists, the cardholder should contact their bank.

NO_SUCH_ISSUER

Issuing bank not found

10216

Error occurred at the bank, please try again later.

This error occurs due to temporary or duration-based interruptions at the card bank. If the error persists, please contact iyzico for transaction-specific issues.

DEBIT_CARDS_REQUIRES_3DS

Debit cards can only be used with 3D Secure transactions

10217

The transaction must be performed as 3D Secure.

This error occurs when the issuing bank informs that transactions made with the debit card must be 3D Secure.

DEBIT_CARDS_INSTALLMENT_NOT_ALLOWED

Installments are not allowed with debit cards

10218

Installments are not allowed with debit cards, please try again.

This error occurs when installments are selected with a debit card.

REQUEST_TIMEOUT

Request to the bank timed out

10219

Error occurred at the bank, please try again later.

This error occurs due to temporary or transaction-specific issues at the bank. Please contact iyzico for transaction-specific issues.

DECLINED

Payment not accepted

10220

Please try again. If the error persists, please contact your bank.

This is a temporary bank error. The user can try again, and if the error persists, they should contact their bank. The detailed error can be checked from the iyzico Merchant Panel, and please contact iyzico for transaction-specific issues.

NOT_PERMITTED_TO_FOREIGN_CARD

Terminal closed to foreign cards

10221

Transactions with foreign cards are not allowed, please contact the company representative.

This error occurs when the account is closed to foreign cards. Merchants who want to accept transactions with foreign cards can contact their iyzico account representative.

NOT_PERMITTED_TO_INSTALLMENT

Terminal closed to installment transactions

10222

The POS is closed to installment transactions, please contact the company representative.

This error occurs when the POS used for the transaction does not support installments. The current installment information can be retrieved from the iyzico installment service. If an installment transaction is desired and not previously agreed upon, contact your iyzico account representative.

REQUIRES_DAY_END

End of day required

10223

End of day required for the POS.

This error can occur for refund requests when a refund request is made for a transaction that occurred on the same day.

EXCEEDS_WITHDRAWAL_AMOUNT_LIMIT

Withdrawal amount limit exceeded

10224

Your card's transaction limit has been exceeded, please contact your bank.

This error occurs when the transaction limit for the card is exceeded. The cardholder should contact their bank for more details.

RESTRICTED_CARD

Restricted card

10225

Your card is restricted for this transaction, please contact your bank.

This error occurs due to a restriction placed on the card by the issuing bank. The cardholder should contact their bank for more details.

EXCEEDS_ALLOWABLE_PIN_TRIES

Exceeded the allowable number of PIN attempts

10226

You have exceeded the allowable number of PIN attempts, please contact your bank.

This error occurs when the user enters the PIN value incorrectly multiple times. The cardholder should contact their bank for more details.

INVALID_PIN

Invalid PIN

10227

Incorrect PIN number, please try again.

This error occurs when the user enters the PIN number incorrectly. Trying the transaction again is recommended.

ISSUER_OR_SWITCH_INOPERATIVE

Bank or terminal cannot process the transaction

10228

Error occurred at the bank, please try again later.

This error occurs due to temporary or duration-based interruptions at the card bank.

INVALID_EXPIRE_YEAR_MONTH

Invalid expiration date

10229

The expiration date of the card is incorrect, please try again.

This error occurs when the expiration date sent in the payment request is incorrect. The user can check and try the transaction again.

REQUEST_BLOCKED_BY_BANK

Request blocked by the bank

10230

The payment request was blocked by the bank, please contact your bank.

This error occurs when the payment request is blocked by the bank. Please contact iyzico for transaction-specific issues.

SALES_AMOUNT_LESS_THAN_AWARD

The sales amount cannot be less than the award points

10231

The sales amount cannot be less than the award points used

This error occurs when the points value sent in the payment request is more than the transaction amount.

INVALID_AMOUNT

Invalid amount

10232

Invalid amount, please contact your bank.

This is a card-related error, and the cardholder needs to contact their bank.

INVALID_CARD_TYPE

Invalid card type

10233

Invalid card type, please contact your bank.

This error is received from the bank and can be resolved by contacting the bank for transaction-specific issues.

NOT_SUFFICIENT_AWARD

Insufficient award points

10234

Insufficient points.

This error occurs when the points value sent in the payment request is more than the user's available points.

AMEX_CAN_USE_ONLY_MR

American Express card error

10235

American Express card error, please contact your bank.

The cardholder should contact their bank for more details.

REFUND_NOT_ALLOWED_FOR_THIS_DEBIT_CARD

Refunds are not allowed for debit card transactions

10237

Refunds are not allowed for debit card transactions

Please contact iyzico for transaction-specific issues. More information can be obtained from the bank.

INPUT_DATA

Invalid transaction

10238

Invalid transaction

This is an alternative payment method error.

USER_ABORT

Payment was canceled by the user

10239

Payment was canceled by the user

This is an alternative payment method error.

TIMEOUT

The request sent timed out

10240

The request sent timed out

This is an alternative payment method error.

REMOTE_ERROR

Communication or system error

10241

Communication or system error

This is an alternative payment method error.

LOCAL_ERROR

Communication or system error

10242

Communication or system error

This is an alternative payment method error.

LOCAL_DECLINE

Payment not accepted

10243

Payment not accepted

This is an alternative payment method error.

REMOTE_DECLINE

Payment not accepted

10244

Payment not accepted

This is an alternative payment method error.

QUOTA

The refund amount for the payment installment and the total previously refunded amount cannot be more than the installment amount

10245

The refund amount for the payment installment and the total previously refunded amount cannot be more than the installment amount

This is an alternative payment method error.

REFUND_DECLINE

You cannot currently process a refund for the transaction made with the alternative payment method, please try again later

10246

You cannot currently process a refund for the transaction made with the alternative payment method, please try again later

This is an alternative payment method error.

BANK_TRANSFER

Bank transfer payment not made

10247

Bank transfer payment not made

This response is returned when the expected payment via bank transfer/EFT is not received.

EXCEEDED_TRANSACTION_AMOUNT

The amount you want to transact exceeds the transaction limit, we cannot assist you at this time.

10248

The amount you want to transact exceeds the transaction limit, please contact your bank.

The cardholder should contact their bank for more details.

FUND_API

An error occurred during the fund API payment.

10249

An error occurred during the balance payment, please contact the company representative.

Please contact iyzico for transaction-specific issues.

LOYALTY_USAGE_INSTALLMENT_NOT_ALLOWED

Points cannot be used for installment transactions.

10250

Points cannot be used for installment transactions.

This is not valid for all banks. When points are used in transactions from İş Bank and installments are sent, the transaction fails at the bank.

LOYALTY_MIXED_USAGE_NOT_ALLOWED

Points and card limit cannot be used together for the card used in the transaction

10251

Points and card limit cannot be used together for the card used in the transaction

This is not valid for all banks. For World cards, if the card's bank is not Yapıkredi, the entire transaction amount must be paid with points, or no points should be used in the transaction.

CALLBACK 3DS

An error occurred during 3D Secure verification.

This status occurs when the user cannot successfully verify themselves in the 3D form.

INIT_3DS

An error occurred during the 3D Secure verification process.

The status of a transaction remains in the init_threeds state under the following circumstances:

-When the user voluntarily exits the 3D form,

-When the user is unable to view the 3D form for various reasons (e.g., due to network issues, low internet speed caused by the internet service provider, or situations where the user's environment prevents the 3D form from opening on their screen),

-In cases where the transaction is conducted with a foreign card and the user does not receive an SMS, -When the card or the card's bank does not support 3D,

-When the user has not set up a 3D password specifically for a foreign card.

General Error Codes

General error codes are typically due to missing information in the payment details during the request. The relevant error codes and their causes are provided in the table below:

Code
Description
Retry
Details

1

System error occurred

true

Try again or contact the support team.

2

System error occurred

true

Try again or contact the support team.

3

Email is mandatory

true

The buyerEmail parameter must be included in the payment request.

4

Email must be at most 100 characters

true

The buyerEmail parameter must be set to a value less than 100 characters.

5

Email was sent in an incorrect format

true

The buyerEmail must be sent in email format.

8

Identity number is mandatory

true

The identityNumber parameter must be included in the payment request.

9

Identity number must be at most 50 characters

true

The identityNumber parameter must be set to a value less than 50 characters.

10

Identity number must be at least 5 characters

true

The identityNumber parameter must be set to a value more than 5 characters.

11

Invalid request

true

If parameters are not set in the correct format, errors may be received. For detailed information, contact the support team.

12

Invalid card number

true

If the card number is not sent in a format compatible with the Luhn algorithm, this error message is returned.

13

Invalid expiration month

true

If expireMonth is sent in the past or in an incorrect format, this error message may be received.

14

Invalid expiration year

true

If expireYear is sent in the past or in an incorrect format, this error message may be received.

15

Invalid CVC

true

CVC must be 4 digits for American Express cards, and 3 digits for other cards. A CVC not following this rule will return a related error message.

16

Cardholder name is mandatory

true

The cardHolderName parameter must be included in the API payment request.

19

Cardholder name must be at most 100 characters

true

The cardHolderName parameter must be set to a value less than 100 characters.

20

ConversationId must be at most 255 characters

true

The conversationId parameter must be set to a value less than 255 characters.

21

Card alias must be at most 293 characters

true

The cardAlias parameter must be set to a value less than 293 characters.

22

IP should be a maximum length of 50 characters

true

In the refund service, the IP value must be sent as a value less than 50 characters.

23

Callback URL is mandatory

true

The callbackUrl parameter must be included in the CF payment request.

25

GSM number is mandatory

true

The gsmNumber parameter must be included in the payment request.

26

GSM number must be at most 25 characters

true

The gsmNumber parameter must be set to a value less than 25 characters.

27

Invalid phone number

true

A phone number starting with (+90) must be sent.

Authentication Error Codes

These error messages occur when there are authentication issues while connecting to the iyzico API. The error codes and their descriptions are as follows:

Code
Description
Retry
Details

1000

Invalid signature

true

1001

API details not found

true

1002

Merchant not found

true

In the marketplace business model, the API information used in the request must be verified. If the API information is incorrect, a merchant not found error is returned.

1003

Authorization error

true

You can verify using the sample collection, and contact our support team for detailed information.

1004

Random string is mandatory

true

1005

Request object is mandatory

true

1006

API key is mandatory

true

The API value set in the request must be verified. If the API value is missing, this error is returned.

1007

Signature is mandatory

true

This error message is returned when a query is made without an API and Security Key.

1008

Authorization header prefix not found

true

You can verify using the sample collection, and contact our support team for detailed information.

1009

Authorization header string is mandatory

true

Onboarding Error Messages

These errors occur during the onboarding process when mandatory information such as IBAN, tax office, etc., is missing. The error codes and descriptions are as follows:

Code
Description
Retry
Details

2000

This service is only available for marketplace customers

true

A request to the marketplace services from an account that is not a marketplace will result in this error.

2001

Sub merchant is not for ID

true

The submitted submerchantExternalId must be checked. If the submerchantExternalId does not belong to any submerchant in the account, this error message is returned.

2002

Sub merchant does exist for ID

true

If a submerchant has previously been created with the same externalId, an error may occur. You may try again with a different externalId.

2003

subMerchantKey is mandatory

true

The submitted subMerchantKey must be checked. This error occurs if the subMerchantKey is not sent.

2004

subMerchantType is mandatory

true

The submitted subMerchantType must be checked. This error occurs if the subMerchantType is not sent.

2005

IBAN is mandatory

true

This error occurs in the update submerchant service if the IBAN parameter is not included in the request.

2007

subMerchantExternalId is mandatory

true

While creating a submerchant in a marketplace, the subMerchantExternalId is a mandatory parameter. You can try again by sending this value.

2008

subMerchantExternalId should be a maximum length of 255 characters

true

Try sending a value less than 255 characters for the subMerchantExternalId parameter.

2009

address is a mandatory parameter

true

While creating a submerchant in a marketplace, the address is a mandatory parameter. You can try again by sending this value.

2010

address should be a maximum length of 255 characters

true

Try sending a value less than 255 characters for the address parameter.

2011

address should be a minimum length of 5 characters

true

Try sending a value more than 5 characters for the address parameter.

2012

contactName is a mandatory parameter

true

While creating a submerchant in a marketplace, the contactName is a mandatory parameter. You can try again by sending this value.

2013

contactName should be a maximum length of 100 characters

true

Try sending a value less than 100 characters for the contactName parameter.

2014

contactName should be a minimum length of 2 characters

true

Try sending a value more than 2 characters for the contactName parameter.

2015

contactSurname is a mandatory parameter

true

While creating a submerchant in a marketplace, the contactSurname is a mandatory parameter. You can try again by sending this value.

2016

contactSurname should be a maximum length of 100 characters

true

Try sending a value less than 100 characters for the contactSurname parameter.

2017

contactSurname should be a minimum length of 2 characters

true

Try sending a value more than 2 characters for the contactSurname parameter.

2018

taxOffice is a mandatory parameter

true

For individual or corporate merchants, taxOffice is a required parameter.

2019

taxOffice should be a maximum length of 255 characters

true

Try sending a value less than 255 characters for the taxOffice parameter.

2020

taxOffice should be a minimum length of 3 characters

true

Try sending a value more than 3 characters for the taxOffice parameter.

2021

legalCompanyTitle is a mandatory parameter

true

For individual or corporate merchants, legalCompanyTitle is a required parameter.

2022

legalCompanyTitle should be a maximum length of 255 characters

true

Try sending a value less than 255 characters for the legalCompanyTitle parameter.

2023

legalCompanyTitle should be a minimum length of 3 characters

true

Try sending a value more than 3 characters for the legalCompanyTitle parameter.

2024

taxNumber is a mandatory parameter

true

For individual or corporate merchants, taxNumber is a required parameter.

2025

taxNumber should be a maximum length of 100 characters

true

Try sending a value less than 100 characters for the taxNumber parameter.

2026

taxNumber should be a minimum length of 2 characters

true

Try sending a value more than 2 characters for the taxNumber parameter.

2028

name should be a maximum length of 255 characters

true

Try sending a value less than 255 characters for the name parameter.

2029

gsmNumber should be a maximum length of 25 characters

true

Try sending a value less than 25 characters for the gsmNumber parameter.

2030

Iban is invalid

true

The IBAN value must be a valid IBAN consisting of 26 characters.

Card Storage Validation Errors

These errors occur when mandatory information for card storage requests is missing. The relevant error codes and descriptions are as follows:

Code
Description
Retry
Details

3000

externalId should be a maximum length of 255 characters

true

Try again by sending a value less than 255 for the externalId parameter when saving the card.

3001

cardUserKey is a mandatory parameter

true

Try again by setting the cardUserKey parameter in the retrieve cards request.

3002

cardToken is a mandatory parameter

true

Try again by setting the cardToken parameter in the delete card request.

3003

card details are a mandatory parameter

true

In card creation services, card information must be sent within the "card" object. Please check this field in the request that caused the error.

1401

card number a mandatory parameter

true

In the card creation service, the cardNumber parameter must include the card number. Please set this information and try again.

3005

cardUserKey is not found

true

If the cardUserKey provided for the user whose card details are requested is not defined in the system, this error message is returned. Please verify the provided information.

3006

cardToken is not found

true

The cardToken information in the request that caused the error must be checked.

3007

Card storage feature is not defined

true

This error occurs when a request is sent to the card storage service without having the card storage feature enabled on the account. You can activate this feature by purchasing it from the plugins section in the iyzico panel.

3008

Encryption error

true

Please contact the support team for more information.

3009

Decryption error

true

Please contact the support team for more information.

3012

Email cannot contain card number

true

The email parameter sent during card registration must not contain a card number.

3013

externalId cannot contain card number

true

The externalId parameter sent during card registration must not contain a card number.

Validation Errors

Validation errors are error messages returned by iyzico due to different situations such as incorrect information, fraud, limit, etc.

Code
Description
Retry
Details

5001

paymentTxId is a mandatory parameter

true

Since paymentTransactionId is a required parameter in the Approve service, this error message is returned when it is not included in the request.

5111

CardUserKey must be sent with cardToken

true

For payment requests made using a stored card, both cardUserKey and cardToken must be provided. If cardToken is not included in the payment request, the corresponding error message will be returned.

5002

paymentId is a mandatory parameter

true

In the second step of the 3DS integration, which is the payment completion phase, the paymentId parameter is mandatory for the CreateThreedsPayment request. If the request sent to iyzico does not include a valid paymentId, this error will be returned.

5005

price should be more than zero

true

In iyzico services, price-determining parameters must have a value greater than zero. If any of these parameters are set to zero, the corresponding error message will be returned by iyzico.

5006

binNumber is a mandatory parameter

true

The binNumber parameter is mandatory for the relevant service. If it is not included in the request, the corresponding error message will be returned by iyzico.

5007

binNumber should be an exact length of 6 characters

true

The binNumber parameter must be either 6 or 8 digits long. If it does not meet this requirement, the corresponding error will be returned.

5008

price should not be equal or more than 100,000

true

To increase the maximum payment limit on your account, please contact our support team.

5014

Conversion data decryption failed while 3D Secure process

true

Please verify the conversationData value you are sending to the CreateThreedsPayment service. If this data was received as empty on your end, it is acceptable to forward it as empty in the related request.

5024

subMerchant identityNumber is a mandatory parameter to approve transaction

true

Submerchant breakdowns cannot be approved if the identityNumber parameter was not provided during the submerchant creation. The relevant submerchant must first be updated with a valid identityNumber, and only then can the breakdown be approved.

5050

basketItemPrice must be more than Zero

true

In iyzico services, price parameters cannot be less than or equal to zero. This error occurs when at least one of the items in the request has a price value that is less than or equal to zero.

5062

Total item price must be equal to price

true

The total amount of the items in the cart must match the value of the price parameter. If the total amount of the items in the cart does not equal the value specified in the price parameter, the following error message will be returned: "The submitted amount must equal the total amount of all breakdowns.

5064

Item approval is already given for this transaction

true

The externalId parameter sent during card registration must not contain a card number.

5066

Bin is not found

true

When an attempt is made to approve a breakdown that has already been approved, the corresponding error message is returned.

5077

subMerchantKey is a mandatory parameter for each product payment transaction

true

In marketplace integration, each product must include the parameters submerchantKey, which indicates which sub-merchant the product belongs to, and submerchantPrice, which specifies the amount to be transferred to that sub-merchant from the transaction

5078

Active sub merchant is not found for this SubMerchantKey

true

If an incorrect subMerchantKey value is provided, or if the value does not correspond to a sub-merchant associated with your account, this error message may be returned.

5086

Payment is not for this merchant

true

This error message is returned when an incorrect value is set for the paymentId parameter in the cancel request.

5087

Payment is not for this merchant

true

This error may occur if the paymentId provided in the Create ThreeDS Payment service is incorrect. It is necessary to verify the validity of the parameters sent in the Create ThreeDS Payment request.

5087

Payment is not for this merchant

true

In the Retrieve Payment Result service, the paymentId of the payment transaction to be queried must be provided. If an incorrect paymentId is submitted, this error message may be returned.

5064

Item approval is already given for this transaction

true

If an attempt is made to approve a breakdown that has already been approved, the corresponding error message will be returned.

6001

Payment request has not passed Fraud check

true

Please contact the support team for detailed information.

Marketplace Payout Errors

These errors occur during marketplace payouts. The relevant error codes and descriptions are as follows:

Code
Description

4000

subMerchantKey is mandatory

4001

Reason is mandatory

4002

Sub-merchant not found

4003

No balance record for the sender

4004

Insufficient balance for the sender

4005

Merchant is not authorized to use the settlement service

4006

To perform a settlement, the sub-merchant's setting for sending funds to balance must be disabled

The generated hash value does not match on the iyzico side. You can recheck using .

This occurs when API information and baseUrl do not match or there are restrictions on the account. You can visit the page. Contact support to check for account restrictions.

For requests, the x-iyzi-rnd parameter must be included in the headers section. If this parameter is missing, the relevant error message is returned.

You can try again through the scripts on the .

For requests, "Authorization" must be defined in the headers section. You can verify using the sample collection.

sample codes
Live vs Sandbox
Postman
sample collection
Postman
Bank error codes
48KB
All Error Codes.xlsx
For all your questions regarding error messages, you can contact entegrasyon@iyzico.com.