The Card Validation endpoint performs a risk assessment by comparing the card’s BIN metadata (issuer country) against the payer’s billing address and IP geolocation. It returns a risk level along with the full card metadata and the detected countries from each data source. Endpoint:Documentation Index
Fetch the complete documentation index at: https://developers.orchestrasolutions.com/llms.txt
Use this file to discover all available pages before exploring further.
POST /Tools/validate
When to Use This
Use Card Validation as a pre-transaction fraud screening step. By comparing where the card was issued, where the payer claims to be (billing address), and where they actually are (IP geolocation), you can flag suspicious transactions before they reach the PSP. For example, a card issued in Germany being used from an IP address in Nigeria with a billing address in the US would produce a high risk score — an indication that the transaction warrants additional scrutiny or rejection.How It Works
Pass the card’s BIN/IIN as a query parameter and the payer’s billing details in the request body. Query parameter:| Parameter | Type | Required | Description |
|---|---|---|---|
iin | string | Yes | The first 6 to 11 digits of the card number |
| Field | Type | Required | Description |
|---|---|---|---|
clientIPAddress | string | Yes | The payer’s IP address |
countryCode | string | Yes | ISO 3166-2 two-letter country code from billing address |
city | string | No | Billing city |
stateProvince | string | No | Billing state or province |
Risk Levels
| Level | Meaning |
|---|---|
VeryLow | Card issuer country, IP country, and billing country all match |
Low | Minor discrepancy between data points |
High | Significant mismatch between card origin and payer location |
VeryHigh | Multiple mismatches or anonymous proxy detected |
Example: Pre-Transaction Fraud Check
Screen transactions before processing and flag high-risk payments for manual review.Related
Metadata Lookup
Get card metadata without the risk assessment
API Reference
Full endpoint specification and response schema