Pay2Fast Mobile Recharge Api Selling API Integration Guide

🚀 Quick Start

To enable an API User, first complete the configuration on the API Configuration page. An API request is accepted only when the token, API User status, callback URL, and source IP all pass validation.

⚙️ API Configuration

After logging in as an API User, configure the following information from Sidebar → API Configuration.

🔐 Authentication

Every customer API request must send the generated API Token as a Bearer Token.

Authorization: Bearer YOUR_API_TOKEN
Content-Type: application/json
Accept: application/json

📱 Recharge API

Use this endpoint to create a mobile recharge request.

Request Body

curl -X POST "https://samadigital.us.cc/api/v1/recharge.php" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "mobile": "9876543210",
    "operator": "JIO",
    "operator_code": "JIO",
    "service_type": "prepaid",
    "amount": 199,
    "client_txn_id": "ORDER-10001"
  }'

Typical Response

{
  "status": "pending",
  "transaction_id": "RCH_123",
  "client_txn_id": "ORDER-10001",
  "provider_txn_id": null,
  "message": "Accepted"
}

🔎 Transaction Status API

Use this endpoint to get the latest status of a recharge transaction. An API User can only view their own transactions.

curl -X GET "https://samadigital.us.cc/api/v1/status.php?transaction_id=RCH_123" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Accept: application/json"

{
  "status": "success",
  "transaction_id": "RCH_123",
  "client_txn_id": "ORDER-10001",
  "provider_txn_id": "PROV-778899"
}

Possible status: pending, success, failed.

📩 Your Response / Callback URL

When a transaction result is available, Pay2Fast sends a JSON POST to the URL configured under the API User's API Configuration → Response / Callback Page.

POST https://your-domain.com/api/callback.php
Content-Type: application/json

{
  "status": "success",
  "transaction_id": "RCH_123",
  "client_txn_id": "ORDER-10001",
  "provider_txn_id": "PROV-778899",
  "message": "Recharge successful"
}

🔁 Provider Callback Endpoint

This is for the upstream recharge provider → Pay2Fast callback. It is different from the API User's own callback URL.

POST https://samadigital.us.cc/api/v1/callback.php
Content-Type: application/json
X-Callback-Signature: YOUR_HMAC_SHA256_SIGNATURE

{
  "transaction_id": "RCH_123",
  "client_txn_id": "ORDER-10001",
  "provider_txn_id": "PROV-778899",
  "status": "success",
  "message": "Recharge successful"
}

If a callback secret is configured under Admin → API Providers, generate an HMAC-SHA256 signature from the exact raw JSON body and send it in the X-Callback-Signature header.

📋 Supported Operator Codes

If the provider uses its own operator IDs, Admin-side mapping can translate them into the provider code.

⚠️ HTTP Response Codes

💻 PHP Server-to-Server Example

<?php
$token = 'YOUR_API_TOKEN';
$url = 'https://samadigital.us.cc/api/v1/recharge.php';

$data = [
    'mobile' => '9876543210',
    'operator' => 'JIO',
    'operator_code' => 'JIO',
    'service_type' => 'prepaid',
    'amount' => 199,
    'client_txn_id' => 'ORDER-10001'
];

$ch = curl_init($url);
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $token,
        'Content-Type: application/json',
        'Accept: application/json'
    ],
    CURLOPT_POSTFIELDS => json_encode($data)
]);

$response = curl_exec($ch);
$httpCode = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo $httpCode . "\n";
echo $response;

JavaScript / Browser Note

🛡️ Security Checklist