> 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

# September 2026 release notes

> What's new across Pay In, Pay Out, and Pay Ops in Payabli's September 2026 release

September 2026 is a big month for Pay Out. It gets a single-call payout endpoint, partial payments for bills, and a microdeposit fallback when a vendor's bank validation fails, plus clearer labels. Pay In sharpens batch and transfer timing, and Pay Ops adds a user-list export.

## Pay In

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

### Batch dates now reflect the actual cutoff time

`BatchDate` now reflects the real cutoff hour for real-time batches. Before, it always showed midnight no matter when the batch actually cut off, so a batch with a 9 PM ET cutoff reported `2026-07-28 00:00`. Now that same batch reports `2026-07-28 21:00`, and you can read funding timing straight from `BatchDate` without cross-checking a separate cutoff-time setting, which makes batch monitoring and reconciliation more precise.

In the Portal, the batch report shows the same change: the batch close date now includes the cutoff time instead of midnight.

**Action required:** Yes, if your integration matches `BatchDate` against an exact timestamp. Replace exact-midnight comparisons with a date range (for example, match `BatchDate` from `2026-07-28 00:00` up to `2026-07-29 00:00`), or update your logic to tolerate a non-midnight timestamp.

### Chargebacks and returns now filter by amount

The chargebacks and returns query (`GET /Query/chargebacks/{entry}`) now accepts two new amount filters. Before, you could filter only by `netAmount`, which matches the original transaction's net. Now, `amount` matches the record's own amount (the top-level `netAmount` in the response), and `totalAmount` matches the original transaction's gross, including service and pending fees. You can sort by both fields. This release also registers `replyBy` as a filter alias for `replyDate`, so filtering by `replyBy` now returns matching records instead of none.

**Action required:** None.

**Learn more:** [API changelog](/changelog/api-changelog/2026/9/8#2026-09-08-filter-chargebacks-and-returns-by-amount) · [List disputes by paypoint](/developers/api-reference/chargebacks/get-list-of-chargebacks-and-returned-transactions-for-an-entrypoint)

### Transfer dates now skip weekends and bank holidays

For some transfers, `TransferDate` now lands on a real banking day. Before, plain calendar math could put it on a Saturday, Sunday, or US federal holiday. Now Payabli rolls the date forward to the next business day, keeping the time of day, so `TransferDate` in the Batches and Funding reports reflects when funds actually settle. Transfers from before this release aren't updated.

**Action required:** None. Contact the Payabli team with questions about a specific transfer.

## Pay Out

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

### Single-call payout endpoint (authorize and capture)

A new `POST /MoneyOut/payout` endpoint runs authorize and capture in one call and returns the capture response. Capturing a payout used to take two calls, `POST /MoneyOut/authorize` followed by `GET /MoneyOut/capture/{referenceId}`, so integrations that need the capture result synchronously can now skip the second round trip.

**Action required:** None.

**Learn more:** [API changelog](/changelog/api-changelog/2026/9/8#2026-09-08-add-an-endpoint-to-authorize-and-capture-a-payout-in-one-call) · [Authorize and capture a payout](/developers/api-reference/moneyout/authorize-and-capture-a-payout) · [Manage payouts](/guides/pay-out-developer-payouts-manage#authorize-and-capture-in-one-call)

### Partial payouts for bills (managed payables)

You can now pay part of a bill instead of the full amount. Before, a bill had to be paid all at once. Now, if you're using managed payables, you can pay part of a bill in the Payabli Portal or through the API, and cover the rest later. The bill moves to a Partially Paid status and stays open until it's fully paid. You can see how much has been paid and how much is still owed on the bill.

Partial payouts let you pay a bill in stages without creating separate bills for each payment. To stay on top of them, subscribe to the Bill Partially Paid notification by email, SMS, or webhook.

**Action required:** Yes, if you want to use partial payouts: contact the Payabli team to enable them for your managed payables.

**Learn more:** [Manage bills](/guides/pay-out-developer-bills-manage) · [Partial payouts in the API changelog](/changelog/api-changelog/2026/9/8#2026-09-08-partial-payouts-for-bills-managed-payables)

### Microdeposit fallback on vendor links

When instant bank validation fails on a Pay Out vendor link, the vendor now sees an inline option to verify the account with microdeposits and continue. Before, they hit a generic error and got stuck. Now they can fix it themselves, so a failed bank check no longer blocks their payout.

**Action required:** None.

**Learn more:** [Verify bank accounts with microdeposits](/guides/pay-ops-microdeposit-portal-bank-account-verification)

### Separate statement descriptor for Same Day ACH credits

You can now request a separate bank statement descriptor for Same Day ACH credits to vendors, distinct from the one used for standard ACH. Before, every ACH credit to a vendor used the same descriptor regardless of speed. Now, when a vendor credit goes out as Same Day ACH, it uses the Same Day ACH descriptor if you've set one. Standard-speed credits keep using the standard descriptor.

**Action required:** Only if you want a distinct Same Day ACH descriptor: contact the Payabli team to set one up.

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

### Payout queries now filter by `orderId`

The payouts query endpoints now accept an `orderId` filter, matching the filter already available on transaction queries. Use it to look up a payout by the `orderId` you supplied on the original `MoneyOut` authorize request — for example, for an idempotency check after an `idempotencyKey` error. `orderId` accepts the `eq` and `ne` conditions and matches case-insensitively, and the payout query response now includes `orderId`, which is `null` for payouts that don't have one.

**Action required:** None.

**Learn more:** [API changelog](/changelog/api-changelog/2026/9/8#2026-09-08-filter-payouts-by-orderid) · [Get list of payouts for paypoint](/developers/api-reference/query/get-list-of-payouts-for-entrypoint)

### Payment Link renamed to Vendor Link

The Portal now says "Vendor Link" everywhere Pay Out used to say "Payment Link", including reports, bills, filters, and settings. The old label matched the wording for Pay In payment links, and the new one separates vendor payout links from those at a glance. Pay In payment links keep their labels, and API field values and endpoints keep their existing names.

**Action required:** Only if you bookmarked Pay Out payment-link pages in the Portal. The paths changed and the old ones don't redirect, so update your saved links.

**Learn more:** [Manage vendor links (Portal)](/guides/pay-out-portal-payment-links-manage)

### Processor renamed to Connector in Pay Out reports

The "Processor" column and filter now read "Connector" across the Pay Out Transactions, Batches, Transfers, and ACH Returns reports, matching the terminology used elsewhere in the product.

**Action required:** None.

**Learn more:** [Pay Out transaction reports (Portal)](/guides/pay-out-portal-transactions-reports)

### Wire and real-time payment balance checks return distinct error codes

Wire and real-time payment (RTP) payouts now return distinct error codes at authorize time. Before, `3729` covered both an amount over the available balance and balance information that was missing or unreadable. Now `3729` means only that the amount exceeds the available balance, and a new code, `3730`, covers missing or unreadable balance information.

**Action required:** Yes, if your integration branches on `3729`. It no longer covers missing or unreadable balance information. Add handling for the new `3730` so that case isn't misread as an over-balance error.

**Learn more:** [API changelog](/changelog/api-changelog/2026/9/8#2026-09-08-wire-and-rtp-balance-error-codes-split) · [Send instant payouts](/guides/pay-out-developer-instant-payouts#error-handling) · [API response codes](/developers/api-reference/api-responses)

### Bill-approved email uses the correct subject line

Bill-approved email notifications now use the subject line "Bill Approved Notice" instead of the earlier "Bill Paid Notice".

**Action required:** None.

## Pay Ops

These are the Pay Ops changes in the September 2026 release.

### Manage Users now exports the user list

You can now export the user list from Manage Users as a CSV or XLSX file, and choose which columns to include. The page listed users before but had no export, so pulling user data for compliance or audits meant copying rows by hand.

**Action required:** None.

**Learn more:** [Export users (Portal)](/guides/pay-ops-portal-users-manage#export-users)

### Webhooks no longer send duplicate or incorrect data during high activity

Webhooks no longer send duplicate or incorrect data during high activity. Before this release, a burst of activity could cause those delivery errors.

**Action required:** None.

### Password resets complete reliably

Resetting your password with the code from the reset email now completes reliably. Before this release, entering a valid code and new password could sometimes fail on the confirmation step.

**Action required:** None.