Skip to main content
Husk uses 3D Secure (3DS) to protect online card payments from fraud. When a merchant triggers 3DS, the cardholder authenticates the transaction in the Husk app before the charge goes through, blocking anyone who has the card number but not the account.

​
When 3D Secure triggers

3DS is required by most European merchants under PSD2’s Strong Customer Authentication rules. You will see it prompt on:
  • New online merchants where the card has not been used before
  • Transactions above a certain amount
  • Any merchant that flags the transaction as higher-risk

​
How cardholders authenticate

1

Merchant redirects to 3DS

At checkout, the merchant sends a 3DS challenge for the card.
2

Husk app receives a push

The cardholder gets a push notification on their phone showing merchant name and amount.
3

Approve or reject

The cardholder taps Approve to confirm the payment or Reject to block it.
4

Merchant completes checkout

On approval, the transaction clears normally. On rejection, the charge is declined and flagged in the dashboard.

​
Set up 3D Secure on a new card

3DS is enabled by default on all Husk cards. When a cardholder receives a new card, they simply need to install the Husk mobile app and enable push notifications.
If a cardholder does not have the Husk app installed or push notifications enabled, 3DS challenges will time out and the transaction will fail. Confirm every team member has the app set up before issuing their first card.

​
Fallback flows

If a push notification is missed, the cardholder can approve the transaction directly from the Husk app’s Notifications tab within a short window before the merchant times out.