v1
latestOpenAPI 3.0.02026-07-2480677847.6 KBModify Merchant Specific Pricing
This operation enables the consumer to update their merchant-specific pricing setup, including transaction charges, account fees, or both. This endpoint can be utilized for the following purposes,
- To expire all existing active and future effective dated merchant-specific charges and create new future effective dated merchant-specific charges. In this scenario, the user must provide a list of default recordIdNumbers from the current tariff assigned to the merchant along with the fee values that need to be overridden.
- To expire all existing active and future effective dated merchant-specific charges and change the tariff assignment for the merchant, creating new future effective dated merchant-specific charges for the new tariff. In this case, the user must provide a list of default recordIdNumbers from the new tariff to be assigned to the merchant along with the fee values to be overridden. Note that if a merchant already has any future effective dated tariff change in place, adding another future effective tariff change is not permitted.
Headers
Standard HTTP Header; Represents the format of the payload being provided in the request. This must be set to application/json and applicable for POST/PATCH.
An RFC4122 UUID used as to trace requests.
For test environment, specific test environment name should be passed (e.g. "bwu15"). Contact Fiserv OmniPay Project team to get confirmation on the test environment to be used. For production, value "prod" should be populated.
Institution number (8-digit number) associated with the merchant. This information defines the acquirer for the merchant.
OPY Internal Client Number
Request body
Example request
{
"accountFees": {
"serviceContractIndex": "497",
"clientTariffIndex": "000321",
"existingMsfFeeExpiryDate": "20251231",
"individualFees": [
{
"recordIdNumber": "9999999999",
"effectiveDate": "20200615",
"expiryDate": "20251231",
"feeMode": true,
"feePercentage": "5.0",
"feeBase": "100.0",
"feeMinimum": "13.0",
"feeMaximum": "13.0",
"triggerHighValue": "250.0",
"triggerVolumeHigh": "250"
}
]
},
"transactionCharges": {
"serviceContractIndex": "497",
"existingMsfFeeExpiryDate": "20251231",
"tierStructureIndex": "000",
"individualFees": [
{
"serviceIndex": "101",
"merchantTariffIndex": "000573",
"recordIdNumber": "9999999999",
"effectiveDate": "20200615",
"expiryDate": "20251231",
"feeMode": true,
"feePercentage": "5.0",
"feeBase": "250.0",
"feeMinimum": "250.0",
"feeMaximum": "250.0",
"chargeCurrencyCode": "EUR"
}
]
}
}Response
OK
Example response
{
"meta": {
"paging": {
"count": 100,
"totalPages": 10,
"currentOffset": 1,
"currentNumberOfRetrievedRecords": 10,
"maxLimit": 10,
"hasMoreRecords": true,
"pageNumber": 1
},
"sorting": {
"sort": "name,-startDate"
},
"messages": [
{
"id": "dd4ba13c-4a3c-4078-a31f-35ac9c07a8f7",
"code": "ACCOUNT_NUMBER_NOT_FOUND",
"title": "The authorization credentials required for this request are invalid.",
"detail": "SQLException found while trying to establish the connection with table TUKCDHN.",
"source": {
"pointer": "/dogs/name",
"parameter": "type",
"header": "type"
}
}
]
},
"errors": [
{
"id": "dd4ba13c-4a3c-4078-a31f-35ac9c07a8f7",
"code": "ACCOUNT_NUMBER_NOT_FOUND",
"title": "The authorization credentials required for this request are invalid.",
"detail": "SQLException found while trying to establish the connection with table TUKCDHN.",
"source": {
"pointer": "/dogs/name",
"parameter": "type",
"header": "type"
}
}
],
"links": {
"self": "https://api.firstdata.com/ipp/accounts-management/v1/accounts?offset=3&limit=10",
"first": "https://api.firstdata.com/ipp/accounts-management/v1/accounts?offset=1&limit=10",
"last": "https://api.firstdata.com/ipp/accounts-management/v1/accounts?offset=10&limit=10",
"prev": "https://api.firstdata.com/ipp/accounts-management/v1/accounts?offset=2&limit=10",
"next": "https://api.firstdata.com/ipp/accounts-management/v1/accounts?offset=4&limit=10"
}
}