Transaction PIN

A transaction PIN is a four-digit numeric code that confirms sensitive money and card actions. It belongs to the active organization rather than to you, so every member acting in that organization confirms with the same PIN, and one organization having a PIN says nothing about another.

The PIN is separate from your login password and separate from the PIN you set on a card.

Set the organization's PIN

The Dashboard shows a "Set up your transaction PIN" prompt when two conditions hold at once:

1. The organization's verification is either submitted for review or already approved.
2. No PIN has been set for that organization yet.

If you do not see the prompt, one of those two is false. An organization still drafting its verification cannot set a PIN yet, and an organization that already has one has nothing to set. See Organization Verification for moving verification forward.

Select Set up PIN, enter four digits, then re-enter the same four digits on the second step. Entering a code that is not four digits shows "OTP must be 4 digits", and a mismatch on the second step shows "PINs do not match" without saving anything. The digits are masked as you type.

Setting or changing a PIN needs the organization.security.manage permission. Owners and admins hold every permission; a member holds it only through a custom role that includes it. See Team Access.

Confirm an action with the PIN

When a sensitive action needs confirmation, Seev asks for a single four-digit entry and verifies it before continuing. These actions ask for it:

• Wallet withdrawals and transfers, including mobile-money withdrawals
• Yield deposits and withdrawals
• Locking, unlocking, and cancelling a card
• Revealing a card's protected details

Enter the PIN belonging to the organization currently shown in the sidebar. If you recently switched organizations, the previous organization's PIN will not verify, and the failure looks the same as a wrong PIN.

Avoid repeated guesses. A rejected PIN leaves the underlying action untouched, so nothing has moved and there is no partial transfer to unwind.

Change the PIN

Changing the PIN asks for the current PIN, a new four-digit PIN, and a confirmation of the new one. All three must be present, and the two new entries must match. Use the new PIN for that organization from then on.

This also needs the organization.security.manage permission, so a member without it can confirm actions with the existing PIN but cannot change it.

If the PIN is rejected

Work through these in order.

1. Confirm the active organization in the sidebar selector.
2. Confirm you are entering the transaction PIN rather than a card PIN or your login password.
3. Check whether a teammate with organization.security.manage changed it recently.
4. Stop guessing after a couple of attempts.

If nobody knows the current PIN, contact support. You verify your identity against the organization, support resets the PIN to a placeholder, and you then change it to a PIN of your own from the dashboard. There is no self-service reset.

Creating another organization does not recover access to the original organization's funds, and the new organization starts with no PIN, no balances, and no verification.

Keep the PIN safe

• Do not use 0000, 1111, a birth year, or another guessable sequence. Nothing in the transaction PIN flow rejects a weak code for you, unlike the card PIN flow, so the choice is entirely yours.
• Do not put the PIN in chat, email, screenshots, or team documentation.
• Give teammates their own membership and role rather than passing the PIN around as a shared credential.
• No Seev employee will ask you to send the PIN.

Related guides

• Accounts and Wallets
• Cards
• Yield
• Team Access