Lists every supported processor.
GET
/api/processors
deprecated
Requires: Transactions.ProcessorConfiguration.ViewSchema, merchant scope.
Each entry carries its identifier, display name, and supported payment types.
Signed in, you can send this request to your own sandbox merchant from the console and read the answer. Sign in to try it.
Example request
Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.
The request body is a . See the Request body section below for its fields.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
suppressNulls
required |
query | boolean | If true, omit properties with null values. |
Request body
application/json
, required
| Field | Type | Description |
|---|
This request body has no documented fields.
Responses
200 OK
Body: array of ProcessorSummaryDto
Each item has these 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 |
processorName
required |
string | Display name of the processor. nullable |
supportedPaymentTypes
required |
array of string | 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 |
paymentTypes
required |
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 |
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 |
This response has no documented body fields.
403 Forbidden
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
401 Unauthorized
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
400 Bad Request
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
404 Not Found
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
501 Not Implemented
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
500 Internal Server Error
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
default The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
429 The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.
Body: RemoteServiceErrorResponse
Each item has these fields.
| Field | Type | Description |
|---|---|---|
error
required |
RemoteServiceErrorInfo |
This response has no documented body fields.
Errors
A failed request returns the platform error envelope. The
error reference lists every value
error.code can carry and shows the four response shapes.