Skip to main content

Testing Credentials

๐Ÿงช Sandbox Merchant Panelโ€‹

UsernamePasswordMerchant Panel URL
testTest@1234https://merchant.hesbstaging.com/merchant

๐Ÿงพ Sandbox Merchant Credentialsโ€‹

ParameterValue
Merchant Code842217
Access Codec333729b-d060-4b74-a49d-7686a8353481
Secret KeyPkW64zMe5NVdrlPVNnjo2Jy9nOb7v1Xg
IV Key5NVdrlPVNnjo2Jy9
Payment URLhttps://sandbox.hesabe.com

๐Ÿ’ณ Test Card Detailsโ€‹

KNETโ€‹

Card NumberExpiry DateCVVResult Code
888888000000000109/251234โœ… Captured (Approved)
8888880000000001Any Expiry1234โŒ Not Captured (Decline)

Visa (MPGS)โ€‹

Card NumberExpiry DateCVVResult Code
401200103714111212/25207โœ… Captured (Approved)
4012001037141112Any Expiry207โŒ Not Captured (Decline)

MasterCard (MPGS)โ€‹

Card NumberExpiry DateCVVResult Code
545301000009553912/25300โœ… Captured (Approved)
5555 5555 5555 444409/25123โœ… Captured (Approved)
5555 5555 5555 4444Any Expiry123โŒ Not Captured (Decline)

MPGS Expiry dates and responsesโ€‹

Expiry DatesResponse
05 / 39โœ… APPROVED
05 / 39โŒ DECLINED
04 / 27โŒ EXPIRED_CARD
08 / 28โŒ TIMED_OUT
01 / 37โŒ ACQUIRER_SYSTEM_ERROR
02 / 37โŒ UNSPECIFIED_FAILURE
05 / 37โŒ UNKNOWN CVV
info

For more details below check the below documentation

MPGS Test cards information

American Express (AMEX)โ€‹

Card NumberExpiry DateCVVResult Code
34567890123456409/251234โœ… Captured (Approved)
345678901234564Any Expiry1234โŒ Not Captured (Decline)

Visa (Cybersource)โ€‹

Card NumberExpiry DateCVVResult Code
400000000000000209/251234โœ… Captured (Approved)
4000000000000002Any Expiry1234โŒ Not Captured (Decline)

AMEX (Cybersource)โ€‹

Card NumberExpiry DateCVVResult Code
34000000000270809/251234โœ… Captured (Approved)
340000000002708Any Expiry1234โŒ Not Captured (Decline)

Common REST API Status Codesโ€‹

This table includes widely used HTTP status codes that are relevant to REST API operations. These codes represent standard responses from the server regarding the outcome of HTTP requests, such as authentication results, validation errors, or server issues.

Status CodeDescription
200OK โ€“ The request has succeeded. Used for successful GET or POST responses.
201Created โ€“ The request has succeeded, and a new resource has been created. Common in POST requests that create data.
204No Content โ€“ The server successfully processed the request, but there is no content to send in response.
400Bad Request โ€“ The server could not understand the request due to an invalid syntax. Often used when required fields are missing.
401Unauthorized โ€“ Authentication is required and has failed or has not yet been provided.
403Forbidden โ€“ The server understands the request but refuses to authorize it.
404Not Found โ€“ The requested resource could not be found on the server.
405Method Not Allowed โ€“ The request method is known by the server but has been disabled for the requested resource.
408Request Timeout โ€“ The server timed out waiting for the request.
409Conflict โ€“ The request conflicts with the current state of the resource.
415Unsupported Media Type โ€“ The media format of the requested data is not supported by the server.
429Too Many Requests โ€“ The user has sent too many requests in a given amount of time (rate limiting).
500Internal Server Error โ€“ A generic error message, given when an unexpected condition is encountered.
502Bad Gateway โ€“ The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503Service Unavailable โ€“ The server is not ready to handle the request, often due to maintenance or overload.

Custom Application Error Codesโ€‹

Description:

This table lists application-specific error codes used to identify and describe issues related to merchant transactions, authentication, authorization, and payment processing. Each code corresponds to a unique system error or validation failure, allowing clients and developers to handle errors in a structured way.

Error CodeDescription
422The input data provided is either invalid or incomplete.
501The specified merchant is not recognized or registered.
503The merchant does not have access to the requested service.
504Incorrect login credentials provided by the merchant.
505The payment token is invalid or has expired.
506The request contains data that is not formatted or structured correctly.
507A generic error occurred during the transaction process.
508The transaction amount exceeds the allowed limit.
509The number of transactions for the day exceeds the permitted limit.
510The total transaction amount for the day has been exceeded.
511The number of transactions for the month exceeds the permitted limit.
512A threshold has been reached, but the transaction can still proceed.
513The session has expired due to inactivity.
514The amount captured is less than what was originally authorized.
515The captured amount exceeds the authorized amount.
516The captured amount is more than the available authorized balance.
517The authorization has expired and is no longer valid.
518Authorization must be enabled before proceeding with this transaction.
519The currency used in the transaction is not supported or invalid.
520The transaction was cancelled by the user or system.
521This transaction has already been captured and cannot be captured again.
522Terminal ID is missing from the request or is invalid.
523The account details provided are incorrect or incomplete.
524The KNET card used is not valid or unsupported.
525The commission structure provided is invalid or does not match the expected format.