Skip to main content

Payin Notification

GET

The Payin Notification API retrieves partner wallet transaction records for a specified date range and customer. The response provides detailed transaction information including transaction identifiers, wallet details, amounts, currencies, transaction type, balances, fees, status, payment mode, purpose of payment, token and other transaction attributes.

A query endpoint, not a push notification

This is a GET statement query: you call it to retrieve transaction records. RHUB has not documented any webhook, callback or push behaviour for it.

Query Parameters​

ParameterExampleDescription
sortBycreationDateField used to sort the transaction records.
limit500Maximum number of records requested.
sortdescSort direction.
fromDate2026-08-01Start date for the transaction search.
toDate2026-09-01End date for the transaction search.
walletCode1000070032Wallet code used for the statement query.
selectedCategory100008Transaction category.
transactionIdnullTransaction ID filter.
sendClientCustomerCode100000909313736ICustomer identifier used to filter transactions.
transactionType100002Transaction type.
transactionSubType100002Transaction subtype.

A complete request appends the query string to the endpoint path. The template below carries the placeholders exactly as RHUB supplies them:

GET /ewallet/api/v1/miniStatement/partnerStatement?sortBy=creationDate&limit=500&sort=desc&fromDate={formDate}&toDate={toDate}&walletCode={walletCode}&selectedCategory=100008&transactionId=null&sendClientCustomerCode={customerId}&transactionType=100002&transactionSubType=100002

With the documented example values:

GET /ewallet/api/v1/miniStatement/partnerStatement?sortBy=creationDate&limit=500&sort=desc&fromDate=2026-08-01&toDate=2026-09-01&walletCode=1000070032&selectedCategory=100008&transactionId=null&sendClientCustomerCode=100000909313736I&transactionType=100002&transactionSubType=100002
Placeholder spelling

The parameter is fromDate; the placeholder RHUB supplies for it is written {formDate}. Both are reproduced exactly as given.

Response​

Example values are synthetic. The structure, field names, nesting and data types are as returned.

{
"transactionId": "null",
"requestTime": "Tue Oct 06 15:57:44 IST 2026",
"responseTime": "Tue Oct 06 15:57:44 IST 2026",
"resultCode": "0",
"resultDescription": "Transaction successful",
"pageable": {
"limit": 500,
"totalRecords": 9,
"sort": "desc",
"sortBy": "creationDate"
},
"miniStatement": {
"walletTransactionList": [
{
"id": 100001,
"code": "1000100001",
"transactionId": "200001",
"fromWalletOwnerCode": "1000000001",
"toWalletOwnerCode": "1000000002",
"fromWalletOwnerName": "EXAMPLE1234",
"toWalletOwnerName": "John Doe",
"toWalletOwnerMsisdn": "9876543210",
"fromAmount": 90.0,
"fromWalletCode": "1000000010",
"fromWalletName": "Main Wallet",
"toWalletCode": "1000000020",
"toWalletName": "Main Wallet",
"fromCurrencyCode": "100003",
"toCurrencyCode": "100003",
"fromCurrencyName": "USD-USA",
"toCurrencyName": "USD-USA",
"fromCurrencySymbol": "$",
"toCurrencySymbol": "$",
"transactionTypeCode": "100002",
"transactionTypeName": "Received from send client",
"creationDate": "2026-08-31 19:21:54",
"fee": 10.0,
"status": "SUCCESS",
"srcPostBalance": -4910.0,
"srcPreviousBalance": -5000.0,
"destPreviousBalance": 10000.0,
"destPostBalance": 10080.0,
"transactionAmount": 100.0,
"fromWalletTypeCode": "100008",
"toWalletTypeCode": "100008",
"debitAmount": 0.0,
"creditAmount": 80.0,
"postBalance": 10080.0,
"payoutFee": 10.0,
"rate": 0.0,
"rateAfterMargin": 0.0,
"remarkToClient": "Example client remark",
"paymentMode": "NA",
"toRemittanceUserType": "100000",
"purposeOfPaymentCode": "PREP",
"purposeOfPaymentName": "Pre-Fund",
"featureCode": "100054",
"token": "TKN1234567",
"toAmount": 80.0
}
]
}
}

Response Parameters​

Types and examples are taken from the response above. RHUB has not supplied field descriptions, requirement flags or lengths for this API, so none are stated here.

Top level​

FieldTypeExample
transactionIdString"null"
requestTimeStringTue Oct 06 15:57:44 IST 2026
responseTimeStringTue Oct 06 15:57:44 IST 2026
resultCodeString0
resultDescriptionStringTransaction successful

pageable​

FieldTypeExample
limitNumber500
totalRecordsNumber9
sortStringdesc
sortByStringcreationDate

miniStatement.walletTransactionList[]​

FieldTypeExample
idNumber100001
codeString1000100001
transactionIdString200001
fromWalletOwnerCodeString1000000001
toWalletOwnerCodeString1000000002
fromWalletOwnerNameStringEXAMPLE1234
toWalletOwnerNameStringJohn Doe
toWalletOwnerMsisdnString9876543210
fromAmountNumber90.0
fromWalletCodeString1000000010
fromWalletNameStringMain Wallet
toWalletCodeString1000000020
toWalletNameStringMain Wallet
fromCurrencyCodeString100003
toCurrencyCodeString100003
fromCurrencyNameStringUSD-USA
toCurrencyNameStringUSD-USA
fromCurrencySymbolString$
toCurrencySymbolString$
transactionTypeCodeString100002
transactionTypeNameStringReceived from send client
creationDateString2026-08-31 19:21:54
feeNumber10.0
statusStringSUCCESS
srcPostBalanceNumber-4910.0
srcPreviousBalanceNumber-5000.0
destPreviousBalanceNumber10000.0
destPostBalanceNumber10080.0
transactionAmountNumber100.0
fromWalletTypeCodeString100008
toWalletTypeCodeString100008
debitAmountNumber0.0
creditAmountNumber80.0
postBalanceNumber10080.0
payoutFeeNumber10.0
rateNumber0.0
rateAfterMarginNumber0.0
remarkToClientStringExample client remark
paymentModeStringNA
toRemittanceUserTypeString100000
purposeOfPaymentCodeStringPREP
purposeOfPaymentNameStringPre-Fund
featureCodeString100054
tokenStringTKN1234567
toAmountNumber80.0