Card status

Card status refers to the current state or condition of a payment card. It indicates whether the card is active, inactive, blocked, expired, or in any other specific state.

Card status is crucial as it determines whether the card can be used for transactions, and can provide information about the card's eligibility for specific features or benefits.

🗒️

Card status is also referred to as Status Network or status_nwk.

Card status mapping

The following table lists all available card status, their description, and how these card status may impact a transaction response message.

  • Where a client takes the final approve/decline decision, the Processor_Decision_Code is the suggested response code the client will receive in the FAST request message.
  • Where Paymentology takes the final approve/decline decision, the Processor_Decision_Code is used to respond to the network.

You can find the Processor_Reason_Code descriptions here.

Card status

Status_nwk

Description

Decision code

Processor_Decision_Code

Reason code

Processor_Reason_Code

*

Mada response code

1000

Fully operational

Status is valid and will proceed to the next steps.

0

1001

Refer to Issuer

01 or 05

401

107

1004

Capture card

04

402

200

1005

Decline all transactions

05

400

100

1006

Inactive - PIN blocked

57 or 75

412

106

1007

Inactive card - formal decline

12

414

N/A

1008

Honour with ID

08 or 96

404

943

1009

Void card - formal decline

46 (Visa)
62 (Mastercard)

415

N/A

1034

Dynamic block by rule engine (PayRule)

Determined by the rule action that triggered the block.

Determined by the rule action that triggered the block.

1041

Lost card - capture

41

405

208

1043

Stolen card - capture

43

406

209

1054

Expired card - report

54

407

101

1062

Restricted card

62

104

104

1140

Lost card - no capture

05

408

100

1143

Stolen card - no capture

05

409

100

1154

Expired card - don't inform

05

410

100

1199

Void card - once card status is set to void it can notchange. It means the card is completely closed.

05

411

100

*Column only applicable to clients using Mada network.

Changing or updating a card status

Card status can be changed via the Set card status endpoint.

When using the Set Card Status endpoint, you can change the card status to any of the following:

Card status

Status_nwk

Description

1000

Fully operational

1001

Refer to Issuer

1004

Capture card

1005

Decline all transactions

1006

Inactive - PIN blocked

1007

Inactive card - formal decline

1008

Honour with ID

1009

Void card - formal decline

1041

Lost card - capture

1043

Stolen card - capture

1054

Expired card - report

1062

Restricted card

1154

Expired card - don't inform

1199

Void card - once card status is set to void it can notchange. It means the card is completely closed.

There are also certain conditions when a card status changes and transactions are blocked.

  1. When PIN attempts has successively failed three times the card status is set to 1006.
  2. When PIN verrification has successively failed four times via API the card status is set to 1006.
  3. PIN unblock.

In such cases, you can subscribe to receive Card Status Update (CSU) notifications indicating the reason for the card status change.

🗒️

You can read more about CSU notifications here.

Updating linked tokens

When the Set Card Status endpoint is used to change the card status, Banking.Live will automatically update the linked digital tokens.

  • If status_nwk = 1000 then all linked digital tokens will be unsuspended.
  • If status_nwk = 1199 then all linked tokens will be deleted.
  • If status_nwk is changed to anything other than 1000 or 1199 then all linked digital tokens will be suspended.
🗒️

IMPORTANT

Automatically updating linked digital tokens is only applicable to clients using Paymentology tokenization services.

Dynamic blocking

Cards can be dynamically blocked, this allows cards to be blocked for a period of time. Upon expiry of the dynamic block, the card will revert to Card Status: 1000 Fully Operational.

You can check if a card has a dynamic block via the Get card status endpoint. When a card has a dynamic block the response message will include the expiry date of the block in the dynamic_block response field.

If there is no dynamic block for the card, or the previous dynamic block has expired, the response message returns an empty value in the dynamic_blockfield.

Removing an existing dynamic block:

Where you want to remove an existing dynamic block, use the Set card status endpoint and set the status_nwk field to 1000 Fully Operational.

Card status API endpoints

  • Set card status: Used to change the status of a card. This version (version 2) supports idempotency and allows cardholders to continue transacting with their digital wallet (i.e. Apple Pay) whilst their card is suspended.
  • Get card status: Used to retrieve the current card status.
  • Unblock PIN: Used to unblock a PIN, where the PIN is blocked due to 3x failed PIN attempts.
  • Verify PIN: Used to verify the PIN of the card.