123hub Payment Gateway API
123hub is a modern payment gateway that enables merchants to accept payments, process payouts, and manage their financial operations through a single API endpoint using method-based routing.Quick Start
Get up and running with your first API call in minutes
Authentication
Learn how to authenticate with Application ID and SHA512 hash
Payments Guide
Create deposits, withdrawals, and check payment status
Webhooks
Receive real-time notifications about payment events
How It Works
All API interactions go through a single POST endpoint with method-based routing. Instead of different URLs for different operations, you specify themethod field in the request body.
Example Request
Example Response
Available Methods
| Method | Description |
|---|---|
payment.in | Create an incoming payment (deposit) |
payment.out | Create an outgoing payment (withdrawal/payout) |
payment.status | Check the status of an existing payment |
balance.get | Retrieve your account balance |
gateway.ping | Health check to verify connectivity and authentication |
Features
Multiple Payment Methods
Multiple Payment Methods
Accept payments via bank transfers, cash payments, card payments, and cryptocurrency. Multiple currencies supported (ARS, BRL, CNY, COP, EUR, GEL, MXN, USD, UYU).
Real-time Webhooks
Real-time Webhooks
Receive instant notifications when payment status changes. Secure webhook delivery with SHA512 signatures and automatic retries.
Single Endpoint, Method-Based Routing
Single Endpoint, Method-Based Routing
All API operations go through one URL. The
method field in the request body determines the action. Simplifies integration and reduces configuration overhead.Unified Response Format
Unified Response Format
Every response follows the same envelope structure with
success, result, error, request_id, and processing_time fields. Successful responses return HTTP 200, errors return HTTP 400 (or 404 for unknown methods).Base URL
All API requests are made to:All requests use the
POST method. The same endpoint is used for both test and production environments. Your credentials determine which environment is active.Authentication
Every request requires two headers:| Header | Description |
|---|---|
X-Data-Application-Id | Your application ID (integer) |
X-Data-Hash | SHA512 hex hash of requestBody + secretKey |
Supported Payment Methods
| Method | Type | Description | Processing Time |
|---|---|---|---|
spei | Bank Transfer | Mexican interbank transfer system (SPEI) | Up to 30 minutes |
oxxo | Cash | Pay at 20,000+ OXXO convenience stores | Up to 30 minutes |
card | Card | Credit and debit cards (tokenized) | Up to 30 minutes |
bank_transfer | Bank Transfer | Generic bank transfer | Up to 30 minutes |
cash | Cash | Cash payments | Up to 30 minutes |
crypto | Cryptocurrency | Crypto payments (USDT, etc.) | Up to 30 minutes |
Supported Currencies
| Currency | Code | Country | Default Method |
|---|---|---|---|
| Argentine Peso | ARS | Argentina | bank_transfer |
| Brazilian Real | BRL | Brazil | bank_transfer |
| Chinese Yuan | CNY | China | bank_transfer |
| Colombian Peso | COP | Colombia | bank_transfer |
| Euro | EUR | Europe | bank_transfer |
| Georgian Lari | GEL | Georgia | bank_transfer |
| Mexican Peso | MXN | Mexico | spei |
| US Dollar | USD | International | bank_transfer |
| Uruguayan Peso | UYU | Uruguay | bank_transfer |
Response Format
All responses follow a consistent envelope:Success Response (HTTP 200)
Error Response (HTTP 400)
