Card Not Present Verification

Validate that the person completing a card-not-present transaction is the legitimate credit card holder, combining facial biometrics with card ownership validation.

What this use case solves

In card-not-present (CNP) transactions — e-commerce checkout, phone or WhatsApp orders — there is no physical card or chip to confirm who is actually completing the purchase. This solution validates, from the credit card number and the cardholder's CPF, that the person finishing the transaction is the legitimate card holder, using facial biometrics or device metadata authentication. Validated transactions carry a chargeback liability guarantee: if a transaction validated by this solution results in an official chargeback due to a validation error, the customer may be reimbursed by Unico.

Use this use case when:

• Your checkout needs to prevent card-not-present fraud at the top of the funnel, without adding heavy friction to legitimate buyers.
• Your anti-fraud system denies transactions you want to recover — via a manual analysis desk or a WhatsApp-based flow — instead of losing the sale outright.
• You want to onboard a customer's credit card into a digital wallet with verified card-holder identity, reusing biometrics already captured in another identity verification process.

Do not use this use case when:

• The transaction is card-present (in-person, chip or contactless) — this solution is specific to remote, card-not-present scenarios.
• You only need to verify a person's identity, with no credit card involved — use a standard onboarding or authentication use case instead.

Capabilities involved

This use case is powered by Card Not Present Verification, a dedicated product for payment transaction and credit card validation — it is not composed from the identity verification capability pipeline described above, since it runs on its own REST API and authentication.

Card Not Present Verification offers two core building blocks:

• Payment transactions — validates a specific transaction made at checkout, ensuring it can be processed for that user.
• Credit Card Onboarding — registers a user's credit card into a digital wallet with holder verification, optionally reusing biometrics captured by another IDCloud product.

Prerequisites

• Service account and OAuth2 access token — see Authentication.
• Sandbox (UAT) credentials — see the Base URL notes in API Reference.

Step-by-step implementation

Card Not Present Verification's integration flow covers authentication, transaction creation, controlling the capture experience (Webview, SDK, or Redirect), and checking the result via webhook or polling.

Card Not Present Verification Integration Overview

Step-by-step flow: authenticate, customize the experience, create a transaction, and handle the webhook notification.

View overview

What's next

• Explore the full Card Not Present Verification documentation — product details, use cases, and API reference. See Card Not Present Verification.
• Set up webhooks — receive result notifications asynchronously instead of polling. See Webhook.