Card Security Block

In certain scenarios, a card may be automatically blocked by the system. This block is a security measure to prevent fraud attempts or misuse. When this happens, the platform sends a webhook through the issuing-card/log entity, informing the change in the card's status. It's important for your company to monitor these events to ensure a good user experience and act quickly when necessary.

When the card is blocked, you will receive a webhook with the following characteristics:

• status: blocked
• type: status (indicates a status change)
• reason: Generally empty, but the main reasons are:
  • Manual block requested by you.
  • Automatic block after 4 or more failed attempts by the user, with errors such as:
    • invalidPin
    • invalidExpiration
    • invalidSecurityCode
    • invalidPaymentMethod

The automatic block is activated as a security measure against potential fraud.

---

How to Monitor Card Status

There are two ways to track a card's status:

1. Query the card directly:

   GET /v2/issuing-card/:id

2. Query the card logs:

   GET /v2/issuing-card/logs?cardIds=<id>

---

Reinstating a Card

3. If the issue causing the block has been resolved and the card needs to be reactivated, simply send:

   PATCH /v2/issuing-card/:id

   JSON

    

   {
     "status": "active"
   }