Payment Transactions
Fetch Payment
Retrieve details of a specific payment by ID
Overview
The Fetch Payment endpoint allows you to retrieve detailed information about a specific payment using its unique identifier. This is useful for checking payment status, verifying transaction details, or retrieving customer information associated with the payment.
Endpoint
Authentication
All requests must include your API key in the Authorization header:
Path Parameters
The unique identifier of the payment to retrieve.
- Format: UUID v4
- Example:
2315fca8-9aec-42ee-8bee-a9d10add170e
Response Structure
The payment details object
Examples
Response Examples
Error Handling
Status Code | Description | Possible Solution |
---|---|---|
401 | Invalid or missing API key | Check your API key and authorization header |
403 | Permission denied | Verify your API key has correct permissions |
404 | Payment not found | Verify the payment ID exists and is valid |
429 | Rate limit exceeded | Implement exponential backoff |
500 | Internal server error | Contact support |
Best Practices
Error Handling
Error Handling
- Implement proper error handling for all status codes
- Use exponential backoff for retries
- Log errors with payment IDs for debugging
- Handle network timeouts appropriately
Security
Security
- Never log complete payment details
- Keep API keys secure
- Use HTTPS for all API calls
- Validate payment IDs before making requests
Performance
Performance
- Cache payment details when appropriate
- Implement request timeouts
- Monitor API response times
- Use connection pooling for multiple requests
Rate Limits
This endpoint is subject to rate limiting:
- 100 requests per minute per API key
- Rate limit info included in response headers:
- X-RateLimit-Limit
- X-RateLimit-Remaining
- X-RateLimit-Reset
Need Help?
For additional assistance:
- Check our Error Handling Guide
- Contact Support
- Join our Discord community