Homologation

Before a connector can go to production, it must complete a homologation process with the OlaClick team. This verifies that all integration components work correctly.

Requirements

1. KYC Iframe — Style Compliance

The iframe must follow the Style Guide. The following will be verified:

Criteria	Description	Required
Color palette	Uses OlaClick's official colors (#006FFF, #003E8F, etc.)	Yes
Typography	Uses Inter or a compatible sans-serif	Yes
Buttons	Follow the defined style (border-radius, colors, hover)	Yes
Inputs	Follow the defined style (border, focus state, error state)	Yes
Responsive	Adapts correctly to different screen widths	Yes
Background	White or light gray, no dark backgrounds or custom colors	Yes
No own branding	Does not prominently display the connector's logos	Yes
Clear UX	Progress indicators, real-time validation, clear messages	Yes

tip

Send screenshots or a staging link of the iframe before scheduling the formal review — this speeds up the process.

2. Authentication — Token Generation

The connector must demonstrate that it can:

• Obtain an access_token using POST /oauth/token with its client_id and client_secret
• Correctly handle token expiration and renew before expiry
• Include the token in the Authorization: Bearer {token} header in all requests

Required test: Obtain a valid token in the staging environment.

3. Connection Status Update

The connector must demonstrate that it can:

• Call PATCH /v1/conections/:id with a Connector Token
• Send status: "active" when KYC validation is successful
• Send status: "rejected" when validation fails
• Handle errors correctly (404 when connection not found, 422 when invalid transition)

Required test: Update a connection from pending to active in the staging environment.

4. Invoice Emission

The connector must demonstrate that it can:

• Receive FISCAL_NOTES_REQUEST events and respond with 200 OK
• Verify the X-OlaClick-Signature header (see Signature Verification)
• Fetch order data using GET /v1/orders/:id
• Confirm with status: "COMPLETED" and invoice_number when the invoice is emitted
• Confirm with status: "REQUEST_ERROR" and message when emission fails
• Handle idempotency (same event_id received twice should not produce duplicate invoices)

Required test: Receive a test event, fetch the order, emit a test invoice, and confirm to OlaClick in the staging environment.

Homologation Process

Steps

1. Request homologation — Contact the OlaClick integrations team.
2. Provide staging access — Share the iframe URL in the staging environment.
3. Style review — OlaClick reviews the iframe against the style guide.
4. Functional tests — Token generation, connection activation, and invoice processing are tested.
5. Approval — Production credentials are delivered.

Staging Environment

Resource	URL
Public API	https://public-api.olaclick-stg.click
OAuth Token	POST https://public-api.olaclick-stg.click/oauth/token

Staging credentials will be provided for the homologation process.

Rejection Criteria

Homologation will be rejected if:

• The iframe doesn't follow the color palette or is not responsive
• The connector cannot generate a valid token
• API errors are not handled correctly
• The iframe redirects outside the context or opens unauthorized popups
• Fields are not validated in real time
• No clear feedback is shown about the process status

Estimated Time

Stage	Duration
Initial review	1-2 business days
Adjustments (if applicable)	Depends on the connector
Functional tests	1 business day
Credential delivery	1 business day

info

The complete process usually takes 3-5 business days if there are no major adjustments.