Wallet Creation and Wallet Priority

post

https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/wallet/create/changepriority

A Cardholder sends a wallet creation or wallet priority request to the Credit+ Issuing system. 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, the Cardholder will receive the wallet created message. If a validation fails, it sends the corresponding error in the response message. This API is also used to change the priority request for existing wallet as part of Multicurrency Programs and multi-purpose GPR wallets. This API worksfor Primary and Add-on cards.
NOTE: The API, if sent with Card Number Alias (CNA), will fetch the corresponding associated device for further processing only if DEVICE _STATUS_CODE = NORMAL (0) OR (DEVICE_STATUS_CODE = UPGRADE (9) AND UPGRADE_STATUS = 1).

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	HDS000	Request processed successfully
400	994	Request Parameters Validation Failure: invalid request
400	997	Request Parameters Validation Failure: invalid request
401	990	Unauthorized access
401	991	Unauthorized access
404	998	Device(s) does not exist
404	902	Invalid Form Factor/Form Factor Type for provided Institution.
500	993	Request processing error
500	989	Request processing error
500	992	Request processing error
401	990	Either Channel is blank or not valid, Please enter Valid Channel.
400	997	Either Passcode flag is blank or length is not 1.
400	997	Either Passcode is blank or Length is greater than 200 whereas Passcode flag is Y.
400	997	Passcode should be blank when Passcode flag is N.
400	997	Either Form Factor Type is blank or not valid, Please Enter Valid form factor types as per the request.
400	997	Form Factor field is blank.
400	997	Card Numberin Form Factor field is blank.
400	997	Mobile Reference Numberin Form Factor field is blank.
400	997	Card Pack ID in Form Factor field is blank.
400	997	Form Factor length should be in between 10 to 24.
400	997	Wallet information listshould at least have one record.
400	997	Either Transaction Flag is blank or not valid, Valid Transaction Flags are A / C.
400	997	Either Wallet Currency OR Priority is blank or currency code Length is not equal to 3 whereas txn flag is A
400	997	Either Change Wallet Currency OR Priority is blank or currency code Length is not equal to 3.
400	API522	Invalid Network Code OR not Exists in interface
400	API523	Invalid Network Code OR not Exists in interface
400	433	User does not have permission to access this service. Please contact System Administrator.
400	8	Invalid Session Key
400	19	Session Key can not be null
400	VALPAS002	Not valid Acquirer id
400	VALPAS003	Acquirer is not active
400	VALPAS004	Incorrect Password
400	VALFRM007	Invalid CPI
400	VALFRM007	Card not active
400	VALFRM018	Card not active
400	VALFRM003	Invalid Card
400	173	Invalid form factor type (CARD/CPI)
400	382	Invalid Program Code
400	387	In Program there is no limit define for wallet creation
400	482	Invalid Wallet Plan Code
400	585	default wallet is not active
400	496	Active wallet currency limit exceeded
400	495	No. of wallets permitted has exceeded.
400	VALREQ013	Wallet closed for currency code:
400	485	Device against wallet Priority not defined
400	VALREQ002	New Currency or Wallet Priority should be mandatory
400	VALREQ050	Priority value should be within the number of currencies allowed for the program
400	CURRINST001	Currency not defined or inactive for the institution
400	VALREQ005	Wallet Priority Already Exists
400	VALCURR001	Wallet Currency Already Exists
400	WALINS001	Error, insert records into wallet
400	WALDEV001	Error, recordsinsert into device wallet link
400	ALR001	Error, insert records for Alert
400	ALR002	Error, Insert records for Alert
400	VALREQ003	Error, Currency code and Priority should be mandatory fields
400	VALDCUR04	Wallet not defined to device for requested currency 2.
400	VALDCUR004	Wallet not defined to device for requested currency 2.
400	VALDCUR05	Wallet not defined to device for requested currency 1
400	VALDCUR005	Wallet not defined to device for requested currency 1.
400	CUR1PRT005	currency 1 priority does not exists.
400	CUR2PRT006	currency 2 prority does not exists.
400	SWAPCURR002	Errorswapping Currency priority2
400	VALPRIOR001	Currency2 priority does not matched with currency1 priority
400	VALCURR003	Currency and priority does not match in wallet.
400	VALREQ004	Wallet Request Flag (TXNFLAG) should be mandatory
400	INT001	New Wallet Prepaid creation is failed due to internal error. Please contact system admin.
400	997	Program code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character.
400	997	Program Code field value must have max length 6.
400	997	Device Plan code field should only contain [A-Z 0-9] and underscore and must start and end with alphanumeric character.
400	997	Device Plan Code field value must have max length 10.
400	997	Only alphanumeric characters and underscore are allowed.
400	997	Card Number Alias field value must have max length 24.
400	CNA001	Bank Does Not Exists
400	CNA002	Card Number Alias Functionality is not applicable for this Institution
400	CNA003	Record does not exists for the given details
400	CNA005	Multiple device numbers are active for given details

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

userId

string

length between 6 and 30

Acquirer ID assigned to the third party system. Processing bin in network membership. Not NULL. Minimum length: 6. Maximum length: 30.

sessionKey

string

length ≤ 50

Validation to check if the session is active and bank code must be derived from it. If incorrect or not active, reject the transaction. Not NULL. Maximum length: 50.

channel

string

required

length ≤ 2

^[0-9]{2}$

For API channel is 31/32 CSC / AGT / Network Code associated to Acquirer ID. Fix length 2. Numeric only.

passCodeFlag

string

enum

required

length ≤ 1

Flag used to enable the pass code. Must be Y or N. Not NULL. Maximum length: 1.

Allowed:

passCode

string

length ≤ 200

Login Password given to Acquirer ID. Should be hashed with SHA5 algorithm. If Pass Code Flag is Y, this should be Not NULL; else, this should be NULL. Maximum length: 200.

formFactorType

string

enum

required

length ≤ 3

Identifies whether the formFactor value is a card number, card number alias, or card pack ID. Must be CRD (Card Number), CNA (Card Number Alias), or CPI (Card Pack ID). Not NULL. Maximum length: 3.

Allowed:

formFactor

string

required

length between 10 and 24

^[a-zA-Z0-9!()*+,-.]{10,24}$

Value depends on formFactorType: CRD (card number), CNA (card number alias), or CPI (card pack ID). Not NULL. Minimum length: 10 (not applicable for Card Number Alias). Maximum length: 24. Alphanumeric and special characters [_!'()*+,-.] allowed for CNA.

productType

string

enum

Product type of Device. Must be P (Pre-paid). Required only when formFactorType is CNA and multiple devices are linked with same CNA.

Allowed:

programCode

string

length ≤ 6

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

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

devicePlanCode

string

length ≤ 10

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

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

walletinfoList

array of objects

required

length ≥ 1

List of wallet information for creation or priority change.

walletinfoList*

Headers

Correlation-ID

string

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

API Consumer must share a Correlation-ID in the HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate 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 the 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

201Wallet created or priority changed successfully