58 | Service not allowed
This code indicates the issuer declined the authorization because the requested service or transaction feature is not allowed for the account.
What This Code Means
Response code 58 (“Service not allowed”) is returned when the issuer determines that a particular service capability or transaction feature requested is not enabled or permitted for the card/account. While similar to “transaction not permitted,” this code often reflects a restriction tied to a specific service dimension of the transaction flow rather than a broad category prohibition. The issuer recognizes the request but rejects it due to service eligibility rules. This is not a funds-related decline and does not indicate a system outage. It indicates the request falls outside the account’s allowed service profile.
Where Users Usually See This Code
- Authorization declines for specialized transaction services
- Payment gateway logs for online processing flows
- Processor dashboards showing response code 58
Why This Code Appears
- The account does not support the requested transaction service feature
- Issuer service rules block the authorization in that channel
- Account-level restrictions limit access to certain merchant or service types
- Service capability is disabled due to issuer policy or risk controls
What Typically Happens Next
- Authorization is declined
- Merchant system records a service restriction decline
- Similar attempts may continue to be declined until the eligibility condition changes
What This Code Is Not
- It is not an expired card outcome (see 54)
- It is not a funds decline (see 51)
- It is not an issuer availability problem (see 91)
Troubleshooting Checklist
- □ Review transaction metadata to understand which service or channel was used
- □ Compare the decline pattern across different transaction types or channels
- □ Log the response code for reconciliation and support workflows
- □ Use official acquirer/processor support channels to validate the transaction classification if needed
Notes And Edge Cases
Issuer mapping between 57 and 58 varies, and two issuers may represent the same underlying restriction using different response codes. The decline code alone does not specify which service feature is not allowed. Merchant-side transaction routing and category coding can influence how the issuer interprets the request. In some cases, the issuer may allow standard purchases but restrict certain features, leading to 58 in niche payment flows.