Insights
The Evervault API provides several endpoints which can be used to retrieve additional information for cards and bin ranges. This can be used for tasks such as fraud detection and payment routing.
- The Inspect endpoint allows you to retrieve metadata for an encrypted card number.
- The BIN Lookup endpoint allows you to retrieve metadata for a BIN range.
- The CardInsights endpoint allows you to perform cardholder verification checks and enrichment.
Inspect
The Inspect endpoint allows you to retrieve metadata for an encrypted card. This can be used to retrieve information such as the card brand, the last four digits, and more.
To retrieve metadata for an encrypted card, send the encrypted card number to the Inspect API endpoint. The API key and app ID are required to authenticate the request, and the API key needs the api:inspect permission.
The API will respond with an object containing details about the encrypted data as well as the card metadata inside of the metadata field.
BIN Lookup
The BIN Lookup API allows you to retrieve BIN data for a card number or BIN range. You can pass a plaintext card number, an encrypted card number, or the first 6-10 digits of a card number. If the number matches a range of BINs, the response returns metadata that is common to all the BINs in that range. The API key and app ID are required to authenticate the request, and the API key needs the binLookup:create permission.
The response includes the BIN metadata, such as the card brand, the funding type, the country, and other relevant details.
BIN Lookup vs Inspect
| Metadata | Description | Inspect | BIN Lookup |
|---|---|---|---|
| Fingerprint | A unique identifier for the encrypted card. This can be used to detect card reuse. | ||
| BIN | The first 6 or 8 digits of the card number. | ||
| Last 4 | The last 4 digits of the card number. | ||
| Brand | The card brand, such as Visa or Mastercard. | ||
| Funding | The card funding type specifies the method by which transactions are financed (e.g. debit, credit). | ||
| Segment | The card segment indicates the primary market or usage category of the card (e.g. consumer, etc.). | ||
| Country | The country where the card was issued. | ||
| Currency | The currency of the card. | ||
| Issuer | The name of the card issuer. | ||
| Product Name | The name of the card product. | ||
| Fast Funds | Indicates whether the card supports fast funds (e.g. domestic, cross-border). | ||
| Three DS | Details on supported 3D Secure versions and ACS indicators for the card range. |
Card Insights
Beta
The Card Insights API is currently in Beta for Enterprise customers. Please contact us at support@evervault.com for more information.
The Card Insights API provides a powerful, real-time interface for card and cardholder verification checks and enrichment. It allows you to run address verification (AVS), cardholder name verification (ANI), and CVV validation. You can also retrieve BIN information, interchange and network fee estimates, and the push and pull transaction capabilities for disbursements and collections. By unifying these inputs, the API provides real-time assessments of card and cardholder authenticity alongside rich card metadata—enabling precise validation and smarter routing, handling, and fraud prevention.
Creating a card insight
Card Insights is extensible - you choose the insights you need per request. Every response includes BIN data by default. You can add any of the following extensions:
- Address Verification (AVS) – Run AVS to verify postal code and street-level elements (line1, line2, city, state, country) against issuer records.
- Name Verification – Run ANI to verify the provided first and last name against issuer records.
- Fees – Receive estimated network and interchange fees for specified transaction types to support transparent pricing and optimisation.
- Transaction Capabilities – Determine push and pull transaction eligibility, network, regulatory status, and expected funds-availability windows.
- CVV Validation – Validate the CVV against issuer records.
This example requests all possible extensions and includes both required and optional fields. The example response includes all possible fields.
Extensions & Required fields
| Extension | Required Fields |
|---|---|
capabilities | card.number |
fees |
|
address | card.number, card.expiry, address.postalCode |
cardholder |
|
cvv | card.number, card.expiry, card.cvv |