ProcessorSummaryDto
A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.
Lightweight summary of a supported processor, returned by the processor discovery endpoint. Use the `processorId` to request that processor's full configuration schema.
Values
Fields
| Field | Type | Description |
|---|---|---|
processorId
required |
string | Stable identifier of the processor (e.g. "tsys"). Pass this to the config-schema endpoint and
submit it as the processor configuration's `ProcessorId` on a merchant create/update.
nullable
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.
|
processorName
required |
string | Display name of the processor.
nullable
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.
|
supportedPaymentTypes
required |
array of string array of | Names of the payment types this processor supports (e.g. "Visa", "Mastercard", "EbtSnap").
These can be passed as the payment-types filter when requesting the config schema.
nullable
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.
|
paymentTypes
required |
array of ProcessorPaymentTypeRefDto array of ProcessorPaymentTypeRefDto | The payment types this processor supports, as explicit `{id, name}` pairs. Use this to
populate a profile's payment types deterministically without scraping the GUIDs off a live
merchant document. The ids are global constants (identical across environments); a client may
also submit a payment type by `name` alone and let the
server resolve the id.
nullable
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.
|
Fields of each ProcessorPaymentTypeRefDto: This body has no documented fields. | ||
schemaVersion
required |
string | Opaque, deterministic content hash of this processor's full projected field schema: the same
value returned (and emitted as an ETag) by the config-schema endpoint. Lets a client detect that
a processor's schema changed from a single listing call, without re-fetching every schema.
nullable
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.
|
This model has no documented fields.