POST /v1/transactions/verify — Verify Payment Details

Use this endpoint to validate payment method details before you initiate a charge — without triggering a full risk scoring pass. FraudEG checks the payment method against BIN databases, velocity windows, and fraud blacklists, then returns a per-check breakdown so you can gate pre-authorization flows without unnecessary friction for legitimate users.

Endpoint

POST https://api.fraudeg.com/v1/transactions/verify

Request Headers

Header	Value	Required
`Authorization`	`Bearer <API_KEY>`	Yes
`Content-Type`	`application/json`	Yes

Request Body

object

required

The payment method details you want to verify.

Show payment_method fields

string

required

Payment method type. Accepted values: card, bank_account, wallet.

string

Card BIN (first 6–8 digits). Required for card type to run BIN-level checks.

string

Last four digits of the card number. Used for velocity and blacklist matching.

string

Masked bank account number for bank_account type (e.g., "****4321"). Never send the full account number.

string

Bank routing number. Used to verify the institution and check for known fraudulent routing numbers.

string

required

Your internal user ID. FraudEG uses this to run user-level velocity checks against recent payment activity.

integer

Intended transaction amount in the smallest currency unit (e.g., 14900 for $149.00 USD). Providing this value enables amount-aware velocity checks and flags unusual purchase sizes for this user’s history.

string

ISO 4217 currency code for the intended transaction (e.g., "USD", "EUR", "GBP"). Required when amount is provided so FraudEG can apply currency-appropriate thresholds in velocity and amount checks.

Response Fields

string

Unique identifier for this verification record. Store this alongside your pre-authorization record for audit purposes.

string

Overall verification outcome. One of:

valid — All checks passed; the payment method appears legitimate.
suspicious — One or more checks returned a warning; consider step-up verification.
invalid — One or more checks failed; decline or request a different payment method.

array

Ordered list of individual checks performed, with per-check results.

Show check object fields

string

Check identifier. Possible values include bin_check, velocity_check, blacklist_check, routing_check, and account_age_check.

string

Outcome of this individual check. One of pass, warn, or fail.

string

ISO 8601 timestamp of when the verification was performed (e.g., "2024-11-15T10:45:00Z").

Code Examples

curl --request POST \
  --url https://api.fraudeg.com/v1/transactions/verify \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "payment_method": {
      "type": "card",
      "card_bin": "520082",
      "last_four": "1234"
    },
    "user_id": "usr_8f3kd92",
    "amount": 14900,
    "currency": "USD"
  }'

const response = await fetch('https://api.fraudeg.com/v1/transactions/verify', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    payment_method: {
      type: 'card',
      card_bin: '520082',
      last_four: '1234',
    },
    user_id: 'usr_8f3kd92',
    amount: 14900,
    currency: 'USD',
  }),
});

const data = await response.json();
console.log(data);
// {
//   verification_id: 'ver_5pRx2mN8qT',
//   status: 'valid',
//   checks: [
//     { name: 'bin_check', result: 'pass' },
//     { name: 'velocity_check', result: 'pass' },
//     { name: 'blacklist_check', result: 'pass' }
//   ],
//   created_at: '2024-11-15T10:45:00Z'
// }

Example Response

{
  "verification_id": "ver_5pRx2mN8qT",
  "status": "valid",
  "checks": [
    { "name": "bin_check", "result": "pass" },
    { "name": "velocity_check", "result": "pass" },
    { "name": "blacklist_check", "result": "pass" }
  ],
  "created_at": "2024-11-15T10:45:00Z"
}

For high-value transactions, combine this endpoint with POST /v1/transactions/score for layered protection. Run /verify first during payment method collection to catch obviously invalid instruments early, then call /score at the point of purchase to apply the full ML-powered risk model with device and behavioral signals.

Overview

Transactions

Identity

Monitoring

POST /v1/transactions/verify — Verify Payment Details

Endpoint

Request Headers

Request Body

Response Fields

Code Examples

Example Response

​Endpoint

​Request Headers

​Request Body

​Response Fields

​Code Examples

​Example Response

Endpoint

Request Headers

Request Body

Response Fields

Code Examples

Example Response