> 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

This entry covers the API changes released on May 11, 2026.

## Card Account Updater for stored cards

We've documented Card Account Updater, a service that automatically refreshes stored card credentials when cards expire, are reissued, or are closed. Twice per month, it checks stored cards that are expiring in the current or next month against the Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) programs, then refreshes the stored token when an update comes back. This reduces recurring payment declines from stale card data.

Subscribe to the new `CardUpdaterComplete` notification event to receive each paypoint run's results by email (CSV) or webhook. See [Card Account Updater](/guides/platform-tokenization-card-updater) for the result code reference and setup, and the [Notifications overview](/guides/pay-ops-notifications-webhooks-overview#merchant-events) for the event.

Contact your Payabli representative to enable Card Account Updater on one or more paypoints, or across your entire organization.

## Updated filter operators on virtual card query endpoints

We've updated the supported filter operators on the [List vcards by paypoint](/developers/api-reference/query/get-list-of-virtual-cards-for-entrypoint) and [List vcards by org](/developers/api-reference/query/get-list-of-virtual-cards-for-organization) endpoints. Identifier filters now support numeric range comparisons, and string filters support starts-with and ends-with matching.

The `sw` (starts with) and `ew` (ends with) operators are new across the API. See the [Filters and conditions reference](/guides/pay-ops-reporting-overview#filters-and-conditions-reference) for the full operator list.

### Updated filters

| Filter       | Before                               | After                               |
| ------------ | ------------------------------------ | ----------------------------------- |
| `status`     | `eq`, `ne`, `in`, `nin`              | `eq`, `ne`, `ct`, `nct`, `sw`, `ew` |
| `paypointId` | `eq`, `ne`, `in`, `nin`              | `eq`, `ne`, `gt`, `ge`, `lt`, `le`  |
| `payoutId`   | `eq`, `ne`, `ct`, `nct`, `in`, `nin` | `eq`, `ne`, `gt`, `ge`, `lt`, `le`  |
| `vendorId`   | `eq`, `ne`, `ct`, `nct`, `in`, `nin` | `eq`, `ne`, `gt`, `ge`, `lt`, `le`  |
| `orgName`    | `eq`, `ne`, `ct`, `nct`              | `eq`, `ne`, `ct`, `nct`, `sw`, `ew` |
| `cardType`   | `eq`                                 | `eq`, `ne`, `gt`, `ge`, `lt`, `le`  |

All other filters and response fields are unchanged.

## New endpoints for querying virtual card transactions

We've documented two endpoints for retrieving virtual card transactions:

* [List vcard transactions by paypoint](/developers/api-reference/query/get-list-of-virtual-card-transactions-for-entrypoint) (`GET /Query/vcardsTransactions/{entry}`)
* [List vcard transactions by org](/developers/api-reference/query/get-list-of-virtual-card-transactions-for-organization) (`GET /Query/vcardsTransactions/org/{orgId}`)

Each record returns virtual card and transaction details, with filters covering both transaction-level fields and the underlying card. See either endpoint's API reference for the full field and filter list.

## New card rejection status

We added the `Reject` transaction status in the Payabli API.
This new status is for transactions that were rejected by the issuing bank or card network after being authorized or settled.
See [Card rejection](/guides/pay-in-cards-cycle-overview#card-rejection) for more information.
We also added new features across the API to allow users to filter for transactions with card rejections and see the amounts rejected.

### New `Reject` transaction status

The `Reject` transaction status has a value of `-4`.
This status indicates that a transaction was rejected by the issuing bank or card network after being authorized or settled.
When querying transactions with the [List transactions for paypoint](/developers/api-reference/query/get-list-of-transactions-for-an-entrypoint) or [List transactions for org](/developers/api-reference/query/get-list-of-transactions-for-an-organization) endpoints, a value of `-4` is returned in the `TransStatus` field for transactions that were rejected.
See the [Money in transaction status reference](/guides/pay-in-status-reference#money-in-transaction-status) for the full list of transaction statuses and their meanings.

### New `Reject` value for `operation` filter

The `operation` filter on the [List transactions for paypoint](/developers/api-reference/query/get-list-of-transactions-for-an-entrypoint) and [List transactions for org](/developers/api-reference/query/get-list-of-transactions-for-an-organization) endpoints now supports the `Reject` value.
Use this value to filter for transactions that were rejected by the issuing bank or card network after being authorized or settled.
See the [Filters and conditions reference](/guides/pay-ops-reporting-overview#filters-and-conditions-reference) to learn more about using filters to query transactions.

### New `cardRejectedAmount` fields on transfer details endpoint

We added two new `cardRejectedAmount` fields to the [Get transfer details](/developers/api-reference/query/get-list-of-transfer-details) endpoint.
The `cardRejectAmount` field in the `Summary` object reflects the total amount of all transactions in the transfer that were rejected by the issuing bank or card network after being authorized or settled.
The `cardRejectAmount` field in each `Record` object reflects the amount of that specific transaction that was rejected.
See the endpoint's API reference for the full response shape.

## New `StoredMethod` field and `idPmethod` filter on subscription queries

The [List subscriptions by paypoint](/developers/api-reference/subscription/get-list-of-subscriptions-for-an-entrypoint) and [List subscriptions by organization](/developers/api-reference/subscription/get-list-of-subscriptions-for-an-org) endpoints now return the full stored payment method linked to each subscription as a new `StoredMethod` object. Both endpoints also accept a new `idPmethod` filter that narrows results by the linked stored method's identifier. See either endpoint's API reference for the full field list and operators.

## New `SubscriptionType` field and filter on subscription queries

The [List subscriptions by paypoint](/developers/api-reference/subscription/get-list-of-subscriptions-for-an-entrypoint) and [List subscriptions by organization](/developers/api-reference/subscription/get-list-of-subscriptions-for-an-org) endpoints now return a `SubscriptionType` field on each record and accept a new `subscriptionType` filter. The field distinguishes `Regular` subscriptions (fixed-amount recurring) from `BalanceDriven` subscriptions (amount tracks an outstanding balance), and returns `null` when no type is assigned. The filter supports `eq`, `ne`, `in`, and `nin` and accepts values case-insensitively. See either endpoint's API reference for the full field list and operators.

## New `subscriptionType` request parameter and balance-driven subscriptions

The [Create subscription](/developers/api-reference/subscription/create-a-subscription-or-scheduled-payment) endpoint now accepts a new optional `subscriptionType` parameter with two values: `Regular` (the default — a standard fixed-amount recurring subscription) and `BalanceDriven`. A balance-driven subscription charges the payor's outstanding balance at run time instead of a fixed amount. Each scheduled run reads the live balance and charges that amount; a zero balance is skipped, not charged.

`subscriptionType` can't be changed after the subscription is created.

The [Get subscription](/developers/api-reference/subscription/get-subscription) endpoint now also returns `SubscriptionType` on the single-subscription response.

### New monthly cadence frequencies

`scheduleDetails.frequency` on the [Create subscription](/developers/api-reference/subscription/create-a-subscription-or-scheduled-payment) and [Update subscription](/developers/api-reference/subscription/update-subscription) endpoints accepts three new values:

* `firstofmonth`
* `fifteenthofmonth`
* `endofmonth`

These cadences are valid for both `Regular` and `BalanceDriven` subscriptions. `BalanceDriven` subscriptions only accept these three values.

### BalanceDriven schedule rules

For `BalanceDriven` subscriptions:

* `scheduleDetails.startDate` is calculated automatically from the chosen frequency. Any value you supply is ignored.
* `scheduleDetails.endDate` doesn't apply — these subscriptions run until cancelled.
* No static `totalAmount` is stored on the schedule. The amount is determined at each run.

## New `splitCount` field on transaction query responses

The [List transactions for paypoint](/developers/api-reference/query/get-list-of-transactions-for-an-entrypoint) and [List transactions for org](/developers/api-reference/query/get-list-of-transactions-for-an-organization) endpoints now return a `splitCount` integer on each transaction record. The value reflects the number of split funding instructions associated with the transaction, matching the length of `splitFundingInstructions` in the same record.

## New `Date on check` event on payout transactions

We've added a new `Date on check` entry to the `Events` array on payout transaction records. This event surfaces the exact date the check printer recorded for the check, which is the value most banks expect in a Positive Pay file.

The date is embedded directly in the `TransEvent` string in `M/D/YYYY H:MM:SS AM/PM` format. For example: `Date on check: 5/11/2026 8:42:22 AM`. Strip the `Date on check:` prefix from the `TransEvent` value, trim any leading space, and convert the date to the format your bank requires.

For payouts issued before May 11, 2026, the `Date on check` event isn't present. Continue using the `EventTime` of the `Captured` event as a fallback.

See [Integrate Positive Pay](/guides/pay-out-checks-positive-pay) for the recommended extraction pattern, and the [Get payout details endpoint](/developers/api-reference/moneyout/get-details-for-a-processed-payout-transaction) for the full response shape.

## New `remitEmail` filter on vendor query endpoints

The [List vendors by paypoint](/developers/api-reference/vendor/get-list-of-vendors-for-entrypoint) and [List vendors by organization](/developers/api-reference/vendor/get-list-of-vendors-for-organization) endpoints now accept a `remitEmail` filter that narrows results by the vendor's remittance email. The filter is case-insensitive and supports the `ct`, `nct`, `eq`, and `ne` operators, matching the existing `email` filter.

## `/` is now allowed in vendor and remittance addresses

We've added `/` to the set of characters allowed in Pay Out vendor street and remittance address fields. This supports common US fractional-house-number formats like `2524 1/2 S Dunsmuir Ave`.

The full allowed character set is now letters, numbers, spaces, and `. , # ' - & /`.

This affects the address fields on [Create vendor](/developers/api-reference/vendor/create-vendor), [Update vendor](/developers/api-reference/vendor/update-vendor), and any other endpoint that accepts vendor address data.