Create a payment gateway configuration

post

/fscmRestApi/resources/11.13.18.05/publicSectorGatewayConfigs

Request

Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
  • Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
Request Body - application/json ()
Root Schema : schema
Type: object
Show Source
  • Title: Configuration Description
    Maximum Length: 300
    The description of the payment gateway configuration.
  • Title: Configuration ID
    Maximum Length: 15
    The unique identifier of the payment gateway configuration.
  • Title: Configuration Name
    Maximum Length: 100
    The name of the payment gateway configuration.
  • Maximum Length: 1
    Default Value: false
    Indicates whether seed data has been deleted. If the value is Y, the seed data has been deleted. The default value is N.
  • Title: Gateway Name
    Maximum Length: 80
    The name of the payment gateway.
  • Title: Gateway Product ID
    Maximum Length: 100
    The unique identifier of the product of the payment processor that is called by the payment gateway.
  • Default Value: 0
    Indicates whether seed data is locked. A value of 0 means it is customer data. A value of 1 means the seed data is locked and cannot be updated. A value of 2 means the seed data can be updated.
Back to Top

Response

Supported Media Types

Default Response

The following table describes the default response for this task.
Headers
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Body ()
Root Schema : publicSectorGatewayConfigs-item-response
Type: object
Show Source
  • Title: Configuration Description
    Maximum Length: 300
    The description of the payment gateway configuration.
  • Title: Configuration ID
    Maximum Length: 15
    The unique identifier of the payment gateway configuration.
  • Title: Configuration Name
    Maximum Length: 100
    The name of the payment gateway configuration.
  • Maximum Length: 1
    Default Value: false
    Indicates whether seed data has been deleted. If the value is Y, the seed data has been deleted. The default value is N.
  • Title: Gateway Name
    Maximum Length: 80
    The name of the payment gateway.
  • Title: Gateway Product ID
    Maximum Length: 100
    The unique identifier of the product of the payment processor that is called by the payment gateway.
  • Links
  • Default Value: 0
    Indicates whether seed data is locked. A value of 0 means it is customer data. A value of 1 means the seed data is locked and cannot be updated. A value of 2 means the seed data can be updated.
Back to Top