February 5
API enhancements and new webhook notifications

Pay In

Added the expectedProcessingDateTime field to the responses for these endpoints:

When a paypoint has Enhanced Refund Flow enabled, 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:

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 for the webhook payload.
  • Added the ReplyBy field to responses from the Query/chargebacks 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 endpoint which allows filtering disputes by deadline. replyDate has the following conditions: (gt, ge, lt, le, eq, ne). See the Filters and Conditions Reference for more information.
January 14
Enhancements and fixes to the Pay In, Pay Out, and Pay Ops features and APIs.

Pay In

  • Added new notifications for TransferAdjusted, TransferReadyforRetry, TransferResolved events. See Notifications and Reports 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 for more information.

Pay Out

Pay Ops

Added four new export endpoints:

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
Introducing Custom Batch Times and the 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, 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. 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.

Was this page helpful?