Plexy
Pay API
Gate APISDKDashboard
Pay API
Gate APISDKDashboard
  1. Payments
  • Overview
  • Authorization
  • Webhooks
  • API Errors
  • Test Scenarios
  • Ecommerce Plugins
  • API
    • Payments
      • Overview
      • Transaction Errors
      • Payment Links
        • Create Payment Link
        • List Payment Links
        • Retrieve Payment Link by Order Reference
        • Cancel Payment Link
        • Retrieve Payment Link
        • Update Payment Link Expiration
        • Retrieve Payment Links Statistics
      • Reccurent Payments
        • Create Merchant-Initiated Payment
      • Direct Payments
        • Get Keys
        • Create Host-to-Host Payment
      • Transaction Management
        • Find Transaction's History by ID
        • Find Transaction by Payment Link ID
        • Find Transaction by ID
        • Find Transaction by Order reference
      • Payment Management
        • Cancel Payment
        • Capture Payment
        • Process Refund
      • Split Requests
        • Create
        • List
        • Update
        • Get By Id
        • Delete
    • Payouts
      • Retrieve Payout Transactions
      • Process Payout
      • Save Card for Payouts
    • Customers
      • Get Customer's Card Tokens
      • List Customers
      • Create Customer
      • Get Customer by ID
      • Get Customer's Transactions
    • Merchants
      • Payment Beneficiary
        • Create
        • Update
        • Gey By Id
        • List
        • Transfer from beneficiary balance to merchant balance
        • Create manual settlement for beneficiary
      • Retrieve Merchant's Details
    • Wallet
      • Authorize
      • Сapture
      • Refund
      • Cancel
    • Payment Methods
      • Google Pay™ Integration
    • Invoice
      • List Bank Invoices
      • Create Bank Invoice
      • Get Bank Invoice
    • Distributions
      • Create distribution
      • List distributions
      • Get distribution by ID
      • Get distributions balance
  • Schemas
    • Schemas
      • response.TransactionList
      • entity.SplitRequest
      • entity.PaymentBeneficiary
      • request.CreatePaymentBeneficiary
      • entity.SettlementPaymentOrder
      • entity.PayoutRequest
      • entity.PayoutRequestRowData
      • entity.UserProfile Copy
      • entity.Store
      • request.AssignStoreToUser
      • request.RemoveStoreFromUser
      • entity.AccountExternalSystem
      • response.AssignStoreToUser
      • request.CreateStore
      • response.Store
      • response.UserList
      • request.WalletAuthorizeRequest
      • entity.ShortWalletTransaction
      • response.WalletAuthorizeResponse
      • request.WalletCapture
      • response.RemoveStoreFromUser
      • command.HandleThreeDResult
      • domain.Report
      • entity.CardSaveSessionCustomer
      • entity.Permission
      • entity.UserProfile
      • entity.UserRole
      • git_plexypay_com_ecom_back_api_internal_domain_view.Page-domain_Report
      • git_plexypay_com_ecom_back_api_internal_domain_view.Page-entity_UserProfile
      • models.CSVApiRequest
      • models.CreateBussinessDetails
      • models.KeyResponse
      • models.OnboardingRequest
      • models.Transaction
      • paymentcore.Address
      • paymentcore.CustomerDetails
      • request.AuthorizePayment
      • request.BrowserDetails
      • request.CardData
      • request.ChangeUserRole
      • request.ContinueThreeDS
      • request.CreateCardSaveSession
      • request.CreateInviteSession
      • request.CreatePaymentLink
      • request.CreatePaymentLinkMetadata
      • request.HandlePayout
      • request.MerchantInitiatedPayment
      • request.PasswordRequest
      • request.Recurring
      • request.RefundPayment
      • request.SaveCard
      • request.SaveOneCustomer
      • request.TwoStepAuthorizePayment
      • request.UpdateMerchantSettingsRequest
      • request.UpdatePaymentLink
      • response.AcquirerResponseThreeDSecure
      • response.AuthorizeAndCapturePayment
      • response.AuthorizePayment
      • response.CancelPaymentResponse
      • response.CapturePaymentResponse
      • response.ContinueThreeDS
      • response.Currency
      • response.Customer
      • response.CustomerTransaction
      • response.CustomerTransactions
      • response.Customers
      • response.Merchant
      • response.MerchantInitiatedPayment
      • response.MerchantSettings
      • response.PaymentLink
      • response.PaymentLinkInfo
      • response.PaymentLinkMetadata
      • response.PaymentLinksInfo
      • response.PaymentLinksStatistics
      • response.PaymentLinksStatisticsItem
      • response.Payout
      • response.Permission
      • response.RefundPaymentResponse
      • response.Report
      • response.SavedCard
      • response.Session
      • response.Settlement
      • response.SettlementTransaction
      • response.Store
      • response.Stores
      • response.Transaction
      • response.TransactionDetails
      • response.TransactionEvents
      • response.TransactionHistoryEvent
      • response.TransactionHistoryEventData
      • response.TransactionResponse
      • response.TransactionWebhookDetails
      • response.Transactions
      • response.UpdateMerchantSettingsResponse
      • response.UserProfile
      • value.PaymentMethod
    • receipt
    • Error
    • response.BankInvoice
    • DistributionStatus
    • DecimalAmount
    • errors.Source
    • Currency
    • ProductType
    • errors.Message
    • DistributionRecipient
    • ProductCategory
    • request.CreateBankInvoice
    • DistributionCreateRequest
    • Product
    • git_plexypay_com_ecom_back_api_internal_platform_errors.Code
    • DistributionBase
    • response.Error
    • Order
    • DistributionCreatedResponse
    • AgentBalance
    • response.BankInvoiceList
    • DistributionDetailResponse
    • AgentDeposit
    • errors.Type
    • DistributionListItem
    • TopupRequest
    • DistributionListResponse
    • CreateOrderRequest
    • DistributionBalanceResponse
  1. Payments

Transaction Errors

Plexy error codes can come from two sources:
SourceOrigin
PlexyGenerated during Plexy internal routing, processing, reconciliation, or merchant balance checks. These errors do not have a numeric bank response code.
Bank Acquirer / Issuer BankReturned by an acquiring bank or the card issuer and then mapped to a Plexy error code. These errors may include a numeric response code.

Error Codes#

Plexy Error CodeSourcePossible Reasons
routing_failedPlexyPlexy could not route the transaction to a suitable processing provider. This may happen because of routing configuration, provider availability, currency/country/card constraints, or internal routing rules.
no_available_terminalsPlexyThere are no active or suitable terminals available for the merchant, payment method, country, currency, or transaction parameters.
insufficient_balanceBankThe cardholder does not have enough funds or available credit to complete the transaction.
country_unsupportedPlexyThe transaction country is not enabled or supported by Plexy, the merchant configuration, or the available processing providers.
exceed_amount_limitBankThe transaction amount exceeds a limit set by the card issuer, acquiring bank, card product, merchant configuration, or risk rules. The cardholder may need to check their bank limits.
suspected_fraudBankThe issuer or acquirer detected a possible fraud pattern, suspicious card activity, or risk-rule violation. The cardholder should contact the issuing bank.
card_disabledBankThe card may be blocked, reported lost/stolen, restricted by the issuer, or unavailable for payments.
restricted_cardBankThe card has restrictions that prevent this transaction type, merchant category, country, currency, or online payment flow.
authentication_declinedBankCard authentication failed or was declined. This may happen because of incorrect authentication data, failed 3-D Secure verification, expired authentication session, or issuer-side authentication rejection.
withdrawal_frequency_limitBankToo many transactions were attempted within a short period. The cardholder may need to retry later or use another card.
transaction_declinedBankThe bank declined the transaction for a generic or issuer-specific reason. Possible reasons include issuer policy, invalid transaction type, temporary issuer restrictions, card status, risk rules, or bank-side processing limitations. The cardholder should contact their bank for details.
unsupported_cardBankThe card type, card brand, issuing country, BIN, transaction type, or payment flow is not supported by the issuer, acquirer, or Plexy processing configuration.
issuer_unavailableBankThe issuing bank or its processing system is temporarily unavailable or unable to respond correctly. The transaction may succeed if retried later.
technical_issuePlexyAn internal or provider-side technical issue prevented successful processing. This may include timeout, unexpected processing error, integration issue, or temporary service degradation.
expired_cardBankThe card expiration date has passed, or the issuer considers the card expired. The cardholder should use another card.
reconcile_errorBankThe bank or processing provider reported a reconciliation or settlement mismatch. This may require operational review.
no_bank_responsePlexyPlexy did not receive a final response from the acquiring bank, issuer, or processing provider. This may be caused by timeout, network issue, or provider-side unavailability.
daily_card_transaction_limit_exceededPlexyThe card exceeded the allowed daily transaction count or amount limit configured in Plexy rules.
insufficient_merchant_balancePlexyThe merchant does not have enough available balance to process the transaction, payout, withdrawal, or related operation.

Numeric Response Code Mapping#

The following bank, acquirer, or issuer response codes are mapped to Plexy error codes.
Numeric Response CodePlexy Error CodeMeaning
61exceed_amount_limitTransaction amount limit exceeded.
51insufficient_balanceInsufficient card balance.
07card_disabledCard is disabled or blocked.
59suspected_fraudSuspected fraud.
62restricted_cardRestricted card.
58unsupported_cardCard is not supported for this transaction.
-19authentication_declinedAuthentication declined.
65withdrawal_frequency_limitTransaction frequency limit exceeded.
05transaction_declinedGeneric transaction decline.
82issuer_unavailableIssuer unavailable.
54expired_cardExpired card.
13:transaction_declinedTransaction declined.
14unsupported_cardUnsupported or invalid card.
34suspected_fraudSuspected fraud.
02transaction_declinedTransaction declined by issuer.
95reconcile_errorReconciliation error.
57transaction_declinedTransaction declined by issuer.
12transaction_declinedTransaction declined.
78transaction_declinedTransaction declined.
91transaction_declinedTransaction declined due to issuer or bank processing issue.

Plexy-Originated Errors#

The following errors are generated by Plexy and are not mapped from numeric bank response codes.
Plexy Error CodePossible Reasons
routing_failedNo suitable route could be selected for the transaction.
no_available_terminalsNo active terminal matched the transaction parameters.
country_unsupportedThe country is not enabled in Plexy or provider configuration.
technical_issueInternal error, provider integration issue, timeout, or temporary service problem.
no_bank_responseTimeout, network issue, or provider-side unavailability.
daily_card_transaction_limit_exceededThe card reached the configured daily transaction limit.
insufficient_merchant_balanceThe merchant does not have enough available balance for the operation.

Bank-Originated Errors#

The following errors are mapped from numeric response codes returned by banks, acquirers, or card issuers.
Plexy Error CodeNumeric Response Codes
insufficient_balance51
exceed_amount_limit61
suspected_fraud59, 34
card_disabled07
restricted_card62
authentication_declined-19
withdrawal_frequency_limit65
transaction_declined05, 13:, 02, 57, 12, 78, 91
unsupported_card58, 14
issuer_unavailable82
expired_card54
reconcile_error95

Recommended Customer-Facing Messages#

Plexy Error CodeRecommended Message
insufficient_balanceInsufficient funds. Please check your card balance or try another card.
exceed_amount_limitTransaction amount limit exceeded. Please check your bank limits or try another card.
suspected_fraudTransaction declined due to suspected fraud. Please contact your issuing bank.
card_disabledThis card is disabled or blocked. Please contact your bank or try another card.
restricted_cardThis card is restricted and cannot be used for this transaction. Please try another card.
authentication_declinedAuthentication failed or was declined. Please check the entered details and try again.
withdrawal_frequency_limitTransaction frequency limit exceeded. Please try again later or use another card.
transaction_declinedTransaction declined by the bank. Please contact your bank or try another card.
unsupported_cardThis card is not supported. Please try another card.
issuer_unavailableThe issuing bank is temporarily unavailable. Please try again later.
expired_cardThis card has expired. Please use another card.
routing_failedWe could not process this transaction. Please try again later or contact support.
no_available_terminalsWe could not process this transaction at the moment. Please try again later.
country_unsupportedPayments from this country are not supported.
technical_issueA technical issue occurred. Please try again later.
reconcile_errorA processing error occurred. Please contact support.
no_bank_responseThe bank did not respond in time. Please try again later.
daily_card_transaction_limit_exceededDaily card transaction limit exceeded. Please try again later or use another card.
insufficient_merchant_balanceMerchant balance is insufficient to complete this operation.

Notes#

Errors without a numeric response code are generated by Plexy.
Errors with a numeric response code are returned by acquiring banks or card issuers and mapped to Plexy error codes.
The same Plexy error code may be mapped from multiple numeric response codes.
For generic bank declines such as transaction_declined, Plexy may not receive a detailed reason from the bank. In such cases, the cardholder should contact the issuing bank for more information.
Modified at 2026-06-12 11:21:22
Previous
Overview
Next
Payment Links
Built with