Why some customers get an extra verification step at checkout

Above a set amount, Turtini asks the customer's bank to verify the cardholder before the payment goes through. Most of the time the customer sees nothing at all — the bank recognises the card and approves it silently. Sometimes they are asked to confirm in their banking app or with a code.

**Why it is worth the extra step**

Card security codes and postal-code checks prove that whoever typed the card details typed them correctly. Somebody using a stolen card passes both without difficulty. Bank verification is different: it asks the bank whether the actual cardholder is present.

When a payment is verified this way and the customer later disputes it as fraud, the card networks make the **bank** responsible for the loss, not you. That is a network rule, not an argument you have to win — the money is not taken back from you at all.

**When it applies**

- Payments of **$100 or more** taken online — tickets, bookings, orders, invoices, donations.
- Not in-person card readers. A physical card tap or chip read cannot do this, and already carries its own protection.
- Not automatic recurring charges. Verification needs the customer to be present, and asking for it on a renewal would simply make the renewal fail.

**Changing the amount.** The $100 threshold can be set higher or lower for your organization if your typical order size makes a different line more sensible. Contact support to change it. Setting it lower protects more payments; setting it higher means fewer customers see a verification step. Turning it off entirely is possible but means every fraudulent chargeback is yours to absorb.