> This is Payabli documentation. For a complete page index, fetch https://docs.payabli.com/llms.txt — append .md to any page URL for lightweight markdown. For section-level indexes, query parameters, and other AI-optimized access methods, see https://docs.payabli.com/ai-agents.md

# November 2026 release notes

> What's new in Pay In and Pay Out in Payabli's November 2026 release

November 2026 focuses on Pay Out. Pay Out reports and query responses now show readable status labels, checks can print your mailing address, and check reissues let you pick the funding account. In Pay In, legacy payment page links now redirect to the current payment pages. Several fixes change how payout data behaves, so check the breaking changes before you update your integration.

## Pay In

These are the Pay In changes in the November 2026 release.

### Legacy payment page links redirect to the current payment pages

Links to legacy payment pages now redirect automatically to the current version of Payabli's payment pages. Payors who open an old link land on the current page, and you don't need to change your links. Since November 5, payments made through a current payment page or payment link show `paymentpage-v2` as their source. With the redirect, payments through legacy links do too. Before, these payments showed a source of `Payment Page` or `Payment Link`, or `RDC` for check capture.

**Action required:** Yes, if any of your integration logic, such as reporting, reconciliation, or webhook handling, checks the payment source for `Payment Page`, `Payment Link`, or `RDC`. Update it to recognize `paymentpage-v2`. If it uses the source to tell payment links from payment pages, use another field instead, such as the invoice number, because both now share one source. If you use legacy payment page links, open them and check that each page loads and takes payments as you expect. If anything looks wrong, contact Payabli support.

**Learn more:** [Hosted payment page overview and quickstart](/guides/pay-in-payment-page-overview)

## Pay Out

These are the Pay Out changes in the November 2026 release.

### Mailing address on checks

You can now choose which address prints as the sender on your check payouts: your business address or your mailing address. Set it at the organization or paypoint level in your Pay Out settings. Checks keep printing your business address unless you turn it on. If your check service is set to use Payabli's address, Payabli's address prints instead, and it takes priority over this setting.

**Action required:** None.

### Readable status labels in Pay Out reports and exports

Pay Out query responses now include a readable label next to each numeric status, so you don't need to map status codes to names yourself. For example, a bill with a status of `20` has a label of `Approved`. JSON responses only gain fields. CSV and XLSX exports add a label column right after each status column, which shifts every later column one place to the right.

**Action required:** Yes, if you read Pay Out exports by column position: update your integration to the new column layout.

**Learn more:** [API changelog](/changelog/api-changelog/2026/11/17#2026-11-17-status-labels-in-pay-out-query-responses-and-exports) · [Pay Out statuses](/guides/pay-out-status-reference)

### Choose the funding account when you reissue a check

When you reissue a payout as a check in the Payabli Portal, and your paypoint has more than one funding account for checks, you can now choose which account funds the reissued check. Before, Payabli picked the account for you. If your paypoint has one funding account, nothing changes.

**Action required:** None.

**Learn more:** [Reissue a payout](/guides/pay-out-portal-transactions-reports#reissue-a-payout)

### Pay Out reports show batch status first

The Batches report now shows **Batch Status** right after **Batch Date**, and canceled batches show **Canceled** instead of N/A. You can also filter batches by the Canceled status. **Payment Group Status** is hidden by default, so the default Batches export no longer includes the `Payment_Group_Status` column. In the Transactions report filters, **Bill Number** now sits next to **Check Number**, and the vendor, line item, and bill number search lists scroll correctly. Saved custom views don't change.

**Action required:** Yes, if you use the default Batches export and need `Payment_Group_Status`: add **Payment Group Status** back in the column picker.

**Learn more:** [Manage Pay Out batches](/guides/pay-out-portal-batches-funding-manage)

### Payout batch date filters match the response dates

Filtering payout batches by `batchDate` or `transferDate` now uses UTC, the same time zone as the dates in the response. Before, the filters shifted the date by your organization, paypoint, or user time zone, so filtering by one day could return the next day's batches. The dates in the response don't change.

**Action required:** Yes, if your time zone isn't UTC and you filter payout batches by date: check that your filters return the batches you expect.

**Learn more:** [API changelog](/changelog/api-changelog/2026/11/17#2026-11-17-payout-batch-date-filters-match-the-response-dates)

### Virtual card decline messages include the decline reason

When a virtual card payout is declined at capture, the decline message now includes the reason, such as an invalid ZIP code, so you can fix the vendor's details and try again. In `responseData.resultText`, the code at the start changes from a name such as `BadRequest` to a number such as `400`. `resultCode` is still `3`.

**Action required:** Yes, if your integration matches on the text of virtual card decline messages: update it to the new format.

**Learn more:** [API changelog](/changelog/api-changelog/2026/11/17#2026-11-17-virtual-card-decline-messages-include-the-decline-reason)

### Placeholder bill due dates are ignored

When you add or update a bill, a due date earlier than 1900, such as `0001-01-01`, now counts as not sent. A new bill gets today's date as its due date, and an updated bill keeps its existing due date. Bills without a valid due date also get the capture date when they're paid, so payment records no longer show a due date of `01/01/0001`. A recurring bill sent with one of these dates now returns error `3211`.

**Action required:** Yes, if your integration sends placeholder due dates: send a real due date or leave the field out.

**Learn more:** [API changelog](/changelog/api-changelog/2026/11/17#2026-11-17-placeholder-bill-due-dates-are-ignored)

### Resent virtual card links reach funded cards

On paypoints with virtual card funding holds, resending a card link for a funded card now sends the card-ready email, so the vendor can use the card. Before, it always sent the awaiting-funds email.

**Action required:** None.

### Account holder names with punctuation are accepted on bank payouts

ACH, wire, and RTP payouts no longer fail when the account holder name contains punctuation, such as `O'Brien-Smith, Jr.` Payabli removes the characters the bank network doesn't accept.

**Action required:** None.

### Processed checks can be reissued again

Processed check payouts offer the reissue action again, in the Payabli Portal and in the `allowedActions` returned for payouts.

**Action required:** None.

### Funding debits always include a payment descriptor

Funding debits for payouts that aren't tied to a bill now include a payment descriptor on the merchant's bank statement.

**Action required:** None.

**Learn more:** [Payment descriptors](/guides/pay-out-payment-descriptors-overview)

### The vendor field keeps its value in Send Payment

In the Payabli Portal, picking another vendor with the same display name no longer clears the vendor field when you send a payment or create a ghost card.

**Action required:** None.