API Documentation - LogicLoom

Create Payment

Initiate a UPI pay-in and receive an intent URL.

POST /api/payments/create

Endpoint

https://logicloom.pro/api/payments/create

Headers

Content-Type application/json

Request body

authEmail string

Merchant email

amount float

Transaction amount

mobileNumber string

Customer's mobile number

custRefNum string

Unique reference number

custEmail string

Customer's email

custName string

Customer's name

apiKey string

API key for authorization

Example request

{
  "authEmail": "[email protected]",
  "amount": 11.0,
  "mobileNumber": "9874561230",
  "custRefNum": "REF1122334479688",
  "custEmail": "[email protected]",
  "custName": "Tester",
  "apiKey": "YourAPIKeyFromLogicLoom"
}

Success response — 200

status

e.g. "success"

custRefNum

Unique ID for the transaction

message

Status update message

amount

Amount

upiIntentUrl

URL for UPI payment

{
  "status": "success",
  "custRefNum": "REF1122334479688",
  "message": "Payment initiated successfully",
  "amount": 11,
  "upiIntentUrl": "pay://payment_url"
}

Initiate Payout

Fund transfer (payout) to a bank beneficiary.

POST /api/merchant/initiate-fund-transfer

Endpoint

https://logicloom.pro/api/merchant/initiate-fund-transfer

Headers

Content-Type application/json

Authentication

Send credentials in the JSON body. apiKey must be present in the body (required by IP restriction middleware).

apiKey string

Merchant API key (required in body)

authEmail string

Merchant email

Headers x-api-key / x-auth-email may also be sent, but apiKey must still be in the body for the IP middleware.

Request body

apiKey string

Merchant API key

authEmail string

Merchant email

custRefNum string

Unique merchant reference for this payout

amount number

Payout amount in INR — must be a JSON number, not a string

beneficiary object

Bank beneficiary details (see nested fields below)

beneficiary object

name string

Account holder name

accountNumber string

Bank account number

ifscCode string

IFSC

bankName string

Bank name

Business rules

Merchant must have payout enabled (payOutEnabled)
Amount must be within the merchant’s min/max payout limits
Balance check uses dashboard payout wallet balance (calculateMerchantStats → usableBalance)
Merchant IP whitelist applies when IP restriction is enabled

Example request

{
  "apiKey": "YourAPIKeyFromLogicLoom",
  "authEmail": "[email protected]",
  "custRefNum": "POUTREF123456",
  "amount": 500,
  "beneficiary": {
    "name": "John Doe",
    "accountNumber": "157077599947",
    "ifscCode": "INDB0002341",
    "bankName": "INDUSIND Bank"
  }
}

Error cases

Case	Description
Missing auth	Missing `apiKey` or `authEmail` in body
Payout disabled	Merchant does not have `payOutEnabled`
Limit exceeded	Amount outside merchant min/max payout limits
Insufficient balance	Payout wallet `usableBalance` is too low
IP blocked	Request IP not on merchant whitelist (when IP restriction is enabled)
Invalid amount	`amount` sent as a string instead of a JSON number

Check Status

Look up a pay-in by merchant reference or transaction ID.

POST /api/merchant/check-status

Endpoint

https://logicloom.pro/api/merchant/check-status

Request body

Provide either custRefNum or transactionId.

authEmail string

Merchant email

apiKey string

API key for authorization

custRefNum optional

Merchant reference number

transactionId optional

Gateway / internal transaction ID

Example — by custRefNum

{
  "authEmail": "[email protected]",
  "apiKey": "YourAPIKeyFromLogicLoom",
  "custRefNum": "REF1122334479688"
}

Example — by transactionId

{
  "authEmail": "[email protected]",
  "apiKey": "YourAPIKeyFromLogicLoom",
  "transactionId": "TXN9876543210"
}

Success response — 200

custRefNum

Merchant reference

transactionId

Transaction ID

amount

Transaction amount

status

Current pay-in status

{
  "custRefNum": "REF1122334479688",
  "transactionId": "TXN9876543210",
  "amount": 11,
  "status": "success"
}

Error responses

HTTP	Message
400	authEmail and apiKey are required.
400	Provide custRefNum or transactionId.
401	Invalid Email or API key.
404	Transaction not found.
500	Failed to check transaction status

Callback Notification

Posted to your configured callbackUrl after pay-in or payout completion.

Pay-in callback

custRefNum

Reference number

status

success or failed

amount

Transaction amount

message

Status message

date

ISO 8601 timestamp

{
  "custRefNum": "REF1122334479688",
  "status": "success",
  "amount": 101.00,
  "message": "Success",
  "date": "2024-11-08T09:19:03.431Z"
}

Payout callback

custRefNum

Merchant payout reference

txnId

Payout transaction ID

status

e.g. Completed

amount

Payout amount

utrNumber

Bank UTR number

message

Status message

date

Timestamp

{
  "custRefNum": "POUTREF123456",
  "txnId": "HSBTPO...",
  "status": "Completed",
  "amount": 500,
  "utrNumber": "...",
  "message": "Payout Successful",
  "date": "..."
}

Error Codes

Common Create Payment error codes.

Code	Meaning
`INVALID_API_KEY`	API key is invalid
`INVALID_AMOUNT`	Invalid amount
`MISSING_PARAMETERS`	Required parameters are missing
`GENERAL_ERROR`	General error occurred