Inyo

Compliance & Fraud

Payment Card Verification

Know that the card your customer pays with belongs with the identity they just proved. Right after the identity check, the customer photographs their payment card in the same widget. Inyo360 checks that the card is real and carries their name, and can hand you a gateway token for it, so you never build a card form.

Read on the device

The card's details are read from the camera on the customer's own phone. The customer checks them instead of typing them in. How the holder sees it

Redacted before storage

The card number, except its last four digits, and the security code are sanitized and masked out prior to storage. Data handling

Checks on the card and its holder

The card is checked for being a genuine physical card, and its name against the identity document the customer just presented. The checks

Tokenizing without a form

The customer confirms the details read from the card, and the payments gateway tokenizes it. You receive the token. Getting started

Payment card step intro explaining why the card is checked and that the number is masked out except its last four digits, with a Take the photos button

Front of a sample payment card being read live in the capture frame, the fields found so far ticked below it

Spinner with the message Checking your payment card

Turn your card over screen, with an illustrated card turning to show its back

Back of the sample card being read live, with the number, expiry, name and security code ticked as they are found

Spinner with the message Checking your payment card

Check your card details screen: masked card number, name, expiry date and security code all ticked, with Continue and Scan again buttons

Spinner with the message Checking your payment card

All done screen: your details have been submitted

Card scanning
Confirming fields
Card verification
Identity match
Card tokenized
Verified


How It Works

The card step runs inside the hosted identity widget, after the document and selfie steps. It is part of the same session, and its checks arrive in the same result. The diagram shows verification with tokenizing; in verification-only mode there are no tokenize steps (5 to 10) and nothing to capture or void (12), and the result carries the card checks only.

sequenceDiagram
    autonumber
    participant Y as Your System
    participant I as Inyo360
    participant C as Customer
    participant G as Payments Gateway
    Y->>I: POST /v1/sessions<br/>paymentCard.tokenize
    I-->>Y: widgetUrl
    Y->>C: deliver widgetUrl
    C->>I: document, selfie,<br/>card front / back
    Note over C: confirm card details
    C->>G: tokenize card
    G-->>C: token
    C->>I: token
    I-->>Y: PaymentCardTokenized
    Y->>G: POST /v2/payment<br/>capture: false
    G-->>Y: AUTHORIZED
    Note over I: Run card<br/>checks
    I-->>Y: SessionResultUpdated:<br/>checks + decision
    Y->>G: capture or void

The token reaches you in its own webhook the moment it exists, because a gateway token must be used soon after it is created and the session's decision can come much later. Pre-authorize with it right away, then capture or void once the result arrives: read payment_card_token_match first, which confirms the token is for the card the customer photographed. See Card Results.


Two Ways to Integrate

Choose one per session: you add one object to the session request, and both modes run in the same widget and arrive in the same result.

ModeHow it worksChoose this when
VerificationSend "paymentCard": {"capture": true}. The customer photographs the card, front and back. You receive the card rows in checks: the card is in view, readable and genuine, and its name matches the identity document.You want to know the card is real and goes with the person, and you collect payment details your own way.
Verification and tokenizationSend "paymentCard": {"capture": true, "tokenize": {}}. The customer also confirms the details read from the card, and the Payments Gateway tokenizes it. You receive the token in its own webhook, then the same rows and one that checks the token against the photographed card.You charge through the Payments Gateway and want a token without building a card form.

Start with Getting Started.


Next Steps

PageWhat it covers
Getting StartedThe two modes, and the path from session to token
Card SessionsThe paymentCard object on POST /v1/sessions
Widget FlowWhat the customer sees, and the sequence behind it
ResultsThe PaymentCardTokenized webhook, pre-authorizing, and the paymentCard block
ChecksThe card rows in checks
Data HandlingWhat reaches Inyo360, what is kept, and what you never receive
Sandbox & Test DataTesting with a printable specimen card