Issuer and channel network setup

Every Omni request is scoped to the issuer authenticated by the API token. During onboarding, Percents associates that issuer with exactly one channel-partner network. Clients do not send an issuer ID, network ID, partner name, or override in a request.

Percents completes these steps separately in sandbox and production:

1. Create or identify the issuer account.
2. Associate the issuer with the agreed channel-partner network.
3. Issue an API token owned by that issuer.
4. Enable Omni catalog access and any agreed file-upload content contracts.
5. Configure source-IP allowlists and the issuer webhook destination.
6. Issue a separate webhook signing token.

The issuer record is the authentication principal. Its channel-network association determines which merchants and offers are visible and how uploaded transaction files are processed. A valid token does not grant access to every network.

The association is intentionally absent from request parameters:

GET /api/v1/omni/offer
Authorization: token tok_...:api_...

Percents resolves the token to its issuer, then resolves that issuer to its channel-partner network. Resource-by-ID endpoints apply the same scope. If an offer or merchant UUID exists under another network, the API returns 404 instead of revealing it.

File uploads also use the authenticated issuer's configuration. The content query parameter selects an enabled processing contract and expected schema; it does not select a channel network.

For each environment, provide Percents with:

• the legal issuer and program name;
• the channel-partner network agreed for that program;
• stable outbound IP addresses or CIDR ranges;
• a public HTTPS webhook URL; and
• the file content contract required by the integration.

Percents returns the API token and webhook signing token through an approved secure channel. Store them separately.

Use sandbox credentials to list merchants and offers, then compare the returned catalog with the expected channel-partner network. Complete this check before accepting transaction files or launching production traffic.

If the catalog is empty or belongs to an unexpected network, stop and contact Percents. Do not try another issuer's token or add an undocumented partner identifier to the request.