⚡ Zero Auth
Instantly verify a card’s validity and status without blocking funds or impacting credit limits.
Ideal for pre-checks, tokenization flows, and frictionless onboarding.ℹ️ For full request and response examples, refer to the API Reference.
🧭 Overview
Zero Auth is a lightweight, non-monetary pre-authorization flow that validates whether a card is active and legitimate.
It ensures a smooth checkout experience, helps detect invalid or inactive cards early, and boosts approval rates for future transactions.
💡 When to Use
Use Zero Auth whenever card validation is needed before attempting a payment or token creation:
- 💳 During checkout when a user first enters their card details
- 🔐 Before tokenizing or storing a card for recurring payments
- 🛡️ As part of fraud prevention or KYC verification flows
🧾 Request Example
{
"wallet_uuid": "1f937eb2-cf2c-421c-aa24-3f26519f42fa",
"holder_name": "John Doe",
"card_number": "5345625884344596",
"expiry_month": "09",
"expiry_year": "2030",
"cvv": "123",
"brand": "Visa"
}✅ Response Example
{
"internal_uuid": "1f937eb2-cf2c-421c-aa24-3f26519f42fa",
"is_valid": true,
"code": "00"
}💬 Zero Auth — Response Codes & Meanings
| Code | Description (EN) | Description (PT-BR) | Action / Recommendation |
|---|---|---|---|
| 00 | Approved / Valid card | Cartão válido / aprovado | ✅ Card successfully validated; proceed to tokenization or payment. |
| 05 | Do not honor | Não autorizar / não honrar | ⚠️ Issuer declined; may indicate fraud or restriction. Ask the cardholder to contact their bank. |
| 14 | Invalid card number | Número de cartão inválido | ❌ Verify the card number format (Luhn/mod10 check). Request re-entry. |
| 51 | Insufficient funds | Saldo insuficiente | ⚠️ Unusual for Zero Auth (since no funds are held). Possible issuer error; retry later. |
| 54 | Expired card | Cartão expirado | ❌ Request a new card with valid expiry date. |
| 57 | Transaction not permitted | Transação não permitida | ⚠️ Issuer blocked operation; check card configuration or use another card. |
| 58 | Transaction not allowed for terminal | Transação não permitida para o estabelecimento | ⚠️ Verify MCC or merchant configuration. |
| 62 | Restricted card | Cartão restrito | ❌ Declined; card blocked or restricted by issuer. |
| 63 | Security violation | Violação de segurança | ⚠️ Possible CVV or authentication failure. |
| 76 | Invalid data sent | Dados inválidos | ⚠️ Review request fields (expiry, brand, cvv). |
| 79 | Authorization error | Erro de autorização | ⚠️ Temporary error on issuer side; try again later. |
| N7 | CVV2/CVC2 failure | Falha no código de segurança (CVV inválido) | ❌ Ask the cardholder to re-enter CVV; ensure correct length (3–4 digits). |
| 91 | Issuer unavailable | Emissor indisponível | ⚠️ Temporary network issue; retry later. |
| 96 | System malfunction | Erro no sistema / falha geral | ⚠️ Generic error; retry or contact provider if persistent. |
⚙️ How It Works
- 📨 The merchant sends a Zero Auth request with card data.
- 🔍 The API performs a non-financial validation with the payment network.
- 📊 The response returns whether the card is valid, expired, or invalid.
- 🚀 If valid, the merchant continues to tokenization or payment.
🧠 Best Practices
- Always perform Zero Auth before storing card data.
- Log and monitor response codes for better fraud analysis.
- Combine Zero Auth with device and behavioral signals for stronger validation.
Updated 7 days ago
