Statement Request on IVR API (V1)

post

https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/helpdesk/statementlog

This API is used to send statements on requests initiated through IVR to customers. The Credit+ Issuing system receives, validates and processes the request. If the request is successful, system logs the “Statement Request” (Service Code: 300) service request (SR) and sends the service request details in the response message. If the request fails, the system returns the corresponding error code in the response and the SR is not logged. When more than one statement is available for a specific month, then the system will log Service Request for ‘Latest’ statement of a month. If the statement has not been generated for the month requested by the cardholder, then the SR is not logged, and an error message is returned in response.

NOTE: This API would be consumed by users who are presently using version 1 of this API. For users who are consuming version 3 of this API, refer to Section ‘Statement Request on IVR API (V3)’.

HTTP Status and Response Status Matrix

HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
Reason: This is the description of the error code returned by Credit+ Issuing application.

HTTP Code	Error Code	Reason
201	CCRBO0004	Request processed successfully.
400	997	Form Factor Type field is mandatory.
400	997	Invalid Form Factor Type.
400	997	Form Factor field value must have min length 10.
400	997	Form Factor field is mandatory.
400	997	Form Factor field value must have max length 24.
400	997	One of the Dates not provided correctly.
400	997	Statement Period From must be in ddMMyyyy format.
400	997	Statement Period From field is mandatory.
400	997	Statement Period To must be in ddMMyyyy format.
400	997	Statement Mode field is mandatory.
400	997	Invalid Statement Mode.
400	997	Invalid Priority Request.
400	997	At least one transaction channel required.
400	VALFRM003	Invalid Device.
400	VALFRM004	Invalid Device.
400	VALFRM005	Invalid Card Pack Id.
400	VALFRM007	Invalid form factor type.
400	VALFRM015	Statement request not allowed for Debit product.
400	STMREQ011	Preferred address not present.
400	STMREQ010	Email-id not present.
400	STMREQ007	Statement Period To is mandatory for Prepaid device.
400	STMREQ005	Statement Period To not allowed for credit device.
400	STMREQ003	Statement not generated for the given period.
400	STMREQ009	Error while statement log req.
400	STMREQ000	Request Processed Successfully.
201	HDS000	Request processed successfully.
400	HDE192	Statement for specified date range not available.
500	HDE105	Error Occurred as Value not specified for Statement By.
500	HDE107	Error Occurred as Email ID not specified.
500	HDE108	Error in fetching Email ID from Device.
400	HDE109	Error Occurred as Email ID not specified in Device table.
400	HDE110	Error Occurred as Email ID is not matching with Device Email ID.
500	HDE111	Error Occurred while generating statement.
500	HDE112	Error Occurred while generating statement fees.
500	HDE113	Error Occurred while generating statement.
400	994	Invalid Encryption-Algorithm header value.
400	994	Invalid Encryption Request Parameters.
400	994	Cryptography error.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

priorityRequest

string

enum

It denotes whether the request is to be taken on priority or not. Valid values: 0 (No priority), 1 (Priority request)

Allowed:

note

string

length ≤ 4000

Any free text that requestor may want to send for logging purpose

formFactorType

string

enum

required

length ≤ 3

This value identifies the data that is being sent in formFactor. Valid values: CRD (Card Number), ACT (Account Number), CPI (Card Pack ID)

Allowed:

formFactor

string

required

length between 10 and 24

Card Number or Account Number or Card Pack ID depending on the formFactorType value

stmtPeriodFrom

string

required

^(0[1-9]|[12]\d|3[01])(0[1-9]|1[0-2])\d{4}$

The system will retrieve the statement that is generated just after the date provided here. Format: DDMMYYYY

stmtPeriodTo

string

^(0[1-9]|[12]\d|3[01])(0[1-9]|1[0-2])\d{4}$

End date of the time period till which statement is required. Format: DDMMYYYY. Must be present for prepaid product. Must not be sent for credit product

statementMode

string

enum

required

Indicates the statement mode in which it will be delivered. Valid values: H (Hard Copy), E (E-mail), B (Both)

Allowed:

channel

string

length ≤ 10

Accessing channel

Headers

Correlation-ID

string

^[a-zA-Z0-9-]{1,50}$

API Consumer must share Correlation-ID in HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate a universally unique identifier (UUID) of length 32 or 36 that is compliant with RFC 4122. The maximum supported length is 50 alphanumeric characters. For example, ac97d177-9345-4934-8343-0f91a7a02836. If the Correlation-ID is not received in the incoming request, the system generates the UUID dynamically and assigns it to the request.

Source

string

API Consumer can share Source in HTTP header for API requests. For the list of Source values, see the Pre-conditions for HTTP Header of REST API topic in the Pre-requisite for Rest API section.

Response

201Successful statement request