Skip to main content

​
Regional Posture Hub — Per-Country Rules Index

Country rules sprawl. Sender registration lives with one regulator, marketing consent with another, quiet hours with a third — and Orbit’s per-country pages each document one jurisdiction in depth. This page is the index over all of them: one matrix to find your target country’s page, one workflow to route a send failure to the right surface, and one template so new country pages stay uniform. Everything here documents tenant-owned controls. Orbit maintains the country-rules reference and the send-time gates; the legal posture for each destination is yours. This page is documentation, not legal advice.
Country coverage is tenant-level — a country listed here is not necessarily enabled on your account. The live, per-channel answer for any destination is always GET /api/v1/compliance/country-rules, not this page; this page points you at the right deep-dive once you know the row.

​
The country matrix

Start with the live row, then read the page. The first stop for any destination is the Country Compliance Requirements reference — per country and per channel, it carries the accepted sender types, the registration level (none / recommended / required), content restrictions, and the opt-out keyword requirement.
Where a jurisdiction needs more than a matrix row — an opt-in regime, a no-send window, a statutory register — Orbit ships a dedicated page. Those pages aggregate here: Registration levels change at the regulator — always read the live registration field for your target row rather than relying on this table’s snapshot. Where the row says recommended or required, file the sender through Sender-ID Registration; where a country runs its own regime (India DLT, US 10DLC), use the dedicated flow its page describes.

​
Check the row first, then the law

When a send to a new destination fails or filters, walk this sequence — it resolves the large majority of country-launch failures before they reach support:
1

Read the country-rules row

GET /compliance/country-rules?channel=<channel> for the destination. If registration is required and you have no approved Sender ID for that country, the send-time gate holds the traffic — this is the intended behavior, not a fault.
2

Match the sender type

Confirm your “from” identity is in the row’s sender_types. An alphanumeric Sender ID into a long-code-only market (or the reverse) fails at the carrier even when consent is perfect.
3

Check content and keyword requirements

Read content_restrictions and stop_requirement on the row. A missing localized STOP keyword (French STOP au 36111 is the canonical example) or a restricted industry (list) blocks or filters the send independently of registration.
4

Open the dedicated page

If the row is satisfied and sends still fail, the destination’s dedicated page (matrix above) maps the remaining obligations — opt-in regimes, no-send windows, statutory scrub registers — to the Orbit surface that carries each one.
5

Escalate with the row and page in hand

If the gate still looks wrong after both steps, contact support with the country code, the channel, the registration value you read, and what the send-time gate returned. Support routes country-rule disputes much faster with those four facts than with a message ID alone.
The full per-gate error surface is Troubleshooting Compliance Error Codes; the matrix above tells you which page a country-specific code belongs to.

​
How the table stays current

Country rules are not a frozen snapshot — Orbit refreshes the structural fields (sender types, registration level, regulator links) of each row from upstream registries on a weekly cadence, and a platform admin can pull a registry on demand. A refresh can raise a row’s registration level but never lower it, and it never overwrites editorial text your team has written — so a row changing under you is a designed event, stamped with which registry did it and when. Read Country Rules Auto-Refresh Feeds for the per-registry source list, the never-overwritten columns, the provenance stamp on every row, and how to check sync health.

​
Template for a new per-country page

New per-country pages follow one shape so the matrix stays browsable. Copy this outline and fill each section — a page that skips a section leaves a support gap the hub cannot route around:
  1. Frontmatter — title: "<Country> <Regime> Rules" + a one-line description naming the country, the regime, and the channels it covers.
  2. Opening paragraphs — the regulating body and statute, which channels it governs, and whether the regime is opt-in or opt-out. State plainly that the posture is tenant-owned: Orbit provides the surfaces, the tenant owns the legal position.
  3. A <Note> — documentation, not legal advice; name the enforcement exposure (penalties, enforcement body) without advising on it.
  4. Obligations → Orbit surface table — one row per statutory duty mapped to the consent ledger, DNC scrub, suppression, quiet-hours, or recording-announcement surface that carries the evidence. This table is the page’s spine; it is what the hub’s step 4 links into.
  5. Send-time posture — the org-level knobs the country’s regime argues for (consent-default policy, unknown-marketing policy) with a copy-pasteable configuration call.
  6. Worked configuration — a numbered end-to-end sequence a tenant can follow before first send, ending at a defensible posture.
  7. Related references — cross-links to the country-requirements reference, the sender-registration flow, and the sibling regime pages.
Keep one jurisdiction per page, cite the official law once in the opening, and add the page to this hub’s matrix in the same change — an unlisted country page is a country page nobody finds.