Technical Q&A

Common technical questions and answers for PayHub API integrators.

Authentication & Security

Q1. Is it required to use a specific API version?
A. No.

Q2. Is it required to use special containers or an SDK?
A. No.

Q3. Can different data types appear in request/response?
A. Yes — for example, an integer in the request and a string in the response.

Q1. What are the possible transaction statuses?
A. success, failed, expired, chargeback

Q2. Which operational statuses are considered final?
A. success, failed, expired, chargeback

⚠️
Note:

expired may later become success (late bank confirmation)

success may later become chargeback or failed

Q3. Which statuses can only be received after a redirect?
A. success, failed, expired, chargeback

Q4. Is a transaction created before redirect?
A. Yes.

Q5. Can the customer change the deposit amount in the UPI app?
A. No — the amount cannot be modified.

Q1. What are the possible transaction statuses?
A. pending, success, failed

Q2. Which statuses are final?
A. success, failed

Q1. Which transaction statuses trigger callbacks?
A. Only final statuses trigger callbacks.

Q2. What is the webhook retry mechanism?
A. If your endpoint is unavailable, retries occur:

Q3. How should errors be handled if the server responds with a non-200 status?
A. Treat the request as failed or rejected.

Q1. Which base URLs should be used?

Q2. What is the lifetime of the redirect URL (responseData.url)?
A. The URL expires in 15 minutes and cannot be configured.

Q1. What are the possible error codes?

Payins:

Payouts:

Q2. Are icons for GSX and payment methods (UPI, IMPS) available?
A. Yes.

Q1. Do you support currencies with 0 or 3 minor units (e.g., KWD 15.375)?
A. Amounts with up to 2 decimal places are recommended (e.g., 2.35).