Update a store
PUT api/stores
Updates an existing store.
Note: In testing, updating a store without including card_acceptor_identifier cleared its existing value. Include the current card_acceptor_identifier in the request if you want to keep it.
Request syntax
put api/stores '{"store_id":<store_id>,"<field>":"<value>"}'
Request parameters
The request accepts the following data in JSON format.
| Parameter | Type | Description | Required |
|---|---|---|---|
store_id | Integer | The store ID. | Yes |
store_number | Integer | The new store number. When updating, the store number is sent as an integer. Changing it also changes the store's owner_name. | No |
store_name | String | The new name of the store. | No |
address1 | String | The first line of the physical address of the store. | No |
address2 | String | The second line of the physical address of the store, such as a suite or unit number. | No |
city | String | The city of the physical address of the store. | No |
state | String | The state of the physical address of the store. | No |
zip | String | The zip code of the physical address of the store, as 5 digits or 9 digits, for example 78731 or 78731-1234. | No |
country | String | The country of the physical address of the store. | No |
phone_number | String | The phone number of the store, for example 512-555-0100. | No |
timezone | String | The timezone of the store, for example Eastern Standard Time. | No |
group | String | The store group that the store belongs to. | No |
level_of_hierarchy | String | The level of hierarchy that the store is assigned to, for example USA > NE > New York. | No |
card_acceptor_identifier | String | Required only if the ETL feature is enabled for the customer. The value must then be unique for the customer and is returned in the response. If the ETL feature is disabled, don't include this parameter in the request. | No |
Payment configuration fields
The following optional fields set the store's payment configuration. These fields aren't returned in store responses.
SC//Reliant™ Platform Manager uses these values to build the store's payment server configuration files from configuration templates. Each value is available in templates through the template tag listed in the table. A value can be used in templates only when the matching payment integration (AJB FIPay or eSocket) is enabled for the site, and the field is selected on the matching payment configuration tab of the global store settings.
AJB FIPay fields
| Parameter | Type | Description | Template tag | Required |
|---|---|---|---|---|
host_processor | String | The host processor in the store's payment configuration. | {{store.host_processor}} | No |
gift_card_merchant_number | String | The gift card (stored value) merchant ID in the store's payment configuration. | {{store.gift_merchant_id}} | No |
vxn_merchant_id | String | The store's VXN merchant ID (MID). | {{store.vxn_merchant_id}} | No |
merchant_terminal_id | String | The merchant terminal ID (TID) in the store's payment configuration. | {{store.merchant_tid}} | No |
payment_switch_1_ip | String | The IP address of the primary payment switch. If this value is blank, the store uses a direct-to-bank template. | {{store.payment_switch_1_ip}} | No |
payment_switch_2_ip | String | The IP address of the secondary payment switch. | {{store.payment_switch_2_ip}} | No |
payment_switch_1_certificate_name | String | The name of the certificate used for the primary payment switch. | — | No |
payment_switch_2_certificate_name | String | The name of the certificate used for the secondary payment switch. | — | No |
bank_processor_url_1 | String | The primary bank processor URL (the primary VXN SDC URL). | {{store.bank_processor_url_1}} | No |
bank_processor_url_2 | String | The secondary bank processor URL (the secondary VXN SDC URL). | {{store.bank_processor_url_2}} | No |
stored_value_processor_url_1 | String | The primary stored value (gift card) processor URL. | {{store.stored_value_processor_url_1}} | No |
stored_value_processor_url_2 | String | The secondary stored value (gift card) processor URL. | {{store.stored_value_processor_url_2}} | No |
dcc_functionality_enabled | String | Whether Dynamic Currency Conversion (DCC) is enabled for the store, for example ENABLED. | {{store.dcc_functionality}} | No |
dcc_functionality_value | String | The DCC functionality value. | — | No |
eSocket fields
| Parameter | Type | Description | Template tag | Required |
|---|---|---|---|---|
config_server_ip_address | String | The IP address of the eSocket configuration server. | {{store.configserverip}} | No |
config_server_port | String | The port of the eSocket configuration server. | {{store.configserverport}} | No |
itk_fixed_node_port | String | The eSocket ITK fixed node port. | {{store.itkfixednodeport}} | No |
itk_variable_node_port | String | The eSocket ITK variable node port. | {{store.itkvarnodeport}} | No |
pincomm_prompt_debit | String | The eSocket PINComm prompt debit setting. | {{store.pincommpromptdebit}} | No |
ubl_lcr_threshold | String | The eSocket UBL LCR threshold. | {{store.ubllcrthreshold}} | No |
Response syntax
{
"exporter_job": integer,
"id": integer,
"store_number": "string",
"store_name": "string",
"hostname": "string",
"group": "string",
"owner_name": "string",
"level_of_hierarchy": "string",
"card_acceptor_identifier": "string",
"created_at": "timestamp",
"updated_at": "timestamp"
}
Response parameters
If the action is successful, an HTTP 200 response is returned. The following data is returned in JSON format.
| Field | Type | Description |
|---|---|---|
exporter_job | Integer | The ID of the exporter job performing the action. |
id | Integer | The store ID. |
store_number | String | The store number. It can include leading zeros, for example 0001. Together with store_name, it uniquely identifies the store. |
store_name | String | The store name. |
hostname | String | The hostname of the node or server that manages the store, for example pfc2324pay0. Empty if no host is assigned. |
group | String | The store group, for example US_ENGAGE. |
owner_name | String | A display name generated from the store number, city, and state, for example Store: 9901 (Austin/TX). |
level_of_hierarchy | String | The level of hierarchy the store is assigned to, for example United States > NE > NJ. null if the store isn't assigned to a level of hierarchy. |
card_acceptor_identifier | String | The card acceptor identifier for the store. |
created_at | Timestamp | The timestamp for when the store was initially created. |
updated_at | Timestamp | The timestamp indicating when the store was last updated. |
Errors
The following are common errors returned by this API.
| Code | Message | Cause |
|---|---|---|
| - | - | - |
Examples
Example: Update the phone number of a store
This example updates the phone number of the store with ID 25651. The response doesn't include the phone number.
ruby api.rb <customer_code> put api/stores '{"store_id":25651,"phone_number":"512-555-0100"}'
Response
{
"exporter_job": 1781615,
"id": 25651,
"store_number": "9901",
"store_name": "Docs Test Store",
"hostname": "",
"group": null,
"owner_name": "Store: 9901 (Austin/TX)",
"level_of_hierarchy": null,
"card_acceptor_identifier": null,
"created_at": "2026-10-10T17:36:20.630Z",
"updated_at": "2026-10-10T17:40:22.489Z"
}
Example: Change the number and name of a store
This example changes the store number of the store with ID 25656 to 9918 and its name to Docs Renamed. The request includes the current card_acceptor_identifier so that the value is kept.
ruby api.rb <customer_code> put api/stores '{"store_id":25656,"store_number":9918,"store_name":"Docs Renamed","card_acceptor_identifier":"DOCS9908"}'Response
{
"exporter_job": 1781680,
"id": 25656,
"store_number": "9918",
"store_name": "Docs Renamed",
"hostname": "",
"group": null,
"owner_name": "Store: 9918 (Austin/TX)",
"level_of_hierarchy": null,
"card_acceptor_identifier": "DOCS9908",
"created_at": "2026-10-10T22:05:24.788Z",
"updated_at": "2026-10-10T22:06:57.688Z"
}