PeBlaze Developer Platform

Payin Integration Guide

Accept UPI payments through a simple server-to-server API. Create an order, present the payment response to the customer, and process the final transaction result through callbacks or status checks.

Production Base URLhttps://api.peblaze.com

AuthenticationMerchant ID + API Key

Content Typeapplication/json

Authentication Methods

Every API request must include both authentication headers. Keep the API key only on your secure backend and never expose it in browser or mobile application source code.

Merchant Identity

merchant-id

Identifies the merchant account making the request. This value is issued by PeBlaze.

API Credential

api-key

Authenticates the request. Treat this value as confidential and rotate it immediately if compromised.

Required Request Headers

Header	Required	Description
Content-Type	Yes	Must be application/json
merchant-id	Yes	Your PeBlaze merchant identifier
api-key	Yes	Your confidential API credential

Content-Type: application/json
merchant-id: YOUR_MERCHANT_ID
api-key: YOUR_API_KEY

Integration Flow

The recommended payment flow keeps sensitive credentials on your backend and treats callbacks as the final source of truth.

1Create Order

Your backend sends the order and customer details.

2Show Payment

Use the returned payment response or intent in your app.

3Receive Callback

PeBlaze posts the final status to your callback URL.

4Verify Status

Use the status API when reconciliation or confirmation is required.

Create Order

Creates a new payin transaction and returns the payment response required to continue the customer payment journey.

POST https://api.peblaze.com/api/v1/payin/create-order

Request Fields

Field	Type	Required
order_id	String	Yes
amount	Number	Yes
username	String	Yes
name	String	Yes
email	String	Yes
mobile_number	String	Yes
user_id	String	Yes
channel_id	String	Yes

curl --request POST \
  --url https://api.peblaze.com/api/v1/payin/create-order \
  --header 'Content-Type: application/json' \
  --header 'merchant-id: YOUR_MERCHANT_ID' \
  --header 'api-key: YOUR_API_KEY' \
  --data '{
    "order_id": "ORD1018",
    "amount": 1,
    "username": "testuser01",
    "name": "Test User",
    "email": "testuser@example.com",
    "mobile_number": "9876543210",
    "user_id": "USER101",
    "channel_id": "TST"
  }'

Order Status

Retrieves the current state of an existing transaction using the PeBlaze transaction ID.

POST https://api.peblaze.com/api/v1/payin/order-status

Request

Send the transaction ID returned during order creation.

Recommended useUse this endpoint for reconciliation, delayed callback checks, or transaction confirmation. Do not continuously poll at a high frequency.

curl --request POST \
  --url https://api.peblaze.com/api/v1/payin/order-status \
  --header 'Content-Type: application/json' \
  --header 'merchant-id: YOUR_MERCHANT_ID' \
  --header 'api-key: YOUR_API_KEY' \
  --data '{
    "transaction_id": "TST17837600783976870"
  }'

Callback Handling

Your callback endpoint should accept JSON, return HTTP 200 quickly, and process each transaction idempotently.

Implementation Rules

Store every callback payload, verify the transaction reference, avoid duplicate wallet or order updates, and acknowledge the request only after safely recording it.

Final Status

Treat the callback or verified order-status response as the final result. Do not mark the order successful only because the payment intent was generated.

Illustrative Callback Payload

The exact callback fields may vary by channel. Your integration should safely ignore unknown fields and preserve the complete raw payload.

{
  "status": "SUCCESS",
  "order_id": "ORD1018",
  "transaction_id": "TST17837600783976870",
  "amount": 1,
  "utr": "123456789012"
}

TST Channel Behaviour

Use the TST channel for predictable end-to-end testing before enabling a live payment channel.

Automatic test callback For channel_id: TST, PeBlaze sends a callback within approximately 10 seconds. The callback result is determined by the last digit of your order_id.

EVEN → SUCCESS

Successful Test

An order number ending in an even digit, such as ORD1018, receives a successful callback.

ODD → FAILED

Failed Test

An order number ending in an odd digit, such as ORD1017, receives a failed callback.

Transaction Statuses

Status	Meaning	Merchant Action
INITIATED / PENDING	Payment is not yet final.	Wait for callback or verify using order-status.
SUCCESS	Payment completed successfully.	Fulfil the order exactly once.
FAILED	Payment was unsuccessful.	Mark the order failed and allow retry.

Production Checklist Use HTTPS for all API and callback traffic, whitelist trusted PeBlaze traffic where applicable, keep credentials on the server, implement idempotency, log raw callbacks, and reconcile transaction status before settling customer orders.

PeBlaze Developer Platform

Payout Integration Guide

Disburse funds to bank accounts through a simple server-to-server API. Initiate a payout, track its progress, and process the final transaction result through callbacks or status checks.

Production Base URLhttps://api.peblaze.com

AuthenticationMerchant ID + API Key

Content Typeapplication/json

Authentication Methods

Every payout API request must include both authentication headers. Keep the API key only on your secure backend and never expose it in browser or mobile application source code.

Merchant Identity

merchant-id

Identifies the merchant account making the request. This value is issued by PeBlaze.

API Credential

api-key

Authenticates the request. Treat this value as confidential and rotate it immediately if compromised.

Required Request Headers

Header	Required	Description
Content-Type	Yes	Must be application/json (not required for GET requests)
merchant-id	Yes	Your PeBlaze merchant identifier
api-key	Yes	Your confidential API credential

Content-Type: application/json
merchant-id: YOUR_MERCHANT_ID
api-key: YOUR_API_KEY

Integration Flow

The recommended payout flow keeps sensitive credentials on your backend and treats callbacks as the final source of truth.

1Check Balance

Confirm sufficient payout balance before initiating a transfer.

2Initiate Payout

Your backend sends the beneficiary bank details and amount.

3Receive Callback

PeBlaze posts the final status to your callback URL.

4Verify Status

Use the status API when reconciliation or confirmation is required.

Initiate Payout

Initiates a new payout transaction and transfers funds to the beneficiary's bank account.

POST https://api.peblaze.com/api/v1/payout/initiate-payment

Request Fields

Field	Type	Required
order_id	String	Yes
amount	Number	Yes
mobile_number	String	Yes
user_id	String	Yes
pg_system	String	Yes
bank_account_name	String	Yes
bank_account_number	String	Yes
bank_ifsc_code	String	Yes
pan	String	No (optional)

curl --request POST \
  --url https://api.peblaze.com/api/v1/payout/initiate-payment \
  --header 'Content-Type: application/json' \
  --header 'merchant-id: YOUR_MERCHANT_ID' \
  --header 'api-key: YOUR_API_KEY' \
  --data '{
    "order_id": "PAYOUT100002",
    "amount": 10,
    "mobile_number": "9876543210",
    "user_id": "USER1001",
    "pg_system": "TST",
    "bank_account_name": "John Doe",
    "bank_account_number": "1234567890123456",
    "bank_ifsc_code": "HDFC0001234",
    "pan": "ABCDE1234F"
  }'

Payout Status

Checks the current state of an existing payout transaction using the PeBlaze transaction ID.

POST https://api.peblaze.com/api/v1/payout/payment-status

Request

Send the transaction ID returned during payout initiation.

Recommended useUse this endpoint for reconciliation, delayed callback checks, or transaction confirmation. Do not continuously poll at a high frequency.

curl --request POST \
  --url https://api.peblaze.com/api/v1/payout/payment-status \
  --header 'Content-Type: application/json' \
  --header 'merchant-id: YOUR_MERCHANT_ID' \
  --header 'api-key: YOUR_API_KEY' \
  --data '{
    "transaction_id": "PAYOUT_TRANSACTION_ID"
  }'

Balance Enquiry

Returns the authenticated merchant's available payout balance. Use this before initiating a payout to confirm sufficient funds.

GET https://api.peblaze.com/api/v1/payout/balance-enquiry

Request

No request body is required. Authentication headers alone determine the merchant account queried.

Header	Required
merchant-id	Yes
api-key	Yes

curl --request GET \
  --url https://api.peblaze.com/api/v1/payout/balance-enquiry \
  --header 'merchant-id: YOUR_MERCHANT_ID' \
  --header 'api-key: YOUR_API_KEY'

Callback Handling

Your callback endpoint should accept JSON, return HTTP 200 quickly, and process each transaction idempotently.

Implementation Rules

Store every callback payload, verify the transaction reference, avoid duplicate wallet or ledger updates, and acknowledge the request only after safely recording it.

Final Status

Treat the callback or verified payment-status response as the final result. Do not mark the payout successful only because the order was accepted or queued.

Illustrative Callback Payload

The exact callback fields may vary by channel. Your integration should safely ignore unknown fields and preserve the complete raw payload.

{
  "status": "SUCCESS",
  "order_id": "PAYOUT100001",
  "transaction_id": "PAYOUT_TRANSACTION_ID",
  "amount": 100,
  "utr": "223456789012"
}

TST Gateway Behaviour

Use pg_system: TST for end-to-end testing before enabling a live payout gateway.

Test gateway Set pg_system to TST in your Initiate Payout request to route the transaction through PeBlaze's test gateway instead of a live banking rail.

Transaction Statuses

Status	Meaning	Merchant Action
INITIATED / PENDING	Payout is not yet final.	Wait for callback or verify using payment-status.
SUCCESS	Payout completed successfully.	Update ledger and mark disbursed exactly once.
FAILED	Payout was unsuccessful.	Reverse the reserved balance and allow retry.

Production Checklist Use HTTPS for all API and callback traffic, whitelist trusted PeBlaze traffic where applicable, keep credentials on the server, check balance before initiating large payouts, implement idempotency, log raw callbacks, and reconcile transaction status before marking beneficiary payouts complete.