Realized

Blob VA Statement API
1.0.0

This is the Corporate Account Statement API -Receive an instant overview of transactions on in your account. Know your bank account balance instantly.Get a consolidated view of your account -Account attributes can be fetched in one click (attribute includes a/c name, cust id, cust segment, Primary RM etc.

TestCase : 1

Description:
Valid input with all fields correctly filled (alphanumeric, <= 20 chars)

Input:
TranID=TXN12345,
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 200,
Status = Success,
base64 data returned

TestCase 2

Description:
Missing TranID field

Input:
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Missing required field: TranID

TestCase 3

Description:
Special characters in TranID

Input:
TranID=TXN#123!,
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = TranID must be alphanumeric and up to 20 characters

TestCase 4

Description:
Special characters in Corp_ID

Input:
TranID=TXN12345,
Corp_ID=CORP@123,
account_no=ACC998877,
from_date=2024-01-01, to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Corp_ID must be alphanumeric and up to 20 characters

TestCase 5

Description:
account_no exceeds 20 characters

Input:
TranID=TXN12345,
Corp_ID=CORP123,
account_no=ACC9988771234567890123,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = account_no must be alphanumeric and up to 20 characters

TestCase 6

Description:
Empty JSON body

Input: {}
Expected Output:
HTTP 400,
Error Code = ER002,
Message = Missing FetchAccStmtReq or Header block

TestCase 7

Description:
Invalid JSON format (e.g., malformed JSON)

Input:
{ FetchAccStmtReq: [Header: {...}] }

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Invalid Request Format or Missing Fields

TestCase 8

Description:
All fields are exactly 20-character valid alphanumeric values

Input: TranID=TXN1234567890123456,
Corp_ID=CORP1234567890123,
account_no=ACCNUM12345678901234,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output: 
HTTP 200,
Status = Success,
base64 data returned

Blob VA API
1.0.0

This is the Corporate Account Statement API -Receive an instant overview of transactions on in your account. Know your bank account balance instantly.Get a consolidated view of your account -Account attributes can be fetched in one click (attribute includes a/c name, cust id, cust segment, Primary RM etc.

TestCase : 1

Description:
Valid input with all fields correctly filled (alphanumeric, <= 20 chars)

Input:
TranID=TXN12345,
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 200,
Status = Success,
base64 data returned

TestCase 2

Description:
Missing TranID field

Input:
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Missing required field: TranID

TestCase 3

Description:
Special characters in TranID

Input:
TranID=TXN#123!,
Corp_ID=CORP123,
account_no=ACC998877,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = TranID must be alphanumeric and up to 20 characters

TestCase 4

Description:
Special characters in Corp_ID

Input:
TranID=TXN12345,
Corp_ID=CORP@123,
account_no=ACC998877,
from_date=2024-01-01, to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Corp_ID must be alphanumeric and up to 20 characters

TestCase 5

Description:
account_no exceeds 20 characters

Input:
TranID=TXN12345,
Corp_ID=CORP123,
account_no=ACC9988771234567890123,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output:
HTTP 400,
Error Code = ER002,
Message = account_no must be alphanumeric and up to 20 characters

TestCase 6

Description:
Empty JSON body

Input: {}
Expected Output:
HTTP 400,
Error Code = ER002,
Message = Missing FetchAccStmtReq or Header block

TestCase 7

Description:
Invalid JSON format (e.g., malformed JSON)

Input:
{ FetchAccStmtReq: [Header: {...}] }

Expected Output:
HTTP 400,
Error Code = ER002,
Message = Invalid Request Format or Missing Fields

TestCase 8

Description:
All fields are exactly 20-character valid alphanumeric values

Input: TranID=TXN1234567890123456,
Corp_ID=CORP1234567890123,
account_no=ACCNUM12345678901234,
from_date=2024-01-01,
to_date=2024-01-31

Expected Output: 
HTTP 200,
Status = Success,
base64 data returned

Single Payment with BeneID
1.0.0

Single payment with beneficiary Id API facilitates the client to initiate a payment request to the registered beneficiary ID’s. Single payment Corp Status API facilitates the client to check the status of the payment using either OrgTransactionID, RefNo, UTRNo or RRN for the registered Corpid.

Test Case 1


Description: 
Empty Request Body

Input: 
null or empty request body

Expected Output:
HTTP status: 400
Error Code: ER001
Error Desc: "Invalid Request Format"

Test Case 2

Description: 
Missing Single_Payment_Corp_Req Object

Input:
Request body without Single

Bulk Payment API
1.0.0

A bulk payment API is used for streamlining and automating the process of making multiple payments from a single source to various recipients.

Test Case 1: Valid Request

Description: 
All fields are correctly filled.

Input: 
Valid JSON with Header and Body fields

Expected Output: 
BatchStatus = Accepted, EnquiryBatchID generated.

Test Case 2: Missing Request Body

Description: 
Entire request body is missing.

Input: 
Empty or null body

Expected Output:
ErrorCode: ERR0001
Description: Missing request body
BatchStatus = Failed

Test Case 3: Invalid JSON Format

Bene Registration V2 API
1.0.0

A "bene registration API" is used for registering or adding beneficiaries, often in the context of financial transactions or payments. It allows a merchant or system to add a new recipient to their list of beneficiaries, enabling them to make payments to that recipient.

Test Case 1

Description: 
Valid New Beneficiary Registration

Input:
TranID: "TEST001"
Corp_ID: "INNOVITIPA"
Ben_Acct_No: "50100000000099"
Ben_Name: "John Doe"
Remarks: "Test registration"

Expected Output:
Status: "SUCCESS"
Status_Desc includes:
Ben_Id: "BENEINNOVITIPATEST001"
Ben_Name: "John Doe"
Remarks: "Test

Payee Name Validation API
1.0.0

This API is used to check the beneficiary/payee details of a given account number and IFSC code. Based on the Inputs provided in the request, the API validates the beneficiary details and returns a success or failure response.

Test Case 1: Valid Request Existing Account and IFSC

Description: 
Send a valid request with correct account number and IFSC from the user list.

Input:
TranID: T12345
Corp_ID: C100
Maker_ID: M001
Checker_ID: C001
Approver_ID: A001
accountNumber: "309014984652"
ifscCode: ICIC0000003
beneficiaryName: JOHN DOE
beneficiaryMobileNumber: "9123456789"

Expected

PAN Verification API
1.0.0

This API is an interface that allows you to make an online verification by accessing verification site. As per the PAN status as managed/maintained by NSDL database Request is validated at verification site and you receive result as PAN

Test Case 1

Description: 
Valid PAN and matching details

Input: 
PAN = "AFPPC4215F"
Name = "JOHN SAM"
Father's Name = "ROY"
DOB = "02/06/1985"

Expected Output: 
PanStatus = "E"
CustomerNameFlag = "Y"
FathersNameFlag = "Y"
DOBFlag = "Y"
SeedingFlag = "Y"

Test Case 2

Description: 
Valid PAN but mismatched DOB

Input: 
PAN = "BXPPC1234K"

Corporate Single Payment API
1.0.0

RBL Bank customer can send a payment request Fund transfer (between a/c’s within The RBL Bank), NEFT, RTGS, IMPS or even DD directly from his ERP solution. The API will also check for authorization matrix built, as per MOA Board Resolution, during integration setup.

Test Case 1

Description: 
Missing Content-Type header

Input: 
No Content-Type header

Expected Output: 
415 Unsupported Media Type - Content-Type must be application/json less

Test Case 2

Description: 
Missing Request Body

Input: 
Empty body

Expected Output: 
400 Bad Request - Request Body is missing or