# Verify Cardholder

```
POST 
/cardholder/verify
```

Checks a cardholder name against a card and waits for the verdict of the issuer.

Send the card as the `paymentToken` of a payment of your account, or as `card` when your integration is PCI DSS compliant and already sends card numbers to `POST /v1/payments`. Send one of the two, never both. The payment token is not used up: you can pay with it afterwards.

The verdict:

* `MATCH` - The issuer confirmed the name.
* `PARTIAL_MATCH` - Some parts of the name match and others do not, for example the last name matches and the first name does not.
* `NO_MATCH` - The name differs from the name the issuer holds.
* `NOT_AVAILABLE` - No verdict: the card is not Visa or Mastercard, the card network or the issuer cannot check this card now, or the name has characters the network does not take. Not billed.

Each call is one check. A check that got a verdict is billed even when your client stops waiting before the response arrives. Live mode only: an API key of a test account gets `403`. An account can run at most 200 checks in 24 hours; above that the call gets `429`.

## Request[​](#request "Enlace directo al request")

## Responses[​](#responses "Enlace directo al Responses")

* 200
* 400
* 401
* 403
* 429
* 500
* 503

The verdict of the issuer

The request is incorrect or could not be processed

Unauthorized error. Please check your auth credentials

The account cannot run paid checks: test mode, not approved, blocked, not billed weekly, or a partner API key with the `MONEI-Account-ID` header

The account reached its limit of 200 checks in 24 hours

Unexpected server error

The service is temporarily unavailable
