PayPilot Version 3.0.2

PayPilot 3.0.2 gives you more control over aging unsettled transactions and terminal transfers, while historical transactions keep their original context.

Open batches now settle automatically at 30 days

Behavior change · Batch Close

What changed: When the earliest eligible unsettled transaction in an open batch reaches 30 days, PayPilot settles the entire batch through Force Batch Settlement. The threshold is inclusive, and every eligible unsettled transaction in the batch is included, not only the one that reached 30 days. Once triggered, the batch no longer waits for standard Batch Close. After settlement succeeds, PayPilot closes the batch and places new transactions in a new batch.

Why it matters: Unsettled transactions no longer stay open indefinitely.

Set how long transactions stay eligible for Batch Close

Improved · Batch Close

What changed: Choose whether eligible unsettled transactions stay available for standard Batch Close for 7, 15, or 30 days. Transactions older than the selected period are excluded from standard Batch Close and marked Force Settlement Required, and Batch Close results show their count and amount. If you shorten the period, PayPilot warns you that existing transactions may move into the Force Settlement range.

Why it matters: You decide how long unsettled transactions can wait for standard Batch Close before they're flagged for Force Settlement.

Access: Configure Register > Settlement > Batch Close > Force Batch Validity. New and existing configurations default to 30 days. This setting doesn't change the 30-day Force Batch Settlement threshold.

Reassign a terminal to another merchant or store

Improved · Terminal binding

What changed: Bind New Terminal now handles terminals already assigned to another merchant or store, not only unbound terminals. After you enter the Terminal SN, PayPilot verifies it and shows the terminal's current merchant, store, and batch status. If the terminal has an open batch or unsettled transactions, choose one:

• Force Batch Settlement: The terminal moves only after settlement succeeds. If settlement fails or can't be confirmed, the original assignment stays in place.
• Ignore and Force Bind: The terminal moves right away. Existing transactions, batches, and settlement records stay with the original merchant, store, and Terminal SN.

PayPilot rechecks the assignment when you select Bind, blocks duplicate submissions while processing, and logs standard and forced moves separately as Terminal Bind and Force Bind.

Why it matters: You can move a terminal in one dialog and see its current assignment and open batch before you commit.

Continue Capture, Refund, and Void after a terminal moves

Improved · Cloud API

What changed: Authorized Cloud API callers can continue eligible Capture, Referenced Refund, and Void actions on an existing transaction after its terminal is unbound or reassigned. PayPilot evaluates these actions against the transaction's original merchant, store, terminal, TID, payment channel, and processor, instead of the terminal's current assignment. Historical transactions don't move with the terminal, and the new store can't access them. Existing authorization, transaction-status, amount, time-limit, Batch Close, payment-channel, and processor rules still apply.

Why it matters: Moving a terminal no longer cuts off follow-up actions on its earlier transactions.

Compatibility

No changes are required for existing Cloud API integrations. Request and response structures, idempotency handling, and processor response-code mapping are unchanged.

Known limitations

• This release doesn't add Unreferenced Refund.
• Rules for starting new transactions on an unbound terminal are unchanged.

Support

For questions or support, contact support@codepay.us.