FraudReviewDisposition
A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.
Where a transaction held for manual fraud review sits in its disposition lifecycle.
Values
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
Pending |
Held and awaiting a human decision. The state the park step writes. |
Approved |
An operator released the transaction to continue processing. |
Declined |
An operator rejected the transaction. |
ExpiredApproved |
The hold deadline elapsed with no reviewer decision and the merchant's configured expiry action released the transaction to continue processing. Only the parked flow itself can produce this: approving on expiry means going on to authorize the payment. |
ExpiredDeclined |
The hold deadline elapsed with no reviewer decision and the transaction was rejected. Either the merchant configured a decline on expiry, or the backstop sweep reclaimed a hold whose flow did not survive to honor an approval. DispositionReasonCode tells the two apart. |
Fields
| Field | Type | Description |
|---|
This model has no documented fields.