This changelog provides an overview of the recent changes made to the Payabli APIs.
This entry covers the API changes released on May 11, 2026.
We’ve updated the supported filter operators on the List vcards by paypoint and List vcards by org 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 for the full operator list.
All other filters and response fields are unchanged.
We’ve documented two endpoints for retrieving virtual card transactions:
GET /Query/vcardsTransactions/{entry})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.
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 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.
Reject transaction statusThe 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 or List transactions for org endpoints, a value of -4 is returned in the TransStatus field for transactions that were rejected.
See the Money in transaction status reference for the full list of transaction statuses and their meanings.
Reject value for operation filterThe operation filter on the List transactions for paypoint and List transactions for org 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 to learn more about using filters to query transactions.
cardRejectedAmount fields on transfer details endpointWe added two new cardRejectedAmount fields to the Get 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.
StoredMethod field and idPmethod filter on subscription queriesThe List subscriptions by paypoint and List subscriptions by organization 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.
splitCount field on transaction query responsesThe List transactions for paypoint and List transactions for org 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.
Date on check event on payout transactionsWe’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 for the recommended extraction pattern, and the Get payout details endpoint for the full response shape.
remitEmail filter on vendor query endpointsThe List vendors by paypoint and List vendors by 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 addressesWe’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, Update vendor, and any other endpoint that accepts vendor address data.