RESTful API v1.4 • OpenAPI 3.0 Specs

Universal Payment API
Engineered for High Scale

Integrate high-speed Payin collections and 24×7 Payout disbursals with clean, predictable REST APIs. Built on strict HTTP semantics, bearer token security, idempotency safeguards, and cryptographically signed webhooks.

<250ms API Hop Latency
99.99% Core SLA
50+ Banking Rails
Latency: ~124ms
curl -X POST "https://api.rpointtech.com/v1/payin/orders" \
            -H "Authorization: Bearer rpt_live_998877665544332211" \
            -H "Content-Type: application/json" \
            -H "Idempotency-Key: idemp_ord_8839210" \
            -d '{
                "amount": 250000,
                "currency": "INR",
                "customer": {
                "name": "Arjun Singhania",
                "email": "arjun@enterprise.in",
                "phone": "+919876543210"
                },
                "payment_method": "upi_intent",
                "notify_url": "https://yourdomain.com/webhooks/rpoint"
            }'
Security & Architecture Standards

Built on Strict Engineering Standards

Consistent paradigms across every endpoint, ensuring seamless developer onboarding and zero integration ambiguity.

RFC 6750

Bearer Token Authentication

Authenticate every REST request by supplying your confidential API secret key in the HTTP Authorization header using the standard Bearer format.

Authorization: Bearer rpt_live_...
IETF Draft

Idempotency Key Safeguards

Supply an Idempotency-Key header with a unique nonce (UUIDv4). If a network glitch re-transmits a call, our engine safely returns the cached transaction.

Idempotency-Key: idemp_984920...
SHA-256

HMAC-SHA256 Signatures

Every incoming event callback carries an X-RPoint-Signature header computed from raw payload and your webhook secret to prove authenticity.

X-RPoint-Signature: 7f8a9b2...
REST API Specification

Core Payment REST Endpoints

Explore primary resources for real-time payment ingestion, automated disbursals, transaction status querying, and customer reversals.

POST /v1/payin/orders
Payin Rail

Create Payin Collection Order

Initializes a payment order and generates UPI Intent URI, dynamic QR string, and hosted checkout redirect URL for multi-channel collection.

Key Request Parameters:
amount (paise) currency customer payment_method notify_url
Response: 201 Created Avg Latency: ~180ms
POST /v1/payout/transfers
Payout Rail

Execute 24×7 Instant Disbursal

Disburses funds instantly to beneficiary bank accounts or UPI VPAs via IMPS, NEFT, RTGS, and UPI with intelligent route failover.

Key Request Parameters:
beneficiary_account ifsc vpa amount transfer_mode purpose
Response: 200 OK Avg Latency: ~220ms
GET /v1/transactions/{id}
Reconciliation

Query Transaction & Bank UTR

Retrieves authoritative payment status, bank clearing timestamps, settled net amounts, and bank UTRs for automated ledger closing.

Key Path & Query Parameters:
id (Order ID / RPoint Ref) include_events (boolean)
Response: 200 OK Avg Latency: ~95ms
POST /v1/refunds
Reversals

Trigger Automated Customer Refund

Initiates full or partial refunds directly back to source payment rails with automatic failover to IMPS payout if the source route is congested.

Key Request Parameters:
order_id amount reason speed (instant / standard)
Response: 200 OK Avg Latency: ~240ms
Asynchronous Event Engine

Cryptographically Signed Webhooks

Receive sub-second JSON event notifications whenever payments settle, transfers disburse, or disputes open.

01

Event Dispatch

When bank confirmation lands on RPoint rails, an HTTP POST event (e.g. order.paid) is dispatched to your configured endpoint within 250ms.

02

Signature Verification

Verify the payload using hash_hmac('sha256', $body, $secret) against the X-RPoint-Signature header to verify origin.

03

Exponential Retries

If your listener fails or returns a non-200 code, our worker automatically retries across 5 exponential intervals over 24 hours.

Error Handling Specification

Explicit & Predictable HTTP Status Codes

Clear error responses allow your application to handle failure edge cases gracefully and keep user trust intact.

200 / 201 Success / Created

The request was validated and executed successfully. Contains the full transaction payload with unique identifiers and timestamps.

400 Bad Request Payload Validation Error

Missing mandatory parameters, invalid currency code, unsupported payment method, or improperly formatted JSON structure.

401 Unauthorized Invalid API Key

Bearer token is missing, expired, revoked, or does not correspond to an active merchant environment.

429 Rate Limited Concurrency Threshold

Request quota exceeded. Standard accounts accommodate 100 req/sec with automated burst pooling.

Developer FAQ

Frequently Asked Questions — Payment API

Quick answers to common architecture, authentication, and integration questions.

We maintain an isolated Sandbox environment (https://sandbox.api.rpointtech.com/v1) populated with mock banking gateways, simulating successful settlements, bank network timeouts, and reversal callbacks.
Compute a SHA-256 HMAC of the raw request payload using your secret webhook key: hash_hmac('sha256', $rawBody, $webhookSecret). Compare this signature with the incoming X-RPoint-Signature header using hash_equals() to prevent timing attacks.
For Payout API endpoints, IP whitelisting is enforced as an additional layer of security to prevent unauthorized disbursements even in the unlikely event of API key exposure. For Payin API requests, IP whitelisting is optional but supported.
Idempotency keys are cached in high-speed in-memory storage for exactly 24 hours. Any request received with an existing idempotency key within that window returns the original transaction outcome without executing additional bank debits.

Ready to Scale Your Payments with RPoint Tech?

Experience high-throughput Payin collections and 24x7 automated Payout disbursals. Go live with our developer-first APIs in under 48 hours.

Get API Credentials Explore API Docs