Fraud Label Feedback

Labels an identity (IP, email, email domain, phone, card BIN, customer id, device id or text) as fraud or legitimate, or marks a dashboard event as a true or false positive.

Overview#

feedback/event is a POST method with a JSON body. Send either type + value, or the event_id of an event from your dashboard or webhooks, plus label: fraud or legit. Optional reason, source and occurred_at are kept with the label.

When to call it#

• Support confirms that an email, phone, device or customer account belongs to a fraudster, or clears one that was wrongly suspected.
• An alert you received was right (fraud) or wrong (legit): send its event_id. For a payment alert, the label is also applied to that transaction as fraud_confirmed or legit_confirmed.

How it works#

Gurdx stores a keyed hash of the identity and a masked value, never the raw value. A fraud label raises the risk of that identity in later checks: payments reusing it fire rule GX2001 (same customer) or GX2002 (shared device, card or IP), IP checks rate it high risk, and email and phone checks mark it invalid with a reason. A legit label offsets earlier fraud evidence. The evidence halves every 90 days. One label is kept per identity: re-sending it returns unchanged, sending the other label updates it.

If you turn on Auto-blacklist confirmed fraud on the Learning page, fraud labels are also added to a "Confirmed fraud" blacklist.

Notes#

• Free: not counted against your quota, available on every plan.
• Test mode validates and returns a sample result without storing anything.
• An unknown event_id, an invalid value or a missing label returns error 131 (invalid_feedback) with HTTP 200.

Request#

• Authenticate with the key parameter or an Authorization: Bearer header.
• Free — not counted against your quota.
• Available on: Free trial Standard Premium Pay-as-you-go

Parameters#

Every method also accepts format, lang, mode, userID. See Options.

Code samples#

curl -X POST "https://gurdx.cretip.com/api/feedback/event" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "email",
    "value": "buyer@example.com",
    "label": "fraud",
    "reason": "stolen card confirmed by issuer",
    "source": "risk_team"
}'

<?php

$payload = [
    'type' => 'email',
    'value' => 'buyer@example.com',
    'label' => 'fraud',
    'reason' => 'stolen card confirmed by issuer',
    'source' => 'risk_team',
];

$ch = curl_init('https://gurdx.cretip.com/api/feedback/event');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => ['Authorization: Bearer YOUR_API_KEY', 'Content-Type: application/json'],
    CURLOPT_POSTFIELDS => json_encode($payload),
]);
$result = json_decode(curl_exec($ch), true);

if ($result['status'] !== 'success') {
    error_log($result['code'].': '.$result['description']);
}

const res = await fetch('https://gurdx.cretip.com/api/feedback/event', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "type": "email",
    "value": "buyer@example.com",
    "label": "fraud",
    "reason": "stolen card confirmed by issuer",
    "source": "risk_team"
}),
});
const result = await res.json();

if (result.status !== 'success') {
  console.error(result.code, result.description);
}

import requests

res = requests.post(
    "https://gurdx.cretip.com/api/feedback/event",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={
        "type": "email",
        "value": "buyer@example.com",
        "label": "fraud",
        "reason": "stolen card confirmed by issuer",
        "source": "risk_team",
    },
)
result = res.json()

if result["status"] != "success":
    print(result["code"], result["description"])

Response#

Success#

{
    "data": {
        "type": "email",
        "value": "b***@example.com",
        "label": "fraud",
        "status": "created"
    },
    "status": "success",
    "executionTime": 3
}

Error#

Errors are delivered with HTTP 200 — always check the status field.

{
    "status": "error",
    "code": 101,
    "type": "invalid_key",
    "description": "The API Key is missing or invalid."
}

Response fields#