Accounts Creation Prepaid GPR

post

https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/cardholder/accounts

This API is used to create and attach accounts or walletsto an existing card. It is applicable only for the Primary, Supplementary, and Add-on cards of the Prepaid product. A request sent with Card Number Alias (CNA) fetches the associated device for further processing only if the status of device code is Normal. When the request isreceived with form factor as Card Pack ID (CPI) or Card (CRD), it is processed for all devices statuses other than Cancelled or Replaced. A maximum of 15 GPR accounts or wallets can be linked to the card

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
400	GPR100	Invalid Card number alias
400	GPR101	Duplicate CNA found
400	GPR102	Invalid id/card pack id/device/CAN
400	GPRW001	Device not found
400	GPRW005	Wallet plan 1 Field is mandatory.
400	GPRW006	Duplicate wallet plans present in request.
400	GPRW003	Service request allowed only for GPR program.
400	GPRW007	Wallet plan not attached to program.
400	GPRW008	Invalid/Expired promotion plan.
400	GPRW009	Existing wallet plan cannot be used for generating new wallet.
400	GPRW010	Maximum 15 wallets other than Closed status are allowed.
400	GPRW011	New wallet under wallet plan can not be created as same characteristic wallet is already attached.
400	GPRW013	Error Creating GPR Wallet
400	GPRW014	Error while creating device wallet link.
400	GPR104	Device isin Cancelled/Replaced/Upgrade Status
400	MISSING_REQUIRED_FIELD	Missing Required Field identifier or packID or alias or number.
400	INVALID_FIELD_LENGTH	Device Numbersize must be between 15 and 19.
400	INVALID_FIELD_LENGTH	Id size must be between 14 and 36.
400	INVALID_FIELD_LENGTH	Card Pack ID size must be between 10 and 24.
400	INVALID_FIELD_LENGTH	Aliassize must be between 1 and 24.
400	INVALID_FIELD_LENGTH	Program Code size must be between 1 and 10.
400	INVALID_FIELD_LENGTH	Device Plan Code size must be between 1 and 10.
400	INVALID_FIELD_LENGTH	Plan Code Code size must be between 1 and 10.
400	INVALID_FIELD_LENGTH	Promotion Code size must be between 1 and 10.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

dataValidUntilTimestamp

date-time

required

length between 20 and 29

The date and time after which the request is considered as invalid. If the timestamp of the institution is greater than this timestamp, the API request is considered as expired and is returned. The dataValidUntilTimestamp parameter is converted into the institution time zone before comparing it with the institution date and time. It is expressed in ISO 8601 extended format. Must be either: YYYY-MM-DDThh:mm:ss[.sss]Z, or YYYY-MM-DDThh:mm:ss.ssshh:mm where [.sss] is optional and can be 1 to 3 digits.

card

required

accounts

array of objects

required

length ≤ 14

Array of values for an account record. A total number of 14 account plan codes and 14 account promotion codes can be added through this array.

accounts*

Headers

X-MC-Correlation-ID

string

length ≤ 36

API consumer can share unique X-MC-Correlation-ID in HTTP header for each API request. It is recommended to generate UUID (maximum length: 36 alphanumeric characters.) that is compliant with RFC 4122. If it is not shared, then the system generates a unique value for each request.
For example, ac97d177-9345-4934-8343-0f91a7a02836

X-MC-Channel

string

enum

API consumer can share X-MC-Channel in HTTP header for API requests. It isthe network or channel through which request isrouted. The only available value for Channel is API.

Allowed:

X-MC-Source

string

API consumer can share X-MC-Source in HTTP header for API requests. It identifies the request originators application. 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.

X-MC-Client-Application-User-ID

string

length ≤ 50

API consumer can share X-MC-Client-Application-User-ID in HTTP header for API requests. This parameter is a unique identifier to track actual user performing action at the client's end. This field is used only for logging purpose. The maximum length is 50.

X-MC-Idempotency-Key

string

length ≤ 36

API consumer can share X-MC-Idempotency-Key in HTTP headerfor API requests. It is a unique value that is generated by a client and sent to an API along with a request.
If a request fails partway through, the client retries with the same idempotency key value, and the server uses it to look up the state of request and continue from where it left off. During this time, the response of the earlier request will be returned if it is before the threshold time of 15 minutes. After this, the request will be processed as a new request and the response of the new request will be returned.
It is recommended to generate UUID (maximum length: 36) that is compliant with RFC 4122. For example, bc57d177-4593-3449-8343-0d81a7a02947

Response

201Accounts created successfully