> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://beta-docs.payabli.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://beta-docs.payabli.com/_mcp/server. # Changelog > **Tip** > > Subscribe to our changelog RSS feed: [https://docs.payabli.com/changelog.rss](https://docs.payabli.com/changelog.rss) ## 2025 * [April 2 Updates](/changelog/2025/4/2) - New endpoint for downloading chargeback attachments * [March 3 Updates](/changelog/2025/3/3) - New query parameters for export endpoints * [February 24 Updates](/changelog/2025/2/24) - New API fields * [February 21 Updates](/changelog/2025/2/21) - Improved error message for transaction amount limits * [February 5 Updates](/changelog/2025/2/5) - API updates * [January 14 Updates](/changelog/2025/1/14) - API updates * [January 1 Updates](/changelog/2025/1/1) - Custom batch times and enhanced refund flow ## 2024 * [December 29 Updates](/changelog/2024/12/29) - Added `externalPaypointId` to boarding application endpoints * [December 27 Updates](/changelog/2024/12/27) - DeviceID added to API responses * [December 23 Updates](/changelog/2024/12/23) - New query parameter * [November 26 Updates](/changelog/2024/11/26) - New status page * [November 20 Updates](/changelog/2024/11/20) - Improved error messages for managed payables * [November 19 Updates](/changelog/2024/11/19) - New user language field in the API * [October 22 Updates](/changelog/2024/10/22) - Playground, boarding and API enhancements * [October 10 Updates](/changelog/2024/10/10) - Support for Apple Pay payments * [July 23 Updates](/changelog/2024/7/23) - Enhanced batches and funding * [May 22 Updates](/changelog/2024/5/22) - Bug fixes for web apps and APIs * [April 22 Updates](/changelog/2024/4/22) - Chargeback notification enhancements and bug fixes * [March 20 Updates](/changelog/2024/3/20) - Fixes to application statuses and transfer notifications * [March 6 Updates](/changelog/2024/3/6) - Web app fixes and BIN data enhancements * [February 15 Updates](/changelog/2024/2/15) - Boarding and UI enhancements * [January 31 Updates](/changelog/2024/1/31) - Export, query, and boarding API enhancements ## 2023 * [December 7 Updates](/changelog/2023/12/7) - UI and reporting enhancements * [November 9 Updates](/changelog/2023/11/9) - New split funding functionality * [October 20 Updates](/changelog/2023/10/20) - Notes & Events, embedded components versioning, and numerous enhancements * [September 19 Updates](/changelog/2023/9/19) - New getPaid tokenization setting and bug fixes * [August 24 Updates](/changelog/2023/8/24) - Creator payments and improvements across apps * [August 1 Updates](/changelog/2023/8/1) - Persistent Creator columns and API improvements * [July 26 Updates](/changelog/2023/7/26) - Enhanced bill and invoice screens, Creator updates, and new webhook notifications * [June 29 Updates](/changelog/2023/6/29) - Canadian postal codes, batch report enhancements, and webhook headers * [June 1 Updates](/changelog/2023/6/1) - Batch report enhancements, and webhook headers ## April 2, 2025 ## New endpoint for downloading chargeback attachments We added the [GET /ChargeBacks/getChargebackAttachments/\{Id}/\{fileName}](/api-reference/chargebacks/get-attachments-from-chargeback) endpoint. This endpoint allows you to download chargeback attachments, such as PDFs or images, associated with a chargeback record. The `Id` parameter is the ID of the chargeback record, and the `fileName` parameter is the name of the file you want to download. ## March 3, 2025 ## New query parameters for export endpoints * Added the `limitRecord` query parameter to all export endpoints. This parameter limits the number of records to return for the query. The maximum is 30,000 records. When you don't include this parameter, the API returns up to 25,000 records. * Added the `fromRecord` query parameter to all export endpoints. This parameter specifies the record number to start the export from. The default is 0. You can use these query parameters together to paginate through large exports. For example, to get the first 10,000 records of an export, you would use `limitRecord=10000&fromRecord=0`. To get the next 10,000 records, you would use `limitRecord=10000&fromRecord=10000`. ## February 24, 2025 ## New API fields We've added several new fields to several endpoints. * Added the `AchSecCode` field to responses for the [GET Query/transactions](/api-reference/query/get-list-of-transactions-for-an-entrypoint) and [GET MoneyIn/details/\{transId}](/api-reference/moneyin/get-details-for-a-processed-transaction) operations. SEC code is a three letter code that describes how an ACH payment was authorized. The [Query/transactions](/api-reference/query/get-list-of-settled-transactions-for-an-entrypoint) endpoints also support filtering by `AchSecCode` and supports these operators: `ct`, `nct`, `in`, `nin`, `eq`, and `ne`. * Added a field that specifies what whether an accountholder is a person or a business to several request and response bodies. The field supports these values: `personal` and `business`. * Added the `achHolderType` field to the request bodies for the [POST TokenStorage/add](/api-reference/tokenstorage/save-a-payment-method-tokenize), [POST Subscription/add](/api-reference/subscription/create-a-subscription-or-scheduled-payment), [POST TokenStorage/update](/api-reference/tokenstorage/update-a-payment-method), and [POST MoneyIn/getpaid](/api-reference/moneyin/make-a-transaction) endpoints. * Added `AchHolderType` field to the responses for the [GET TokenStorage/\{methodId}](/api-reference/tokenstorage/get-a-payment-method), [GET Query/transactions](/api-reference/query/get-list-of-transactions-for-an-entrypoint) and [GET MoneyIn/details/\{transId}](/api-reference/moneyin/get-details-for-a-processed-transaction) endpoints. ## February 21, 2025 ## Improved error message for transaction amount limits We updated an error message to make it easier to understand. An error for a transaction amount outside of the maximum and minimum limits of a paypoint will now display the message: "Transaction amount is outside the minimum and maximum limit of the paypoint." instead of: "No tier is available for the amount, mode 0 or 2." ## February 5, 2025 ## API updates We've released several enhancements and bug fixes to our API. Here are the highlights: ## Pay In * Added the ability to skip a subscription payment by setting `totalAmount` to zero. See [Pause a subscription or skip a payment](/developer-guides/pay-in-manage-subscriptions#pause-a-subscription-or-skip-a-payment) for more details. * Added the `expectedProcessingDateTime` field to the responses for these endpoints: * [GET /MoneyIn/refund/\{transId}/\{amount}](/api-reference/moneyin/refund-a-settled-transaction) * [GET /MoneyIn/reverse/\{transId}/\{amount}](/api-reference/moneyin/reverse-a-transaction) * [POST /MoneyIn/refund/\{transId}](/api-reference/moneyin/refund-a-settled-transaction-with-instructions) When a paypoint has [Enhanced Refund Flow enabled](/guides/pay-in-enhanced-refund-flow), the `expectedProcessingDateTime` field shows the date and time that a queued refund is expected to be processed. ## Pay Out Added the `parentOrgId` filter with `(eq, neq, in, nin)` operators to these endpoints: * [Query/batchesOut/\{entry}](/api-reference/query/get-list-of-moneyout-batches-for-an-entrypoint) * [Query/batchesOut/org/\{orgId}](/api-reference/query/get-list-of-moneyout-batches-for-an-org) * [Query/payouts/\{entry}/\{orgId}](/api-reference/query/get-list-of-payouts-for-entrypoint) * [Query/payouts/org/\{orgId}](/api-reference/query/get-list-of-payouts-for-organization) * [Query/bills/\{entry}](/api-reference/bill/get-list-of-bills-for-entrypoint) * [Query/bills/\{entry}/org/\{orgId}](/api-reference/bill/get-list-of-bills-for-organization) * [Query/vendors/\{entry}](/api-reference/query/get-list-of-vendors-for-entrypoint) * [Query/vendors/org/\{orgId}](/api-reference/query/get-list-of-vendors-for-organization) ## Pay Ops * All instances of EIN values returned in API responses are now masked. * Added a `UpdatedMerchant` webhook notification for paypoint updates. You can now get a notification when a paypoint's address, banking information, or funding configuration is updated. See [Webhook Notification Response Reference](/developer-guides/webhook-payloads#updatedmerchant) for the webhook payload. * Added the `ReplyBy` field to responses from the [Query/chargebacks](/api-reference/query/get-list-of-chargebacks-and-returned-transactions-for-an-entrypoint) endpoint. The ReplyBy field is the deadline by which a merchant must respond to a dispute. By default, this field is exactly 10 days after the `CreatedAt` timestamp, in UTC. * Added the `replyDate` filter to the [Query/chargebacks](/api-reference/query/get-list-of-chargebacks-and-returned-transactions-for-an-entrypoint) endpoint which allows filtering disputes by deadline. `replyDate` has the following conditions: `(gt, ge, lt, le, eq, ne)`. See the [Filters and Conditions Reference](/developer-guides/reporting-filters-and-conditions-reference) for more information. ## January 14, 2025 ## API updates We've released several enhancements and bug fixes to our API. Here are the highlights: ## Pay In * Added new notifications for `TransferAdjusted`, `TransferReadyforRetry`, `TransferResolved` events. See [Notifications and Reports Overview](/developer-guides/notifications-and-webhooks-overview) for more information. * Added the `settings` objects for configuring Apple Pay for payment pages. Before, you had to use the `AdditionalData` object to configure Apple Pay. See [Configure the Apple Pay Button](/developer-guides/hosted-payment-page-apple-pay#configure-the-apple-pay-button) for more information. ## Pay Out * Implemented masking for the EIN field in the response for the [ GET /Bill/\{idBill}](/api-reference/bill/get-bill) endpoint. * Added the `Gateway` field in the response for the [/MoneyOut/details/\{transId}](/api-reference/moneyout/get-details-for-a-processed-payout-transaction) and [/Query/payouts/\{entry}](/api-reference/query/get-list-of-payouts-for-entrypoint) endpoints. ## Pay Ops Added four new export endpoints: * [/Export/batchDetails/\{format}/\{entry}](/api-reference/export/export-batch-details-for-entrypoint) * [/Export/batchDetails/\{format}/org/\{orgId}](/api-reference/export/export-batch-details-for-organization) * [/Export/batchesOut/\{format}/\{entry}](/api-reference/export/export-list-of-batches-out-for-entrypoint) * [/Export/batchesOut/\{format}/org/\{orgId}](/api-reference/export/export-list-of-batches-out-for-organization) Added a new query parameter `columnsExport` to export endpoints, including exports for: * Transactions * Batches * Subscriptions * Settlements * Transfers * Chargebacks * Customers * Organizations * Boarding * Paypoints * Invoices * Vendors * Bills * Payouts This new parameter lets you define a custom column mapping for an export. Documentation for the parameter is available in each endpoint's API reference. ## January 1, 2025 ## Custom batch times and enhanced refund flow We're excited to changes that allow you to close Pay In batches when it makes sense for your merchants. With [Custom Batch Times](/guides/pay-in-custom-batch-times), you can choose any hour of the day as your preferred batch cutoff time instead of using the default of 5 PM Eastern Time. We've also released the [Enhanced Refund Flow](/guides/pay-in-enhanced-refund-flow). This feature provides a frustration-free experience for processing card refunds, ensuring that refunds are processed at the optimal time to avoid issues with the backend processor. To opt in to Custom Batch Times or the Enhanced Refund Flow, contact the Payabli team. ## December 29, 2024 ## Added `externalPaypointId` to boarding application endpoints Added the `externalPaypointId` field to the following endpoints: * [GET /Boarding/app/\{appId}](/api-reference/boarding/get-boarding-application-by-id) * [POST /Boarding/app](/api-reference/boarding/create-boarding-application) * [PUT /Boarding/app/\{appId}](/api-reference/boarding/update-boarding-application) * [GET /Query/boarding/\{orgId}](/api-reference/boarding/get-list-of-applications-for-an-organization) The `externalPaypointId` field is an optional unique identifier for a paypoint. It's useful if you want to correlate a boarding application with a paypoint or merchant in your system. ## December 27, 2024 ## DeviceID added to API responses We've added the `DeviceID` field to transaction detail and transaction query responses. ## December 23, 2024 ## New query parameter We've added the `lastModified` query parameter to the [`/Query/paypoints` endpoint](/api-reference/query/get-list-of-paypoints-for-an-organization). You can use this parameter to filter paypoints by the date they were last modified. ## November 26, 2024 ## New status page We've released a new Payabli status page at [https://status.payabli.com/](https://status.payabli.com/). You can subscribe to updates from the page. ## November 20, 2024 New and updated query endpoints, and improved error messages This release brings you new query endpoints for batch details and improved error messages for managed payables. ## Improved error messages for managed payables We've improved error messaging for [MoneyOut/capture](/api-reference/moneyout/capture-an-authorized-payout-transaction) decline responses. When a capture of a managed payout is declined, you'll now get a clear and actionable message in the `resultText`. ## Changes to some query endpoints The `/Query/settlements` endpoints now only return details for settled transactions. To get details about all batched transaction, regardless of settlement status, use the new `batchDetails` endpoints: * By paypoint: [/Query/batchDetails/\{entry}](/api-reference/query/get-list-of-batchdetails-for-an-entrypoint) * By org: [/Query/batchDetails/org/\{orgId}](/api-reference/query/get-list-of-batchdetails-for-an-organization) ## November 19, 2024 ## New user language field in the API We've added a `language` field to user objects to support future localization of PartnerHub and PayHub. ## October 22, 2024 ## Playground, boarding and API enhancements This release includes a new developer tool, improvements to the boarding application process, and enhancements to the API for better tokenization and error handling. ## Embedded Components Playground We've released the Embedded Components Playground, a new developer tool that lets you build and preview embedded components in your browser. Learn more in the [guide](https://docs.payabli.com/developer-guides/embedded-component-playground), or try it out at [https://playground.payabli.com](https://playground.payabli.com). ## Boarding These changes impact the UI and boarding APIs. * Improved boarding application field validations to support Canadian applicants. ## API These changes impact the APIs. * Made enhancements to the TokenStorage/add endpoint and embedded components to improve the tokenization process for some cards. Before, tokenization sometimes failed for cards if they weren't being tokenized as part of a transaction. We've added two new keys to the tokenization request body: `fallbackAuth` and `fallbackAuthAmount` to run an authorization on cards while tokenizing them. See the [/TokenStorage/add](/api-reference/tokenstorage/save-a-payment-method-tokenize) reference, or the configuration reference section of the embedded components docs for more details. * Improved tokenization error handling. ## October 10, 2024 ## Support for Apple Pay payments Payabli is excited to announce support for Apple Pay. We've made setup and management a breeze, so you can focus on making sales. ## Activate Apple Pay Before you can accept Apple Pay for transactions, you must set it up and activate it for your organization and paypoints. How you activate Apple Pay depends on whether you use the PartnerHub UI or the Payabli APIs. * [Activate Apple Pay (API)](developer-guides/wallet-apple-pay-enable) * [Activate Apple Pay (UI)](/user-guides/wallet-apple-pay-enable) ## Accepting Apple Pay for transactions You can use the Express Checkout embedded component, hosted payment pages, or payment links to accept Apple Pay for one-time transactions. ### Via the embedded component Use the [Express Checkout embedded component](/developer-guides/embedded-components-express-checkout) for a secure low-code way to accept Apple Pay. ### Via hosted payment pages [Configure your payment pages](/developer-guides/hosted-payment-page-apple-pay) for a secure, no-code way to accept Apple Pay. ### Via payment links To accept Apple Pay from a payment link, set `paymentMethods.methods.applePay` to `true` when you [create a payment link](/api-reference/paymentlink/generate-payment-link-from-invoice) or [update an existing payment link](/api-reference/paymentlink/update-payment-link). ```json // example truncated "paymentMethods": { "methods": { "visa": true, "mastercard": true, "applePay": true "eCheck": true }, "enabled": true // example truncated ``` ## July 23, 2024 ## Enhanced batches and funding We're happy to announce the release of an improved version of the engine that drives batches and funding. We will be migrating all paypoints to the new engine between **July 23 and July 29.** The new batches and funding engine improves performance and observability, gives you the option to separate deposits from debits, like ACH returns and chargebacks, and gives you the option to choose between gross or net funding. If you choose gross funding, your debits can come from a bank account separate from your deposit account. The existing batches and funding engine provides net funding, and paypoints won't notice any changes to how funding works after the migration. If you want to stay with the current funding model, you don't need to take any action. If you want to move to a gross funding model or learn more about the new experience, reach out to the Payabli team. ## May 22, 2024 ## Bug fixes for web apps and APIs This release includes several bug fixes and enhancements across the web app, API, and embedded components. Here are the highlights: ## Notifications These changes impact notifications received via webhooks, SMS, and email. * Fixed an issue that prevented notifications from being sent to multiple email addresses. Notifications are now sent to multiple email addresses as expected. * Fixed an issue that prevented the activated merchant notification from being sent consistently. This notification now functions as expected. ## Boarding These changes impact boarding in the API and UI. * Fixed an issue that prevented updates to boarding application status. Application status updates now function as expected. ## Web app These changes impact PartnerHub, PayHub, or both. * Fixed a bug with payouts that caused incorrect record counts, totals, and total pages to be displayed. Record counts and totals now display as expected, and pagination works correctly. * Fixed an issue that caused some card payment details to be incompletely displayed in the UI. Now, card details for a transaction display as expected. * Fixed an issue with filters in the Transactions reports that prevented card transactions from being filtered correctly. The card filter now works as expected. ## API * Fixed a bug with the Query/payouts response that caused the summary to display incorrect record counts and totals. Record counts and totals now display as expected. * Fixed an issue that caused some reverse requests to fail on the MoneyIn/getpaid endpoint. Reverse requests now function as expected. * Fixed an issue that caused a 500 error to be triggered when certain lineItem fields are longer than allowed. Now, if a field is over, the API returns a 400 error with a clear error message. ## April 22, 2024 ## Chargeback notification enhancements and bug fixes This release includes several bug fixes and enhancements across the web app, API, and embedded components. Here are the highlights: ## Notifications These changes impact notifications received via webhooks, SMS, and email. We've added a new field to webhooks, email, and SMS notifications for new chargebacks and ACH returns. Now, when you have notifications enabled for new chargebacks or ACH returns, the notification includes the chargeback ID. In the `ReceivedChargeBack` and `ReceivedAchReturn` webhook payloads, the ID is returned as `chargebackID`. In email and SMS notifications, the field appears as Chargeback ID. ## Web app These changes impact PartnerHub, PayHub, or both. * Fixed a bug that prevented customers from entering alphanumeric ZIP codes on mobile devices. Now, alphanumeric ZIP codes are supported on mobile Virtual Terminals, payment pages, embedded components and more. * Fixed a bug that prevented header from being displayed on some new invoices. Headers now display as expected. ## API * Improved handling for special characters in fields related to ACH. Before, non-standard characters would cause the error "Narrative value is invalid". Now, Payabli transliterates these values to accepted characters. * Fixed an issue with transfer notification emails that caused reason messages to be cut off. Now, reason messages display as expected. * Fixed an issue with bulk payment files that caused all custom field names to be changed to lowercase. Now, Payabli preserves the original capitalization. * Fixed validation on some endpoints that caused them to return a 500 response instead of a 200 response with success details or a 400 response with error details. Affected endpoints now function as expected. * Fixed an issue with the `MoneyOut/captureAll`, `MoneyOut/capture`, and `MoneyOut/cancelAll` endpoints that prevented successful operations. ## March 20, 2024 ## Fixes to application statuses and transfer notifications These changes affect the Payabli web apps and APIs. * Fixed a bug with transfer notification emails that caused reason messages to be cut off. Now, reason messages display as expected. * Fixed a bug with boarding applications that caused submitted applications to stay in the *Not Submitted* status. Application statuses now work as expected. ## March 6, 2024 ## Web app fixes and BIN data enhancements This release includes several bug fixes and enhancements across the web app and API. Here are the highlights: ## Web app These changes impact PartnerHub, PayHub, or both. * Fixed a bug with pagination in reporting components. Pagination now works as expected. * Fixed a bug that caused the "Add Customer" window to close immediately when creating customer from an invoice. Adding a customer from an invoice now works as expected. * Fixed a bug that prevented autopay exports from the web apps in sandbox. Autopay exports now work as expected in PartnerHub and PayHub. * Fixed a bug that kept the "City" field from autopopulating while creating an organization. The field now populates as expected. * Fixed a bug that caused boarding application dates to display inconsistently. Dates now work as expected. ## API Added a `binData` object to the API response for these endpoints: * [/TokenStorage/\{methodId} GET](/api-reference/tokenstorage/get-a-payment-method) * [/MoneyIn/details/\{transId} GET](/api-reference/moneyin/get-details-for-a-processed-transaction) * [/Query/transactions/entry GET](/api-reference/query/get-list-of-transactions-for-an-entrypoint) * [/Customer/customerId GET](/api-reference/customer/get-customer-record) This `binData` object displays important information about a payment card's type and issuer, and includes the following fields: * `binMatchedLength`: The number of characters from the beginning of the card number that were matched against a Bank Identification Number (BIN) or the Card Range table. * `binCardBrand`: The card brand. For example, Visa, Mastercard, American Express, Discover * `binCardType`: The type of card: Credit or Debit. * `binCardCategory`: The category of the card, which indicates the card product. For example: Standard, Gold, Platinum, and so on. The `binCardCategory` for prepaid cards is marked `PREPAID`. Examples: * GOLD * PREPAID BUSINESS * PLATINUM TRAVEL * PREPAID RELOADABLE * `binCardIssuer`: The name of the financial institution that issued the card. * `binCardIssuerCountry`: The issuing financial institution's country name. * `binCardIssuerCountryCodeA2`: The issuing financial institution's two-character ISO country code. See [this resource](https://www.iso.org/obp/ui/#search) for a list of codes. * `binCardIssuerCountryNumber`: The issuing financial institution's ISO standard numeric country code. See [this resource](https://www.iso.org/obp/ui/#search) for a list of codes. _Showing the 20 most recent of 31 entries. Append `/llms.txt` to the changelog URL for the complete index._