Fraud Feedback

For details on how to use this endpoint, see Using the Fraud Feedback API. For general information on Real-Time Decisioning, see Real-Time Decisioning Overview.

Create fraud feedback

Create feedback on whether a transaction was confirmed to be fraudulent or a false positive. Action: POST
Endpoint: /fraud

Body field details (request)

Fields	Description
transaction_token string Required	Unique identifier of the transaction. Allowable Values: Format: UUID
is_fraud boolean Required	Indicates whether the transaction has been determined to be fraud. Allowable Values: `true`, `false`
status string Required	The fraud status. Allowable Values: `CONFIRMED` – Customer confirmed fraud or false positive `DISPUTED` – Dispute is created
actor string Optional	The party making the call. If no value is provided, this field will default to `UNKNOWN`. Allowable Values: `UNKNOWN` – The party is unclear `THIRD_PARTY_FRAUD` – Third-party fraud `CARD_USER_FRAUD` – First-party fraud
amount string Optional	The amount of the transaction that was fraud, for partial fraud claims. If no value is provided, this field will default to the transaction amount from the Marqeta system. Allowable Values: A valid amount.
dispute_status string Optional	The dispute status, if a dispute has been filed. Allowable Values: `NOT_STARTED`, `INITIATED`, `WON`, `LOST`
fraud_type string Optional	The high-level fraud type. Allowable Values: `LOST_CARD` `STOLEN_CARD` `NEVER_RECEIVED_NOT_RECEIVED_AS_ISSUED` `FRAUDULENT_APPLICATION` `COUNTERFEIT_CARD` `ACCOUNT_CREDENTIAL_TAKEOVER` `CARD_NOT_PRESENT_ACCOUNT_NUMBER_FRAUD` `MANIPULATION_OF_CARDHOLDER` `MISCELLANEOUS` `INCORRECT_PROCESSING` `MERCHANT_MISREPRESENTATION` `BUST_OUT_COLLUSIVE_MERCHANT` `MODIFICATION_OF_PAYMENT_ORDER`
reported_datetime string Optional	The date and time the fraud was reported, in UTC. Allowable Values: Format: `YYYY-MM-DDThh:mm:ssZ`
memo string Optional	Any notes related to the case. Allowable Values: 500 char max
metadata object Optional	Additional data written as key/value pairs (for example, `KEY1:VALUE1;KEY2:VALUE2`). Allowable Values: Up to 20 fields.

Sample request body

JSON

{
  "transaction_token": "9xf93ekp-e03a-4fe3-baeb-ppde1e9db665",
  "is_fraud": true,
  "status": "CONFIRMED",
  "actor": "UNKNOWN",
  "amount": 108.95,
  "dispute_status": "INITIATED",
  "fraud_type": "STOLEN_CARD",
  "reported_datetime": "2026-06-01T12:00:00Z",
  "memo": "Cardholder reported card stolen prior to transaction.",
  "metadata": {
    "KEY1": "VALUE1",
    "KEY2": "VALUE2"
  }
}

Feedback response

Returns a response code and message from the feedback request. For a successful request: 201 {"message":"success"}

Fields	Description
message string Returned	The message from the feedback request. Allowable Values: 256 char max

Response errors

Error code	Description
400	Bad request.
401	Unauthorized.
403	Forbidden.
500	Internal server.

Sample response

JSON

201

{
  "message": "success."
}

3D Secure

Disputes (Mastercard)

⌘I

​Create fraud feedback

​Body field details (request)

​Sample request body

​Feedback response

​Response errors

​Sample response