Errors

Star SaaS uses standard HTTP response codes to indicate whether an API request was successful or failed. Generally:

2xx codes indicate success.

4xx codes indicate client errors, such as missing required parameters or a failed charge.

5xx codes indicate server-side errors on Stripe’s end, which are rare.

Certain 4xx errors, like a card being declined, come with an error code that provides a brief explanation, allowing for programmatic handling.

When we send an error response, the body will generally contain the following fields:

Response Body Attributes

Item	Description
code	Error code (please refer to reference table)
source	Name of the request parameter that caused the error
message	Description of the error

Common Errors

I0013: Encryption (encryption_data) Error

Make sure sign_key is correct; Noted that the sign_key is case sensitive
Make sure the encryption is via SHA256 method
Make sure the parameters in return_url do NOT contain "&"

I0014: Test sub-account is used in production

The initial merchant account is created in test environment
Merchant needs to use the merchant account in sandbox while developing payment integration
Once complete developing and testing, please reach to us to obtain the merchant account in production

I0015 : Live sub-account is used in Sandbox

After us enables a merchant account to LIVE, merchant need to change the target URLs to live environment URLs.

Error Codes

Acquiring

Issuing

Response Body Attributes#

Common Errors#

I0013: Encryption (encryption_data) Error#

I0014: Test sub-account is used in production#