A Plan holds an ordered list of rules. When a transaction arrives for a merchant on that plan, Preczn works through the rules to decide which Connection receives it.

Most plans start with a rule already in place. Adding a connection to your platform creates a default plan for it carrying a single Distribution rule that sends 100% of volume to that connection, and a plan you build across payment connections gets a Distribution rule splitting volume evenly between them — so a plan can usually route before you configure anything.

📘
A transaction can opt out of routing entirely
If the transaction request names a processor, that connection is used and no rules are evaluated. Rules only apply when the request leaves the choice to Preczn. See Transaction Routing.

How Preczn chooses a connection

Rules are not all weighed together. Preczn works through them in a fixed sequence and stops at the first one that selects a connection.

Order — the request carries an order value and an earlier transaction used the same one. That earlier connection is reused, and nothing below is considered.
BIN — the card's leading digits match a BIN rule. Longer BINs are tested first, so the most specific match wins.
Distribution, Card Brand, or Currency — the first of these that matches, taken in the order the rules appear in your plan.

Reject Salvage sits outside this sequence because it does not choose a connection. Whichever rule above picks the first one, Reject Salvage defines which connections to try next if that attempt is declined.

❗️
Order within step 3 matters
A Distribution rule matches every transaction unconditionally. If one sits above a Card Brand or Currency rule in your plan, the rules beneath it are never reached. Keep your conditional rules above the Distribution rule you want as the fallback.

Rule order in a plan

The Rules section of the Plan Details page numbers rules by the priority you have arranged them in, and that number is the order used in step 3 above.

Two placements are managed for you rather than chosen:

A Reject Salvage rule is held at the top of the list. Because it is a retry policy rather than a routing decision, its position does not affect which connection is chosen first.
BIN rules are evaluated longest-BIN-first regardless of where they sit in the list, so a more specific BIN always beats a less specific one.

ACH transactions do not follow these rules

When the payment is a bank account, Preczn routes to a connection in the plan that supports ACH rather than applying the rules above. On a plan with one connection, that connection must support ACH. On a plan with several, the first ACH-capable connection in the plan is used. If no connection in the plan supports ACH, the transaction is rejected:

ACH transaction not supported for this Plan

See ACH (Direct Debit).

Working with rules

All rule types are added, edited, and removed the same way.

To add a rule

Open Routing → Routing Plans in the left navigation and select the plan.
In the Rules section, select Add Rule.
Choose the type from the RULE TYPE dropdown, then fill in the criteria for that type.
Select Save Rule.

To edit a rule, select Edit to the right of it in the Rules section, change what you need, then select Edit Rule.

To delete a rule, choose Delete from the dropdown beside that rule's Edit button and confirm.

📘
Adding a connection to an existing rule
A rule can only distribute across connections that its plan already holds. To widen a rule, first select Edit at the top of the Plan Details page, add the connection to the plan, save, and then edit the rule.

Percentages in any rule that distributes across connections must total exactly 100. A connection that should receive nothing needs an explicit 0; leaving the field empty is an error.

Rule types

A plan can hold any combination of the rules below, and most plans use more than one. Each entry covers what that rule matches on and what you configure; the order they are applied in is set out in How Preczn chooses a connection.

Distribution

Splits transactions across the plan's connections by a percentage you set. This is the rule every default plan starts with.

Choose how the split is measured:

Volume — by currency amount. Across 50 transactions totalling $500 on a 50/50 split, roughly $250 reaches each connection.
Count — by number of transactions. Across 60 transactions on a 50/25/25 split, 30 go to the first connection and 15 to each of the others.

Preczn tracks what each connection has already taken and sends the next transaction to whichever is furthest behind its target share, so the split converges over time rather than alternating strictly.

📘
What the split is measured over
Balancing is calculated within the current calendar month and is tracked separately for each currency and payment method type. The measurement restarts at the beginning of each month, and only approved transactions count toward it.

Card Brand

Routes on the card brand, optionally combined with an amount test. Use it to send a brand to the connection with the best economics for it.

Configure three things:

The card brand the rule applies to.
An amount comparison — greater than, less than, or equal to a value you set. The rule only matches when both the brand and the amount test pass.
How matching transactions are split across connections, by Volume or Count, exactly as the Distribution rule does.

Because a Card Brand rule only matches its own brand, place it above the Distribution rule that should catch everything else.

BIN

Routes on the Bank Identification Number — the leading digits of a card number, which identify the issuing bank and card programme.

Enter the BIN in the rule's criteria and choose the connection to receive matching transactions. A BIN rule sends all of its matches to a single connection rather than distributing them.

Preczn compares your BIN against the same number of leading digits on the card, so a 6-digit BIN tests the card's first 6 digits. Add as many BIN rules as you need; when a card matches more than one, the longest BIN wins.

A BIN must be 4 to 11 digits and digits only. Each BIN can appear once per plan — saving a plan with the same BIN on two rules is rejected:

BIN RULE values must be unique. Invalid values: 411111

The common use is a card programme you want kept on one connection — a virtual card issuer, or a corporate programme with negotiated pricing.

Currency

Routes non-USD transactions to a chosen connection.

The rule takes one connection and applies to every transaction whose currency is not USD. There is nothing else to configure and no split to set. Transactions in USD are unaffected and fall through to the next matching rule.

See Country & Currency Codes.

Order

Keeps every transaction that shares an order value on the same connection.

An order identifier ties several transactions to one purchase — an instalment schedule, or a capture that follows an authorization. The transaction API accepts order as an optional field for this.

Adding the rule to a plan is the whole configuration. Once it is present, Preczn looks for an earlier transaction carrying the same order and, if it finds one, routes to the connection that most recent transaction used. If there is no match, the remaining rules decide as usual.

This matters most when a plan distributes across connections. On a 50/50 split, the two payments of one order would otherwise land on different connections, leaving a single purchase with settlement and any later dispute spread across two providers.

🚧
Order routing affects your distribution split
Holding an order on one connection sends volume there that a Distribution rule would otherwise have balanced elsewhere. The Distribution rule compensates by favouring the other connections on subsequent transactions, so the split still converges — but over a longer period than it would without Order routing.

❗️
Order and Reject Salvage cannot be combined
The two rules cannot be used on the same plan. If a plan needs Reject Salvage, remove the Order rule first.

Reject Salvage

Retries a declined transaction against the plan's other connections, in an order you set. A card one connection declines may still be approved by another, so the rule exists to recover authorizations that would otherwise be lost.

Reject Salvage is only offered on a plan holding more than one connection.

The rule gives every connection in the plan a position, and you choose which connection sits in each one. That is the order they are attempted in. Because each connection already occupies a position, you can reorder them but cannot drop one from the rule.

When the first attempt is declined, Preczn moves to the next connection in the rule — skipping the one that already ran — and continues until a connection approves the transaction or the list is exhausted.

Two limits are worth knowing:

Only a declined authorization triggers a retry. A transaction that errors is not salvaged.
Verify transactions are never salvaged, even on a plan carrying the rule.

❗️
Weigh the risks before enabling Reject Salvage
Retrying a decline elsewhere can leave a cardholder with several authorizations that never settle, reducing the credit available to them.
Connections apply their own risk and settlement policies. A transaction can be authorized at one connection and still be withheld from settlement there — for example where AVS or CVV rules are enforced. The retry that follows may then authorize against a card that is already near its limit, and a later attempt can come back for insufficient funds.
The rule is offered for convenience, and the trade-off is yours to make deliberately rather than by default.