Submit Feedback

Send the final operational or financial outcome to POST /risk-engine/feedback.

Outcomes#

| Outcome | Meaning | | --- | --- | | approved | Legitimate and accepted. | | rejected | Rejected by your business. | | chargeback | Later resulted in a chargeback. | | confirmed_fraud | Confirmed fraudulent. | | false_positive | Flagged but confirmed legitimate. |

Canonical request#

curl -X POST "$VERTEXY_API_BASE_URL/risk-engine/feedback" \
  -H "Authorization: Bearer $VERTEXY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "assessmentId": "c8acf6d5-8bf4-4b80-a7e5-1b33583c1c23",
    "outcome": "false_positive",
    "falsePositive": true,
    "idempotencyKey": "review-resolution:rev_1001",
    "occurredAt": "2026-06-21T10:35:00.000Z",
    "metadata": { "reviewId": "rev_1001" }
  }'

Fields#

• outcome is required.
• Prefer assessmentId; use transactionId only when the assessment ID is unavailable.
• Reuse an idempotencyKey when retrying the same fact.
• occurredAt records when the outcome happened.
• confirmedFraud, chargeback, and falsePositive can reinforce the outcome.
• metadata can hold internal audit context.

Submit manual-review and verification outcomes when known; submit disputes and chargebacks when they arrive later. Keep one canonical feedback event per operational fact. See Retries and Idempotency for failure handling.