Overview
Card verification allows you to confirm that a card is valid, active, and belongs to the customer without processing an actual charge. This is done through a zero-amount authorization (also called a $0 auth or account verification), where the issuer validates the card details and returns an approval or decline without reserving or capturing any funds.
Use Cases
Use Case Description Card enrollment Verify a card before saving it for future use Subscription signup Confirm card validity before starting a free trial Wallet top-up Validate a card before linking it to a digital wallet Pre-authorization check Ensure a card is active before a high-value transaction Fraud prevention Detect stolen or invalid cards early in the flow
How It Works
Submit a verification request with the card details (or a vaulted token).
Yuno sends a zero-amount authorization to the card issuer.
The issuer validates the card number, expiration, CVV, and account status.
A verification result is returned: VERIFIED or FAILED with a reason code.
No charge appears on the customer’s statement (some issuers may show a temporary $0 hold).
API Example
cURL
Response - Verified
Response - Failed
curl --request POST \
--url https://api.y.uno/v1/card-verifications \
--header 'Content-Type: application/json' \
--header 'X-Api-Key: YOUR_API_KEY' \
--data '{
"payment_method": {
"type": "CARD",
"token": "tok_card_abc123"
},
"country": "BR",
"currency": "BRL",
"customer": {
"email": "customer@example.com"
}
}'
Verification Results
Status Description Next Step VERIFIEDCard is valid and active Safe to save or use for payments FAILEDCard is invalid, expired, or declined Prompt customer for another card
Failure Reasons
Reason Code Description CARD_EXPIREDCard has passed its expiration date CARD_DECLINEDIssuer declined the verification INVALID_CARD_NUMBERCard number fails Luhn check or is not recognized CVV_MISMATCHCVV does not match issuer records INSUFFICIENT_FUNDSNot applicable for $0 auth (rare) LOST_OR_STOLENCard reported as lost or stolen
Some issuers do not support zero-amount authorizations and will decline the request. In these cases, consider using a small-amount authorization (e.g., $1.00) followed by an immediate void. Check with your provider for issuer support.
AVS and CVV Results
Card verification responses include Address Verification System (AVS) and CVV check results when available:
Result Meaning MATCHData matches issuer records NO_MATCHData does not match NOT_CHECKEDIssuer did not perform the check UNAVAILABLEIssuer does not support this check
AVS results require the customer’s billing address to be included in the verification request. Without address data, AVS will return NOT_CHECKED.
Best Practices
Verify before vaulting : Always verify a card before saving it for recurring use.
Handle failures gracefully : Provide clear error messages when verification fails.
Use with 3DS : Combine card verification with 3D Secure for subscription enrollments.
Do not over-verify : Excessive verification requests on the same card may trigger issuer fraud alerts.
Inform customers : Some issuers show a temporary $0 pending charge. Consider informing customers that this is a verification, not a charge.