Credit Card
Welcome to the Manjo Gate API Documentation for the Credit Card (CC) module. This guide provides comprehensive details on how to integrate with the Gate system to process Credit Card transactions, retrieve transaction records, and handle webhooks for asynchronous payment status updates.
Overview
The Gate API provides a unified endpoint for creating various transactions, including Credit Cards. To initiate a credit card payment, you interact with the centralized transaction/create endpoint. Once the customer completes the payment through the gateway, the Gate system verifies the payment and dispatches an HTTP POST request to your specified webhook URL (callback_url).
Authentication
The Gate API uses API Keys (X-API-KEY) for authentication. For server-to-server integration, include the following header in your API requests:
| Header | Value | Required | Description |
|---|---|---|---|
X-API-KEY |
<your_api_key> |
Yes | API Key provided by Manjo |
Content-Type |
application/json |
Yes | Request payload format |
X-API-KEY: <your_api_key>
Content-Type: application/json
Endpoints
| Page | Path | Purpose |
|---|---|---|
| Create Transaction | POST /api/v1/transaction/create |
Create a new CC payment request and get the redirect payment URL. |
| Payment Callback | POST {your_callback_url} |
Handle real-time webhook callback notifications from Gate upon payment completion. |
Payment Workflow
- Initiate Payment: Your backend sends a
POST /api/v1/transaction/createrequest withmethod: 4and payment details. - Redirect Customer: Extract
payment_urlfrom the API response and redirect the customer to the secure payment gateway page. - Customer Pays: The customer completes the card details and authorization on the gateway page.
- Gateway Redirect: Upon completion, the customer is redirected back to your
redirect_url. - Asynchronous Webhook: Manjo Gate sends a real-time HTTP POST callback payload to your
callback_url. - Fulfill Order: Your server verifies
trx_idand fulfills the order.
Notes
- Payment Method Enum:
method: 4specifically maps to Credit Card. - Payment Expiration: You can pass
expired_datein ISO 8601 (e.g.2026-12-31T23:59:59+07:00) or local datetime format. - Idempotency: Webhook callbacks must be handled idempotently using
trx_id.