Global Constraints

Required fields must be included for the request to be accepted.

Client behavior expectation: If a field is Required, you should always send it with a valid value.

Imperative fields should be sent whenever your implementation has the ability to provide them.

Imperative does not mean “send it sometimes.” It means:

Imperative fields materially improve fraud evaluation by enhancing correlation and context. They are labeled Imperative because they are high-value signals, but we understand they may not be available across all clients.

Client behavior expectation:

Conditional fields become required only when certain conditions are met—for example, based on the value of another field, or when a related field is present.

Conditional rules are used to express dependencies like:

Client behavior expectation:

Optional fields may be included at your discretion. They are not required for the request to be accepted, and there are no validation dependencies that require them to be present.

Optional fields typically provide additional context or enrichment data that can improve evaluation, reporting, or downstream workflows, but they are not necessary for basic processing.

Client behavior expectation: