Sites
A site represents a distinct location or channel within your merchant account where payments are processed. Every payment — whether it's online or in person — is attributed to a site.
All transactions processed through a given site are grouped together for settlement. That means the funds from one site are paid out alongside all the other transactions from that same site.
Site types
Each site is configured as one of two types:
| Type | What it's for |
|---|---|
| Ecommerce | Online payments through your website or app, using the Online Payments API |
| In-person | Face-to-face payments using yetipay terminals, through Pay At Counter or Pay At Table |
A site can only be one type — you can't mix online and in-person payments on the same site.
Why sites matter
- Settlement grouping. All funds processed by a site are settled together. If you need separate payouts for different parts of your business (e.g. different store locations, or online vs in-store), set them up as separate sites.
- Payment routing. When you call the API, the
siteIdin the URL tells us which site the payment belongs to. - Configuration. Each site can have its own settings — payment methods, capture mode, and so on.
Example setup
A restaurant chain with an online ordering platform might have:
| Site | Type | Purpose |
|---|---|---|
site-london-01 | In-person | London branch terminals |
site-manchester-01 | In-person | Manchester branch terminals |
site-online | Ecommerce | Online ordering website |
Each site settles independently, so the London branch's takings are paid out separately from Manchester's, and both are separate from online orders.