Get Payment Driver Configuration
post
/config/sim/v1/setup/getpaymentdriverconfiguration
Gets the configuration of all the payment drivers.
Request
Supported Media Types
- application/json
- multipart/form-data
A request body
Root Schema : PaymentDriverConfigGetRequestBody
Type:
objectThe input Body model that needs to be given.
Show Source
-
include:
string
Objects included in responseExample:
locations -
includeAll:
string
This can take 2 values: basic or detailed. If 'basic' is specified, The response contains all the properties of the object except
Ext values. If 'detailed' is specified, The response contains all the properties of the object. Example:detailed -
languages:
string
If specified, limits translated strings returnedExample:
en-US, de-DE, es-MX -
limit:
integer
If using paging, number of results returned in this page.Example:
10 -
offset:
integer
Starting resource record indexExample:
0 -
orderBy:
string
Sorts the response by the specified field name and sort orderExample:
objectNum:asc -
searchCriteria:
string
Search criteria to filter results based on field valueExample:
where equals(active,1)
Response
Supported Media Types
- application/json
200 Response
A collection of all Payment Drivers with configurations for an organization.
Root Schema : PaymentDriverConfig
Type:
objectModel for a Payment Driver Configuration Object.
Show Source
-
configuration(required):
object configuration
An object containing the configuration parameters for the payment driver.
-
hierUnitId(required):
integer
Unique reference of the hierarchy unit.Example:
1034 -
hierUnitName(required):
object hierUnitName
Additional Properties Allowed: additionalPropertiesA group of string objects representing the name of the hierarchy unit configured languages.
-
hierUnitObjNum(required):
integer
Object number of the hierarchy unit.Example:
3 -
name(required):
object name
Additional Properties Allowed: additionalPropertiesA group of string objects representing the name of the Payment Driver in configured languages.
-
objectNum(required):
integer
Object number of the Payment Driver.Example:
20
Nested Schema : configuration
Type:
objectAn object containing the configuration parameters for the payment driver.
Show Source
-
assemblyName:
string
Name of the assembly containing the module
-
categoryAndType:
string
Category and type of the driver to be initiated
-
className:
string
Class name of the module to be initiated
-
clientCertCommonName:
string
Displays client certificate common name, if loaded
-
clientCertEffectiveDt:
string
Displays client certificate effective date, if loaded
-
clientCertExpDt:
string
Displays client certificate expiration date, if loaded
-
clientCertificate:
string
Client certificate public key
-
clientCertPassword:
string
Client certificate password
-
currencyCode:
string
Enter the 3 digit ISO Numeric Currency Code. (SPI Only)
-
description:
string
A description for this module
-
enableQuickChip:
boolean
Select True to enable the Quick Chip feature with fast transactions. The payment Service provider should support this feature.(SPI only)
-
hostTimeout:
integer
Timeout in seconds before the request is abandoned.
-
includeNamespaceWithXMLMessage:
boolean
Include NameSpace elements in XML message.(SPI only)
-
merchantNumber:
string
Enter the merchant identification number.
-
passphrase:
string
Enter the authentication pass phrase.(OPI only)
-
primaryHost:
string
Enter the URL for the endpoint.(format- http(s)://host:port number)
-
securitySettings:
integer
Http Only; Https without certificate validation; Https with certificate validation(Server certificate required, Client certificate optional)(SPI only)
-
serverCertCommonName:
string
Displays server certificate common name, if loaded
-
serverCertEffectiveDt:
string
Displays server certificate effective date, if loaded
-
serverCertExpDt:
string
Displays server certificate expiration date, if loaded
-
serverCertificate:
string
Server certificate public key
-
spiInterface:
boolean
True- Use SPI Interface, False- Use OPI JSON Interface
-
supportsCardAcquisition:
boolean
Select True to enable the Payment Service Provider to supply Card Acquisition payment and loyalty data.(SPI only)
-
validateXMLAgainstSchema:
boolean
Validate XML message against schema and log errors in SPIXML.log.(SPI only)
Nested Schema : hierUnitName
Type:
objectAdditional Properties Allowed
Show Source
A group of string objects representing the name of the hierarchy unit configured languages.
Example:
{
"en-US":"Enterprise",
"de-DE":"Unternehmen",
"es-MX":"Empresa"
}Nested Schema : name
Type:
objectAdditional Properties Allowed
Show Source
A group of string objects representing the name of the Payment Driver in configured languages.
Example:
{
"en-US":"OPI",
"de-DE":"OPI",
"es-MX":"OPI"
}400 Response
400 Bad Request
Root Schema : ErrorDetails
Type:
objectResponse body when the request returns an error.
Show Source
-
detail(required):
string
A short, human-readable summary of the problem.Example:
Specified Data is invalid -
errorDetails(required):
string
A human-readable explanation specific to this occurrence of the problem.Example:
Entity Does Not Exist -
o:errorCode(required):
integer
Error code of the problemExample:
55223 -
status(required):
integer
HTTP status code.Example:
400 -
title(required):
string
A short, human-readable summary of the problem type.Example:
VALIDATION ERROR -
type(required):
string
A URI reference that identifies the problem type. When this member is not present, its value is assumed to be "about:blank".Example:
http://www.abc.org/xyz.html