cURL
Payment Requests
Payment Status
Check payment request status and handle payment notifications
GET
cURL
Overview
Monitor and track payment requests using the status endpoint and handle payment notifications.Get Payment Request Status
Retrieve the current status of a payment request using its identifier.API Endpoint
Authentication
- HTTP Header:
X-API-Keywith your API key obtained from the dashboard - Content Type:
application/json
Request Parameters
Response Fields
Last Log Object
Example Request
Payment Through SFTP
Process batch payments using SFTP file uploads for high-volume transactions.SFTP Configuration
- Credentials: Obtain SFTP address and credentials from the dashboard profile page
- Multiple Providers: Different SFTP addresses may be available for different payment providers
- File Format: Semicolon-delimited CSV without header row
CSV File Format
Each row represents a separate payment with the following fields in order:CSV Example
Payment Notifications
Receive automated notifications about payment status changes via webhooks.Notification Setup
- Configuration: Set notify URL in dashboard profile page
- Method: HTTP POST with
application/x-www-form-urlencodedcontent type - Requirement: Notifications only sent if notify URL is configured
Notification Fields
Example Notification
Notification Verification
Verify notification authenticity using HMAC SHA512 signature.Signature Verification
- Header: Check
X-Signatureheader in notification request - Algorithm: HMAC SHA512 hash in Base64 format
- Key: Use your API key from the control panel
Verification Process
Error Codes
Complete list of error codes and descriptions for troubleshooting.Payment Processing Errors (001-020)
Limit and Validation Errors (021-048)
System Errors (998-999)
Best Practices
Status Checking
- Polling: Check status periodically, not continuously
- Rate Limiting: Respect API rate limits
- Error Handling: Handle network timeouts and API errors gracefully
SFTP Batch Processing
- File Validation: Validate CSV format before upload
- Error Monitoring: Monitor notification responses for batch failures
- Batch Size: Consider optimal batch sizes for your volume
Notification Handling
- Signature Verification: Always verify notification signatures
- Idempotency: Handle duplicate notifications gracefully
- Response Time: Respond to notifications quickly (< 30 seconds)
- Error Handling: Return appropriate HTTP status codes
Security
- API Key Protection: Keep API keys secure and rotate regularly
- HTTPS Only: Use HTTPS for all API communications
- Signature Verification: Always verify webhook signatures
- Error Logging: Log errors without exposing sensitive data
Path Parameters
Response
OK

