Reward Redemption (Merchandise) API

This API is used to redeem reward pointsto purchase a product (merchandise) for requests received through various channelssuch as online banking or mobile banking. The Credit+ Issuing system receives, validates, and processes the request. If the request is successful and adheres to business rules, then number of points coming in the request are redeemed from the account's loyalty point bucket. The system logs the “Reward Redemption (Merchandise)” (Service Code: 512) 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. This API is applicable for prepaid, credit and debit products issued on Pine Labs platform.

NOTE: No monetary amount is credited through this API. This API is applicable for general purpose reloadable programs only in case of prepaid products. Further, the device status should not be blocked, cancelled or upgrade and the unpaid status should be normal (0).

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 CodeError CodeReason
201000Successful.
400119Transaction Not Allowed.
500999Internal Error.
400954Invalid/not matching mobile number/Card number.
400955Customer not billed/NTB customer.
400956Available reward points are not sufficient for redemption.
400956Co-Brand Partner is not Configured/Available.
400957Minimum Redemption Points/Amount criteria not met.
400957Account Unpaid Status is not Normal.
400957Loyalty plan is not configured.
400958Card already blocked/cancelled/upgraded.
400959Merchandise not configured.
400960Redemption allowed for Primary device.
400997Card Type field is mandatory.
400997Points To Be Redeemed field is mandatory.
400997Device Number field is mandatory.
500951Internal Error.
400997Device Number field value must have min length 4.
400997Device Number field value must have max length 24.
400997Card Number field should be numeric.
400997Mobile number field is mandatory.
400LOYT00020Error in fetching Product and Account details.
400LOYT00028Error in fetching data from account.
400LOYT00028Redemption not Allowed. Account is in Unpaid Status.
400LOYT00023Redemption Points entered are less than Minimum Points defined on this plan.
400LOYT00029Total selected points are less than Minimum redemption points on Plan.
400LOYT00024Error in fetching data from CARD_RANGE, Account No.
400LOYT00019Error in fetching details of Account No.
400LOYT00029Error While Getting Redemption Value.
400LOYT00032Error fetching cumulative balance.
400TXN003Error updating balance.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Accessing channel

string
enum
required

Card product type. Valid values: C (Credit), P (Prepaid), D (Debit)

Allowed:
string
required
length between 4 and 24
^[0-9]+$

Complete card number or last 4 digits

string
^[0-9]+$

Registered mobile number on the card. Must be provided if only the last four digits of the card number has been provided in the deviceNumber attribute

string
required
^[0-9]+$

Number of reward points that has to be redeemed

Headers
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.

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

Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json