Card Suspension

You can suspend a card by making use of the block card API. When a card is suspended, the user will not be able to make transactions on the card, but a suspended card can be reactivated at any time using the unblock card endpoint.

📘

The block card API offers two sets of endpoints :

  • The block card endpoint can be used to block and unblock both prepaid and debit cards. See its path below:

/card-management/api/v1/card/

  • The prepaid card endpoint also has its own endpoint for blocking and unblocking. See its path below:

/card-management/api/v1/card/prepaid/

Feel free to use any one that suits your use case.

Block A Card

To block a card successfully, make a POST Request to the block card endpoint.

/card-management/api/v1/card/block

These are the parameters of the request:

Query Parameters description

Parameter #Parameter NameData TypeRequiredDescription
1isActiveActivebooleantrueTrue: Select this option when creating a backup for the card.
False: Select this option when you don't want a backup.

Body Parameters

Field #Field nameData typeMax lengthRequiredDescription
1panstring16 to 19trueCard Personal Account Number (PAN)
2holdRspCodestring2 to 2trueHold Response Code.

- 41 for Lost Card
- 43 for Stolen Card
- 45 for Account Closed
- 01 for Refer to Card Issuer.Make use of the applicable code
3seqNrstring3 to 3trueCard Sequence Number
4expiryDatestring4 to 4trueCard Expiry Date
5ridstring1 to 11falseReceiving Institution Identifier

This is what a typical request would look like:

{
  "pan": "5060990000000151002",
  "holdRspCode": "41",
  "seqNr": "001",
  "expiryDate": "5004"
}

Response Message  field description

Field #Field nameDescription
1codeInternal Response Code
2descriptionSuccessful or Error Message
3correlationIdRequest identifier
4errorsErrors array if any errors exist.

This is what a typical successful or failed response would look like

{
  "code": "00",
  "description": "Successful",
  "correlationId": "5daa9a3f6ce9497d84c559aea9f924b3"
}
{
  "code": "400",
  "description": "Unsuccessful",
  "correlationId": "d5c294c81e904a21b3847a5f2b91de44",
  "errors": [
    {
      "message": "File Update error - Card Lookup Failed",
      "fieldName": "27 - P003"
    }
  ]
}

Unblock A Card

To unblock a card successfully make a POST Request to the unblock card endpoint .

/card-management/api/v1/card/unblock

These are the parameters of the request:

Query Parameters description

Parameter #Parameter NameData TypeRequiredDescription
1isActiveActivebooleantruetrue -

false

if the application is configured to restrict non active requests, the value provided by the client may be overridden by the system and set to true

Body Parameters

Field #Field nameData typeMax lengthRequiredDescription
1panstring16 to 19trueCard Personal Account Number (PAN)
2seqNrstring3 to 3trueCard Sequence Number
3expiryDatestring4 to 4trueCard Expiry Date
4ridstring1 to 11falseReceiving Institution Identifier

This is what a typical request would look like:


  "pan": "5060990000000151002",
  "seqNr": "001",
  "expiryDate": "5004"
}

Response Message  field description

Field #Field nameDescription
1codeInternal Response Code
2descriptionSuccessful or Error Message
3correlationIdRequest identifier
4errorsErrors array if any errors exist.

This is what a typical successful or failed response would look like

{
  "code": "00",
  "description": "Successful",
  "correlationId": "5daa9a3f6ce9497d84c559aea9f924b3"
}
{
  "code": "400",
  "description": "[not a valid card number]",
  "errors": [
    {
      "message": "not a valid card number",
      "fieldName": "pan"
    }
  ]
}



Block A Prepaid Card

To block a prepaid card successfully, make a POST Request to the block prepaid card endpoint .

/card-management/api/v1/card/prepaid/block

These are the parameters of the request:

Body Parameters

Field #Field nameData typeMax lengthRequiredDescription
1panstring16 to 19trueCard Personal Account Number (PAN)
2holdRspCodestring2 to 2trueHold Response Code.

- 41 for Lost Card
- 43 for Stolen Card
- 45 for Account Closed
- 01 for Refer to Card Issuer.Make use of the applicable code
3seqNrstring3 to 3trueCard Sequence Number
4expiryDatestring4 to 4trueCard Expiry Date

This is what a typical request would look like:

{
  "pan": "5060990000000151002",
  "holdRspCode": "41",
  "seqNr": "001",
  "expiryDate": "5004"
}

Response Message  field description

Field #Field nameDescription
1codeInternal Response Code
2descriptionSuccessful or Error Message
3correlationIdRequest identifier
4errorsErrors array if any errors exist.

This is what a typical successful or failed response would look like

{
  "code": "00",
  "description": "Successful",
  "correlationId": "5daa9a3f6ce9497d84c559aea9f924b3"
}
{
  "code": "400",
  "description": "[required, length must be 2]",
  "errors": [
    {
      "message": "required",
      "fieldName": "holdRspCode"
    },
    {
      "message": "length must be 2",
      "fieldName": "holdRspCode"
    }
  ]
}

Unblock A Card

To unblock a pre-paid card successfully make a POST Request to the unblock prepaid card endpoint.

/card-management/api/v1/card/prepaid/unblock

These are the parameters of the request:

Body Parameters

Field #Field nameData typeMax lengthRequiredDescription
1panstring16 to 19trueCard Personal Account Number (PAN)
2seqNrstring3 to 3trueCard Sequence Number
3expiryDatestring4 to 4trueCard Expiry Date

This is what a typical request would look like:


  "pan": "5060990000000151002",
  "seqNr": "001",
  "expiryDate": "5004"
}

Response Message  field description

Field #Field nameDescription
1codeInternal Response Code
2descriptionSuccessful or Error Message
3correlationIdRequest identifier
4errorsErrors array if any errors exist.

This is what a typical successful or failed response would look like

{
  "code": "00",
  "description": "Successful",
  "correlationId": "5daa9a3f6ce9497d84c559aea9f924b3"
}
{
  "code": "400",
  "description": "[not a valid card number]",
  "errors": [
    {
      "message": "not a valid card number",
      "fieldName": "pan"
    }
  ]
}