# ProcessorProfileCapabilitiesDto

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

The capabilities one of a merchant's boarded processor profiles can actually deliver.

## Fields
- `processorProfileId` (string(uuid)): The processor profile these capabilities describe. Correlates with  `processorProfileId` on the processor-profiles API.
- `processorId` (string): The stable processor key the profile is boarded on (for example `tsys` or  `fiserv`). Echoed exactly as stored on the profile, so it matches the value on the  processor-profiles API. Compare it case-insensitively: the platform resolves the key that way  and the stored casing is not normalized. (nullable)
- `processorName` (string): The processor's display name as stored on the profile. Presentation only: never match on  this, always match on `processorId`. (nullable)
- `supportsZeroDollarVerification` (boolean): Whether this processor supports a zero-dollar account-verification authorization (authorize  $0 with an AVS/CVV check, then void immediately). This is what gates the hosted payment page's  "save my card, do not charge me" flow: when `false`, a save-card-only session  on this processor cannot complete without an amount.
- `supportsReversal` (boolean): Whether the processor accepts a reversal of an authorization that has not settled.
- `reversalWindowSeconds` (integer(int32)): The maximum age, in seconds, an authorization may have and still be reversible, or  `null` when the processor publishes no window. (nullable)
- `supportsVoid` (boolean): Whether the processor accepts a void of a transaction in the open batch.
- `supportsPartialRefund` (boolean): Whether the processor accepts a refund for less than the original settled amount.
- `supportsPartialReversal` (boolean): Whether the processor accepts a reversal that releases only part of the authorization hold.  When `false`, only full-amount reversals are accepted.
- `supportedAdjustmentTypes` ([AdjustmentTypes](https://devportal.demo.winkpg.io/docs/api/models/AdjustmentTypes.md)): The adjustment-shaped follow-up operations the processor advertises (offline adjustment,  incremental authorization, both, or none). 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.
  Values:
  - `None`: Processor advertises no adjustment support. Both OfflineAdjustment and IncrementalAuthorization requests are rejected.
  - `OfflineAdjustment`: Processor accepts TransactionOperationType.OfflineAdjustment: pre-settlement edits to the stored settlement record (tip, tax, level-3, AVS) with no network call. Modeled by OfflineAdjustmentFlowRunner.
  - `IncrementalAuthorization`: Processor accepts TransactionOperationType.IncrementalAuthorization: an online amount-bumping auth on top of the existing approved hold (Visa Estimated/Incremental, MasterCard PreAuth+Final, Discover Incremental). Modeled by IncrementalAuthorizationFlowRunner.
- `softDescriptorNameMaxLength` (integer(int32)): The number of leading characters of the soft descriptor merchant name (the alternate merchant  name sent on a transaction) that the processor prints on the cardholder statement. A longer  name is accepted on the request and truncated by the processor. `null` when  the processor declares no limit. (nullable)

## See also

- [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.