Wallet Closure or Refund Request API

A cardholder can do both Refund, Closure functions for the prepaid devicesseparately as well as together. The Credit+ Issuing system will receive the request. Now, the system will process the request and will perform the necessary validations. Once the validations are successful, it sends a Wallet Closure or Refund Request service request. If a validation fails, it sends the corresponding error in the response message. This API can be processed for all prepaid devices statuses configured in the system.

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
401997Either Channel is blank or not valid, Please enter Valid Channel.
400997Request logged successfully and can be approved after locking period, i.e. block release date, locking period for this wallet is days. Request Number NOTE: The locking period day is calculated in the message text field based on the configuration made at the wallet plan.
400997Either Passcode flag is blank or length is not 1.
400997Either Passcode is blank or Length is greater than 200 whereas Passcode flag is Y.
400997Passcode should be blank when Passcode flag is N.
400997Either Form Factor Type is blank or not valid, Please Enter Valid form factor types as per the request.
400997Form Factor field is blank.
400997Card Number in Form Factor field is blank.
400997Card Pack ID in Form Factor field is blank.
400997Form Factor length should be in between 10 to 24.
400997Either Passcode flag is blank or length is not 1.
400997Subsequent Action can be blank but if it present must have values A / D.
400997Either Refund Reference Number is blank or length is not 12 whereas Subs action is A / D.
400997Either Close Device is blank or not valid, Valid Close Device values are Y / N.
400997Either Refund Reason is blank or length is greater than 100.
400997Either Mode of Refund is blank or not valid, Valid Mode of Refund are CA / DD / CH
400997Remarks can be blank but if it is present length must be less than 100.
400997Wallet Detail list should at least have one record if value of subs action is
400997Wallet Number is Mandatory if Device is Multi currency Device or if GPR card close Device value is N.
400997Payout Currency is mandatory if device is multi-currency Device and currency code Length should be equal to 3.
400997Form Factor field is mandatory
400997Form Factor Type field is invalid.
400997Form Factor Type is mandatory
400997Program Code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character.
400997Tolerance Type can be blank but if it present must have values N / P.
404902Invalid Form Factor for provided Institution.
500401User Or Bank do not support API.
400997Device Plan Code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character.
400997Product Type field is invalid.
400997Only alphanumeric characters and underscore are allowed.
400997FORM_FACTOR field value must have max length 24.
400CNA006Multiple device numbers are active for given details
400CNA002Card Number Alias Functionality is not applicable for this Institution
400CNA003Record does not exists for the given details
400CNA001Bank Does Not Exists
500-20004Error: Currency conversion failed for money transfer limit validation.
500-20004Error: VISA/ Mooney transfer limit violated.
500-20004Error: GET_TARGET_WALLET
50020004Error: GET_LIMIT_PLAN_ATTRIBUTES
500REF012Agent wallet not defined.
500REF013Error while fetching Agency wallet details.
500REF079Unapproved load transaction(s) exists. Refund not allowed.
500REF083Unapproved Miscellaneous Debit/ Credit transaction(s) exists. Refund not allowed.
500REF083Wallet Balance has changed, Refund Not Allowed
500REF057Locking period is till LV_BLOCK_RELEASE_DATE Request can be processed only after the locking period.
50061Cumulative balance error/rate not defined
500REF014Lv_Acc_Prog_Cur_Amt= Lv_Acc_Prog_Cur_Amt
500REF055Insufficient balance after considering the refund amount and calculation of minimum balance / retention amount.
500REF018Error Occurred during cancelation of wallet
500REF016Insufficient available balance.
500REF017Insufficient balance after considering the refund amount and calculation of minimum balance / retention amount.
500REF080Refund Amount in refund currency should not be zero.
500REF019Error while processing Refund Transaction
500REF011Error updating balance for agency’s wallet.
500REF011Error updating balance for Corporates wallet.
500-20005Error fetching cumulative balance.
500-20005Client Program Activity Information Not Found. Line
500-20007Error: VALIDATE_DEVICE_LIMITS
50044000Exceeded Maximum number of load for Client.
500-20002Error: GET_LIMIT_PLAN_ATTRIBUTES
500-20003is greater than per transaction amount limit
500REF058ERROR OCURRED WHILE UPDATEING REFUND AMOUNT
500913Backward offset time limit violated.
400994Invalid Request - Unrecognized field.
400988Encryption type Not Supported.
400913Forward offset time limit violated.
400994Invalid Encryption Request Parameters
400994Cryptography error
400994Invalid Encryption-Algorithm header value
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

Free text. Not Null.

string
enum
required

CSC / AGT / Network Code associated to Acquirer ID. Can contain values '31', '32' Only. Not NULL.

Allowed:
string
enum
required
length ≤ 1

Flag to enable the pass code. Should be 'Y' or 'N'. Max length is 1. Not NULL.

Allowed:
string
length ≤ 200

Login Password given to Acquirer ID (it should be hashed with SHA5 algorithm). If PassCodeFlag is 'Y', then this should be Not NULL. Else, this should be NULL. If it is present, max length is 200.

string
enum
required
length ≤ 3

To identify if it is a Card Number (CRD) or Card Pack ID (CPI) or Card Number Alias (CNA). Maximum length: 3. Either CRD or CPI or CNA. Not NULL.

Allowed:
string
required
length between 10 and 24

It is a Card Number or Card Pack ID or Card Number Alias. Maximum length: 24. Minimum length: 10 (minimum length is not applicable for CNA). Not NULL.

string
length ≤ 11
^\d{11}$

Reference Number Identifier. Not Null if Subaction is A OR D, this cannot be blank and length must be equal to 11.

string
enum

Product type of Device. Allowed values (P/C/D). This field is required only when formFactorType is CNA and multiple devices are linked with same CNA.

Allowed:
string
length ≤ 6
^[A-Z0-9][A-Z0-9_]*[A-Z0-9]$

Program attached to the device. Maximum Length: 6. This field is required only when formFactorType is CNA and multiple devices are linked with same CNA.

string
length ≤ 10
^[A-Z0-9][A-Z0-9_]*[A-Z0-9]$

Device Plan Code attached with the device. Maximum Length: 10. This field is required only when formFactorType is CNA and multiple devices are linked with same CNA.

string
enum
required

Indicates closure for device requested. Value can be either of Y or N Only.

Allowed:
string
required
length ≤ 100

Free style text for user reason behind closure. Cannot be blank or more than 100 chars.

string
enum
required

Indicates mode of refund. Valid Mode of Refunds can be 'CA', 'DD', 'CH'.

Allowed:
string

Name & location of merchant.

string
length ≤ 100

Comments on Reason for Refund. If Present Length must be < 100.

string
length ≤ 100

Indicates the additional information related to refund. Maximum length: 100.

string
enum

Any action to be performed after Refund. Values can be A - Approve Action or D - Decline Action.

Allowed:
walletDetailList
array of objects
required
length between 1 and 16

Contains wallet information. Atleast 1 record. Max 16 records.

walletDetailList*
string
required
^\d+$

Current UTC timestamp in milliseconds. AES key expiration criteria depends on input UTC timestamp. Applicable only for encrypted requests. Numeric.

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
enum
required

API Consumer must share Encryption-Algorithm as a key (value: DES168) in HTTP header in order to encrypt the API requests.

Allowed:
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