Home Services Card validation

Card validation

Verify a payment card, confirm the customer’s billing address, run fraud checks and optionally take a fractional authorisation the customer can recognise later - powered by ePayment card services on the eValidate platform.

Contact sales Pricing API docs

What you get

Card validation goes beyond checking digit formats. Use issuer networks and acquirer-side signals (via ePayment) to prove the card is real, the billing address matches, and the customer is a lower fraud risk - without taking a full goods payment up front.

  • Card validity & scheme / issuer signals (Visa, Mastercard and more)
  • Address Verification Service (AVS) against the customer billing address
  • Fraud screening signals on the customer and payment instrument
  • Optional fractional (micro) authorisation the user can verify later
  • Same prepaid £ balance as every other eValidate product
Example endpoint
POST /v1/card/validate
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "pan_token": "tok_…",
  "expiry_month": 12,
  "expiry_year": 2028,
  "billing_address": {
    "line1": "10 Downing Street",
    "postcode": "SW1A 2AA",
    "country": "GB"
  },
  "options": {
    "avs": true,
    "fraud_check": true,
    "fractional_auth": { "amount_pence": 1 }
  }
}
Capabilities

Four checks in one card service

Compose what you need per request - validate only, or full AVS + fraud + micro-auth

Card verification

Confirm the card is structurally valid, not expired, and accepted by the scheme - before you take a material payment or open an account.

Address validation (AVS)

Match the customer’s stated billing address and postcode to the card issuer’s records - a strong signal that the person owns the card and lives where they claim.

Fraud checks

Screen the instrument and customer context for elevated risk (velocity, anomalous patterns, issuer decline codes) so high-risk onboarding can be stepped up or blocked.

Fractional payment

Authorise a tiny amount (for example 1p–£1) the customer can see on their statement later. Ideal for account setup, mandate confirmation or proving card possession without a full charge.

How it works

Validate first - charge later if needed

1. Capture card securely

Collect card details via PCI-aware fields or a tokenised host page so raw PANs never need to touch your servers.

2. Run validation stack

API returns card validity, AVS match codes, fraud score / flags and optional fractional auth result in one response.

3. Customer verifies later

Ask the user to confirm the micro-amount on their statement (or app notification) to complete strong card possession proof.

4. Proceed with confidence

Open the account, ship goods or take the real payment only when card, address and fraud signals look clean.

Use cases

Where card validation fits

Account opening

Prove a real card and matching home address before granting credit, marketplace access or subscription trials.

Address confidence

AVS complements postcode lookup - the issuer confirms the billing address, not only that the postcode exists.

Fraud reduction

Block stolen cards and mismatched addresses early - before payouts, refunds or fulfilment create loss.

With bank & identity

Stack with bank validation, identity and OTP for a full onboarding pack under one eValidate £ balance.

Sister brand

Powered by ePayment card services

eValidate exposes card validation for onboarding and risk. Full merchant acquiring and gateway processing remain available on ePayment Services.

On eValidate

  • Card validity, AVS, fraud signals
  • Fractional authorisations for possession proof
  • Shared £ top-ups with other validation APIs
  • Enterprise SLA & arrears billing options

On ePayment

Add card validation to your stack

Speak to sales about volumes, fractional auth amounts, PCI scope and combining card checks with address, bank and identity APIs.

Contact sales Model on pricing Portal