View your physical card PIN in the Cledara mobile app

A generated PIN is attached to each of your physical Spend card to allow for Chip-and-PIN payments. 

Below is a step-by-step guide to accessing your physical card PIN. 

Feel free to jump to the FAQ section at the bottom if you have specific questions in mind:

  What happens if I enter the wrong PIN when making a payment?
  What happens if I enter the wrong password when viewing my PIN?
  I cannot view my own card PIN. What could be wrong?

To know how to view and card PINs on the Cledara web platform, visit this article.


Step-by-step guide

  1. To view or the PIN on the Cledara mobile app, switch to the Cards screen, and swipe until you see the card you are looking for.

  2. Under the card, click More:

  3. Under Card settings, you will see the options to view your PIN:

  4. To view the PIN, you will first need to enter your Cledara password:

    Screenshot.png

    If you have biometrics activated on your device, it will be used for verification instead of your Cledara password.

  5. Your PIN will only be viewable for 30 seconds. After this time, the screen will automatically close.


FAQ

What happens if I enter the wrong PIN when making a payment?

You have three attempts to enter the correct PIN. After three unsuccessful attempts, your card will be blocked for 24 hours.

If the PIN is entered incorrectly three more times after the 24-hour block, the card will be permanently blocked. To unblock your card, please contact support@cledara.com.

What happens if I enter the wrong password when viewing my PIN?

After 5 consistently failed attempts, you will be temporarily blocked from accessing the PIN for 5 minutes.

I cannot view my own card PIN. What could be wrong?

For security reasons, you cannot view your physical card PIN if the card is disabled. Please make sure your card is active before trying to access your card PIN. 

If your card is disabled by a Spend Admin, it will have to be reactivated by a Spend Admin.

Was this article helpful?
0 out of 0 found this helpful