Overview
Retrieve the current status of a payment request using its identifier.API Endpoint
Authentication
- HTTP Header:
X-API-Key
with your API key obtained from the dashboard - Content Type:
application/json
Request Parameters
Parameter | Description | Required |
---|---|---|
{id} | Payment request identifier from payment creation response | YES |
Response Fields
Field | Description | Type |
---|---|---|
id | Payment request identifier | string/integer |
recipientName | Payment recipient name | string |
paymentRequestStatusId | Payment request status: 1 – paid 2 – unpaid 3 – cancelled | integer |
transactionId | Created transaction internal identifier | string/integer |
transactionNumber | Created transaction public identifier | string |
transactionStatusId | Created transaction status: 0 – waiting 1 – approved 2 – declined 3 – pending | integer |
link | Payment request link to customer-facing web page | string |
unit | Payment currency | string |
amount | Payment amount | number |
referenceId | Custom reference details | string |
notes | Payment notes | string |
client | Payment sender customer object | object |
notifyUrl | Webhook URL for payment status notifications | string |
successUrl | Redirect URL on successful payment | string |
failureUrl | Redirect URL on failed payment | string |
lastLog | Last payment attempt status and message | object |
Last Log Object
Field | Description | Type |
---|---|---|
transactionStatusId | Last payment attempt status: 0 – waiting 1 – approved 2 – declined 3 – pending | integer |
message | Last payment attempt message | string |
code | Last payment attempt code | string |
Example Request
Status Codes
Payment Request Status
- 1 – Paid
- 2 – Unpaid
- 3 – Cancelled
Transaction Status
- 0 – Waiting
- 1 – Approved
- 2 – Declined
- 3 – Pending
Best Practices
Status Checking
- Polling Frequency: Check status periodically, not continuously
- Rate Limiting: Respect API rate limits to avoid throttling
- Error Handling: Handle network timeouts and API errors gracefully
- Caching: Cache successful responses to reduce API calls
Implementation Tips
- Store payment request IDs securely for status tracking
- Implement exponential backoff for failed requests
- Use webhooks for real-time updates instead of constant polling
- Log status changes for audit trails
Integration Example
Path Parameters
Response
OK