BLC Complete Card Replacement - Field Descriptions
The following page details each of the fields received in the response when using the Complete Card Replacement endpoint.
Request Fields
The following table describes fields that can be included in the body of the request when replacing a card.
| Field | Description | Minimum Length | Maximum Length | Mandatory |
|---|---|---|---|---|
| moveBalance | If true then the balance will move to the new card. | 4 | 5 | No |
| moveLimitAccumulators | If true then the limit accumulators will move to the new card. | 4 | 5 | No |
| moveChildCards | If true then the child cards associated with the card will move to the new card. | 4 | 5 | No |
| moveExpiryDate | If true, then move the same expiry date to the new card. | 4 | 5 | No |
| expiryDate | If provided, card is set to the new Expiry Date. Otherwise default from program is used. Should not be set when MoveExpiryDate is true. Format YYYY-MM. | 0 | 7 | No |
| freetext1 | Additional fulfilment data used for transferring extra information to the card manufacturer. | 0 | 50 | No |
| freetext2 | Additional fulfilment data used for transferring extra information to the card manufacturer. | 0 | 50 | No |
Response Fields
A successful response for the BLC Card Replacement endpoint will return a 204 No Content status code. No fields are returned.