> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gigstack.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up the issuing business

> Confirm the team, country, credentials, and environment before issuing your first fiscal document.

Before building an invoice, record four choices: **which business issues it, its invoicing
country, the API environment, and live or test mode**. These choices determine which
credentials and numbering configuration gigstack uses.

## 1. Select the business

Select the intended team in [gigstack](https://app.gigstack.pro). Save its team ID and
confirm its registered name with the account owner. For a multi-business integration,
follow [gigstack Connect](/guides/gigstack-connect) to select an authorized team.

You can read the team's identity with [Get team](/reference/getTeamsById).
The public team response does **not** expose the invoicing provider and country selection.
Its postal address, the customer's country, currency, or `sat.completed` alone cannot
prove which fiscal flow is configured.

Ask the account owner to confirm the configured issuing country and provider. Keep that
choice in your integration's configuration. If the country is unknown or is not covered
by these guides, stop before issuance and confirm the supported setup with
[support](mailto:support@gigstack.io). Do not default to Mexico.

## 2. Match the key and mode

Use the [quickstart environment commands](/quickstart#1-set-your-environment) to set
`GIGSTACK_BASE_URL` and `GIGSTACK_API_KEY` locally. Read
[Authentication and test mode](/authentication#environments) to choose the host and key.
A staging key requires the staging host;
a public test key uses the public host. A test request does not configure the issuing business.

Start with a new test customer and confirm its returned `livemode` is `false`.
Use a test key for the entire practice flow. For a saved draft, also inspect the draft's
stored mode before stamping. Do not put credentials or certificate passwords in source code.

## 3. Complete the country's setup

| Issuer | Account owner completes | API integration checks |
| - | - | - |
| Mexico | Registered identity, valid CSD certificate and private key/password, and invoicing provider setup | Intended team and mode; recipient fiscal data; successful issuance and returned UUID |
| Colombia | Registered identity, Colombian provider credentials, and numbering configuration for the selected test or live environment | Intended team and mode; DIAN recipient identity; provider result and persisted document |

### Mexico

Open the selected team's [Integrations](https://app.gigstack.pro/integrations) and its
**SAT** connection. The owner supplies the CSD files and password. The equivalent API
upload is documented in [SAT connection](/guides/teams#upload-sat-csd-certificates); read the accepted
multipart fields before sending files. A CSD is the issuing certificate; do not substitute
a different credential because its file extension looks similar.

Then follow [Mexico fields](/countries/mexico) and the
[draft, preview, and issue walkthrough](/recipes/invoice). A customer being saved or a PDF
preview being generated does not prove that issuer credentials will pass stamping.

### Colombia

For a Colombian team, [Integrations](https://app.gigstack.pro/integrations) includes
**Facturación Electrónica**. Its **Información fiscal** form collects the legal name,
NIT, street, department, city, and postal code. Saving that identity form alone does not
connect provider credentials or configure an authorized numbering range.

Have the owner confirm Colombian provider onboarding and the numbering range for the
same environment as the key. gigstack resolves separate test and live provider settings.
If credentials or numbering have not been supplied, complete that setup with your account
owner or [support@gigstack.io](mailto:support@gigstack.io) before calling the issuance endpoint.
Include the team ID, issuing country **Colombia**, API environment (public or staging),
and intended mode (test or live). Request confirmation that provider activation and the
numbering range are ready for that mode, plus an approved test recipient and its fiscal
classification for your first test. Do not email API keys, provider passwords or other
credentials; do not send them as fields of an invoice request.

Continue with the [Colombia customer and invoice example](/countries/colombia#first-immediate-payment-invoice).
These setup instructions were checked against the application and API source; they do not
claim a completed Colombian test issuance.

## Ready to continue

You should know the team ID, owner-confirmed issuing country/provider, correct base URL,
key mode, and whether the country's credentials and numbering are ready. Keep issuance,
customer email delivery, payment collection, cancellation, and refund approval separate:
a setup guide does not authorize any of those actions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.