Overview
Stores represent physical or online locations belonging to a merchant. When a merchant has multiple branches or POS locations, each one can be registered as a store. This lets you attribute payments to specific locations for reporting, and aligns with SKAT SAF-T compliance requirements. A default store is automatically created when a merchant first sets up their POS. Partners can create additional stores at any time via this API.Create a Store
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Store name |
locationId | string | No | SKAT location identifier (auto-generated if omitted) |
streetAddress | string | No | Street address |
city | string | No | City |
postalCode | string | No | Postal code |
countryCode | string | No | Two-letter country code (default: DK) |
phone | string | No | Store phone |
email | string | No | Store email |
isDefault | boolean | No | Set as default store for the merchant |
Response
List Stores
Response
Get Store Details
Update a Store
Deactivate a Store
"isDefault": true.
Using Stores with Payments
Pass thestoreId when creating a payment to attribute it to a specific store:
storeId and registerId are optional. If omitted, the payment is not attributed to a specific location. See the Payment Integration guide for the full create-payment reference.
API Quick Reference
| Operation | Method | Endpoint |
|---|---|---|
| Create store | POST | /partner/merchants/:merchantId/stores |
| List stores | GET | /partner/merchants/:merchantId/stores |
| Get store | GET | /partner/merchants/:merchantId/stores/:storeId |
| Update store | PUT | /partner/merchants/:merchantId/stores/:storeId |
| Deactivate store | DELETE | /partner/merchants/:merchantId/stores/:storeId |

