Skip to main content

March 3rd 2026

R
Written by Richard Thorne
Updated over 2 weeks ago

Release Notes

  • Simplifying Barter Onboarding
    ​

To enable BarterPay (either for the first time or when re-enabling), a valid BarterPay Merchant ID must be provided. The integration cannot be enabled without this required input

  1. When enabled with a valid Merchant ID, the system will call the BarterPay Add-Integration API using the expected payload. During this process, the entityId will be automatically fetched from the instance and appended to the webhook path.

  2. API response

    1. If the API response is not success, the integration will not be enabled and an error message will be displayed via a toast notification.

    2. If the API response is success, the system will fetch the API key and stored for future authentication.

  • Cash Drawer Actuals to Show Only Payment Types with Data
    ​
    1. The Cash Drawer Actuals will shows only payment type columns that contain transaction data, so that we can focus on relevant payment methods without visual clutter.

    2. Payment types that are currently disabled will still be shown if they contain data.The filtering logic is based solely on the presence of data and does not depend on the enabled or disabled status of the payment type.
    ​
    ​

Did this answer your question?