Testing and Debugging

Test Credentials

For testing purposes, use the followoing credentials and addresses.

Resource	Credentials	Address
Merchant Panel	Test login and password that you receive on registration at OmniCart.	https://mp.omnicart.scripsi.io/
API Service	An API key — generate one in your Merchant Panel.	https://api.omnicart.scripsi.io/

tip

After you are done with testing, contact or our technical support to switch to production environment.

Test Cards

Use these cards in test environments. For each of the cards below, the following details will work.

CVV/CVC	Any 3-digit number.
EXPIRY	Any future date.
CARDHOLDER NAME	Any name.

Please, note

An invalid input, such as a past expiration date, will return the corresponding error regardless of the test card number.

Brand	Card Number	Success	Message
	4111 1111 1111 1111	True	Payment successful.
	4012 8888 8888 1881	True	Payment successful.
	4000 0000 0000 0002	False	Authentication error (3D Secure).
	4000 0000 0000 0069	False	Insufficient funds.
	4000 0000 0000 0259	False	Card blocked.
	5500 0000 0000 0004	True	Payment successful.
	5105 1051 0510 5100	True	Payment successful.
	5105 1051 0510 5100	False	Insufficient funds.
	5200 8282 8282 8210	False	Authentication error (3D Secure).
	6011 0000 0000 0004	True	Payment successful.
	6011 1111 1111 1117	True	Payment successful.
	6011 0000 0000 0004	False	Insufficient funds.
	3530 1113 0200 0000	True	Payment successful.
	3566 1111 1111 1113	True	Payment successful.

API Debug Mode

OmniCart API is capable of returning debug information in responses. For this purpose, pass the debug property set to truein a request. If this setting is not specified or disabled, OmniCart returns only the error that caused the failure. If the setting is enabled, OmniCart checks the entire incoming request and returns all errors that may lead to a request processing failure.

Please, note

Authentication errors prevent OmniCart from checking the request contents.

Consider the examples below.

This is an example of a successful response. If the debug property is undefined or explicitly disabled, the response contains only the main response code and message pair.

If the debug property is enabled, the response contains the main message and the debug object with an additional message. Note that the request is successful since the above are not error messages.

Example of a successful response

Legend

//debug information

debug: false

{
  "cartId": "6f891edb-1e1f-48bb-b042-2cb790a0f402",
  "code": "000000",
  "message": "Success",
  "timestamp": "2025-04-23T18:25:43.511Z"
}

debug: true

{
  "cartId": "6f891edb-1e1f-48bb-b042-2cb790a0f402",
  "code": "001001",
  "message": "Tag(s) [...] defined but not used",
  "debug": [
    {
      "code": "001002",
      "message": "Undefined tags in item(s): [...]"
    }
  ],
  "timestamp": "2025-04-23T18:25:43.511Z"
}

This is an example of a failed response. If the debug property is undefined or explicitly disabled, the response contains only the main error code and message pair.

If the debug property is enabled, the response specifies the error that caused the request to fail separately. The debug object contains errors that will cause the request to fail next time if you do not fix them at this point.

Example of a failed response

Legend

//debug information

debug: false

{
  "code": 124101,
  "message": "cartId already exists",
  "timestamp": "2025-04-23T18:25:43.511Z"
}

debug: true

{
  "code": 124101,
  "message": "cartId already exists",
  "debug": [
    {
      "code": "124102",
      "message": "customerId {0} is linked to itemId {1} in cartId {2} with an active timer"
    },
    {
      "code": "132000",
      "message": "Insufficient permissions to pass {0}"
    },
    {
      "code": "132002",
      "message": "Insufficient permissions to set or modify timer settings"
    }
  ],
  "timestamp": "2025-04-23T18:25:43.511Z"
}