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.
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"
}'
Consistent paradigms across every endpoint, ensuring seamless developer onboarding and zero integration ambiguity.
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_...
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...
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...
Explore primary resources for real-time payment ingestion, automated disbursals, transaction status querying, and customer reversals.
Initializes a payment order and generates UPI Intent URI, dynamic QR string, and hosted checkout redirect URL for multi-channel collection.
Disburses funds instantly to beneficiary bank accounts or UPI VPAs via IMPS, NEFT, RTGS, and UPI with intelligent route failover.
Retrieves authoritative payment status, bank clearing timestamps, settled net amounts, and bank UTRs for automated ledger closing.
Initiates full or partial refunds directly back to source payment rails with automatic failover to IMPS payout if the source route is congested.
Receive sub-second JSON event notifications whenever payments settle, transfers disburse, or disputes open.
When bank confirmation lands on RPoint rails, an HTTP POST event (e.g. order.paid) is dispatched to your configured endpoint within 250ms.
Verify the payload using hash_hmac('sha256', $body, $secret) against the X-RPoint-Signature header to verify origin.
If your listener fails or returns a non-200 code, our worker automatically retries across 5 exponential intervals over 24 hours.
Clear error responses allow your application to handle failure edge cases gracefully and keep user trust intact.
The request was validated and executed successfully. Contains the full transaction payload with unique identifiers and timestamps.
Missing mandatory parameters, invalid currency code, unsupported payment method, or improperly formatted JSON structure.
Bearer token is missing, expired, revoked, or does not correspond to an active merchant environment.
Request quota exceeded. Standard accounts accommodate 100 req/sec with automated burst pooling.
Quick answers to common architecture, authentication, and integration questions.
https://sandbox.api.rpointtech.com/v1) populated with mock banking gateways, simulating successful settlements, bank network timeouts, and reversal callbacks.
hash_hmac('sha256', $rawBody, $webhookSecret). Compare this signature with the incoming X-RPoint-Signature header using hash_equals() to prevent timing attacks.