Pular para o conteúdo

Onboarding

Before initiating any Pix journey with Lina Pay, you need to understand the tenant/sub-tenant architecture and configure at least the domains that will appear in the redirectUri of your payment consents. This page walks through that initial setup and points to the APIs you will call along the way.

Companies and linked companies (tenants and subtenants)

Lina Pay allows a company (tenant) to have one or more linked companies (sub-tenants). This architecture separates payments by tenant and sub-tenant, keeping credentials isolated and allowing unique configurations — such as webhook delivery and branding customization — per sub-tenant.

Configure your redirect domains (required before Pix journeys)

The redirectUri you send in the body of POST /consents is where the end user lands after approving the payment at their bank. Lina enforces an allow-list of domains per sub-tenant: any URL sent as redirectUri must belong to a domain previously registered for that sub-tenant, otherwise the consent is rejected.

For every domain you plan to use as redirectUri target (including staging, production, and any white-label surface), call POST /api/v1/sub-tenants/domains once. You can inspect the currently registered domains of your sub-tenant via GET /api/v1/sub-tenants.

Initial setup flow

  1. Issue an access token — see Get your credentials.
  2. Call GET /api/v1/sub-tenants to inspect your current sub-tenant (id, branding, registered domains).
  3. For each domain that will be used in redirectUri, call POST /api/v1/sub-tenants/domains.
  4. (Optional) Call PATCH /api/v1/sub-tenants to adjust branding — logo, primary/secondary colors, and fonts.
  5. You're ready to initiate payments through Instant Pix.

Managing additional sub-tenants

In addition to the sub-tenant provisioned by Lina during your onboarding, you can create new sub-tenants programmatically — useful when you operate multiple brands, verticals, or isolated environments under the same tenant. Each new sub-tenant receives its own eppIamClientId / eppIamClientSecret pair, so payments, webhooks, and branding stay isolated.

Next steps