This table provides detailed interpretations of the return codes that may appear in the ret_code parameter of Pockyt API responses.

Return Code	Detailed Meaning
000000	Indicates an error within Pockyt's system. Contact solutions@pockyt.io for more information.
000010	The API version specified in the request is incorrect or not supported.
000020	A required parameter in the API request is missing.
000021	The provided parameter does not correspond to any relevant information in the system.
000022	There's a mismatch between provided parameters, suggesting an inconsistency in the request.
000023	The value assigned to one or more parameters is incorrect or in an invalid format.
000030	The request was denied due to lack of proper access rights or permissions.
000040	There's an issue with the status of the transaction being processed.
000080	An error occurred within the system of an external supplier or partner involved in the transaction.
000100	The API call was successful and the transaction or request was processed correctly.

During the integration process with Pockyt's APIs, developers may encounter various errors. Common errors are below:

Incorrect Base URL or Path: the base URL is not correctly set to the sandbox environment during testing phases, or the path specified in the URL is incorrect.
Missing Required Fields: not all the mandatory fields are included in the API request or requests are sent with empty values.
Duplicate Reference Numbers in Pay-Ins: For Pay-Ins, submitting duplicate reference numbers can lead to errors. Each transaction should have a unique reference number.
Improper Formatting in Payouts: For Payouts, errors can occur due to improperly formatted fields, particularly date and time fields. It's important to adhere to the expected format standards for these fields to ensure correct data interpretation.
Verification Signature (verifySign) Errors: Errors in calculating the verifySign value are a common source of issues. The verifySign parameter must be accurately calculated as it plays a crucial role in authenticating and securing API calls..

Common Errors

Data Error: verifySign

Cause	Fix
Incorrect MD5 signature encryption.	Refer to the documentation for proper signature configuration.
Passing null parameters	Verify the correct parameter values as per documentation.

Cause	Fix
Incorrect timestamp format.	Follow the standard timestamp format in the documentation. correct format should be "yyyy-mm-ddTHH:MM:SSZ"

Cause	Fix
Incorrect bank account parameters.	Provide a valid value or remove the field from the request.

Cause	Fix
Fatal error encountered.	Review request details for missing or invalid data.

Cause	Fix
Missing credentials like `customerNo`, `transactionNo`, or `reference` for specific workflows.	Ensure credentials are saved correctly and passed as needed.

Cause	Fix
Check `"vendor": ""` Configuration	Read the documentation for finding the valid options. The possible payment channels are "alipay", "wechatpay", "paypal", "venmo", "unionpay", "creditcard" "truemoney", "alipay_hk", "tng", "gcash", "dana", "kakaopay", "bkash", "easypaisa","cashapppay"

Cause	Fix
Using both TransactionNo and reference in the request body	Just choose one of the two.

Cause	Fix
Invalid parameter values, e.g., using a different `profileType` than the default `INDIVIDUAL`.	Verify the correct parameter values as per documentation.