Channel control is a cash management feature that lets you define transaction posting rules based on a transaction’s channel, or origin. It allows you to configure exceptions to standard end‑of‑day (EOD) cutoff rules for specific channels, such as ATM, while transactions from all other channels follow standard cutoff processing.

You manage channels by creating or deleting them as needed. Each channel is assigned a unique code when it's created and that code can't be changed afterward. When you delete a channel, the Pismo platform keeps it in the historical record and marks it as inactive. Channels aren’t created automatically and must be explicitly set up by your organization.

How channel control works

Channel control extension to past-business-date toggle

The past-business-date toggle determines whether a transaction can use a business date other than the current date. Channel control extends this behavior with channel-based exceptions, letting you choose which channels may bypass cutoff restrictions.

When you configure the toggle with allowed channel codes, transactions submitted through an allowed channel may bypass cutoff restrictions. If you remove a channel from the allowed list, the Pismo platform rejects any new transactions that violate cutoff rules. If a transaction references a deleted or unknown channel, the Pismo platform returns a 4XX validation error.

Safeguards

Channels must exist before you can use them. If a toggle update includes an invalid channel, the Pismo platform rejects the request.

Create channel control

Endpoints

You can use the following channel control endpoints to create and delete channels.

Channel Rules

Channel‑based business date exceptions

You can configure channels that are exempt from business‑date cutoff rules or remove a channel from exemptions by using the Past business date toggle endpoint.

Using channels in transactions

Transactions may include one of the following channel identifiers, which determines how business-date and cutoff rules are applied during validation.

Each transaction in a bulk request is validated independently. Clients can include a channel identifier on a transaction to apply channel-specific validation rules, including any cutoff exemptions. In bulk requests, clients can provide a channel identifier per transaction to apply channel-specific business-date and cutoff rules during validation.

Common use cases

Post transactions after cutoff

On the Pismo platform, channel control defines the rules that determine which actions are allowed through each access channel, under which conditions, and within which limits. In some cases, a client may need to bypass specific rules, such as cutoff restrictions. This feature enables that behavior.

For example, a client may allow transactions from the ATM channel. Because ATM transactions can arrive after the cutoff date using a back business date, the Pismo platform accepts the request. Transactions from any other channels that are not explicitly allowed remain restricted.

Remove a previously allowed channel

If the client removes the ATM channel from the exception list, any new ATM transactions violating cutoff rules are rejected.

Bulk payments with mixed channels

When a bulk file includes entries with and without a channel:

• Entries with a valid channel follow exception rules.

• Entries without a channel follow standard cutoff behavior.

• Each entry is evaluated independently.

Channel events

The Pismo platform emits the following events, which you can use to manage channel creation and update descriptions as needed.

• Channel created, updated, or deleted