Introduction
Getting started with the JPL Payments Gateway API.
Getting Started with JPL Payments Gateway
Welcome to the JPL Payments Gateway API documentation. This guide will help you get started with integrating payment processing into your application.
Overview
The JPL Payments Gateway provides a robust and secure platform, aligned with PCI DSS level 1 compliance standards for processing payments, managing collections, and handling financial transactions. Our API is designed to be developer-friendly with clear endpoints and comprehensive error handling.
Key Features
- Secure Payment Processing: Aligned with PCI DSS level 1 compliance standards
- Multiple Payment Methods: Support for various payment channels
- Comprehensive API: Full-featured REST API with detailed documentation
Base URL
All API requests should be made to:
Production: https://api.gateway.justtap.io
Sandbox: https://api-uat.gateway.justtap.io[!TIP] Always use the sandbox environment for testing and development. Switch to production only when you're ready to process real transactions.
Quick Start
Here's a simple example to get you started with the JPL Payments Gateway:
1. Obtain Your API Credentials
Before you can make API calls, you'll need:
- API Key: Used to authenticate your requests
See the Authentication section for detailed instructions.
2. Make Your First Request
Here's an example of checking the API status:
curl -X GET https://api-uat.gateway.justtap.io/health \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json"Common Response Codes
| Status Code | Meaning | Description |
|---|---|---|
| 200 | OK | Request successful |
| 201 | Created | Resource created successfully |
| 202 | Accepted | Request accepted for processing |
| 400 | Bad Request | Invalid request parameters |
| 401 | Unauthorized | Missing or invalid authentication |
| 403 | Forbidden | Insufficient permissions |
| 404 | Not Found | Resource not found |
| 422 | Unprocessable Entity | Validation error |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server error occurred |
Next Steps
Now that you understand the basics, explore these sections:
- Authentication - Learn how to authenticate your API requests
- Collections - Start processing payments and collections