Sage 100

 View Only

  • 1.  Two changes in REPAY Credit Card processing causing disruptions

    Posted 10-09-2024 13:44

    I'm seeing two major issues with Repay causing disruptions with our clients this month.  @Wayne Schulz mentioned one in a Facebook Post that caught my attention and one of our clients is experiencing the other.
    1. October 3rd:  Sage 100 64-Bit Installs require a manual Registry change. 
    Sage 100 64-bit: Workaround to fix payment form issues - REPAY ERP & eCommerce Release Notes

    2. October 8th:  Sage 100 Transaction ID Error where the Repay Transaction ID's were expanded from 10 to 15 digits.  Repay has download "hot fixes" for v2022, v2023 and v2024; and are 'expected' to release for v2020 and v2021 this week.
    Sage 100: Version 7.09 - REPAY ERP & eCommerce Release Notes 

     



    ------------------------------
    Madeline Stefanou
    RKL eSolutions, LLC
    ------------------------------


  • 2.  RE: Two changes in REPAY Credit Card processing causing disruptions

    Posted 10-09-2024 14:38

    Repay has a pretty good running list of updates which they post to their site - https://releases.repay.com/ - and you can also "subscribe to updates" ( upper right corner of their KB screen) to receive email alert summaries as they post changes into the KB. I think I get alerts around once a week.



    ------------------------------
    Wayne Schulz
    wayne@s-consult.com
    Schulz Consulting
    (860) 516-8990
    Moodus, CT
    ------------------------------



  • 3.  RE: Two changes in REPAY Credit Card processing causing disruptions

    Posted 10-18-2024 07:51

    From Dylan at Repay:

    Dear Valued Customer, 

    We're writing to make you aware of an issue that affects Sage 100 implementations with SQL databases.  

    Recently, transaction IDs from the payment gateway increased to 11 digits. By default, Sage 100 supports 10-digit transaction IDs. Pre-authorizations are successful, but running Daily Sales Reports/Update to capture payments results in "Transaction not found REFID" errors. 

    To address this issue, we've released an updated version of the REPAY addition - version 7.09 - that increases the field length to 15 digits.  

    If your instance of Sage 100 uses a SQL database, please update to version 7.09 of the REPAY addition. The linked documentation explains how to resolve payment captures that failed. 

    Downloads: https://releases.repay.com/sage-100-version-7.09-10xx2E  

    Documentation: https://s3.us-west-2.amazonaws.com/downloads.repay.com/BP/Sage+100/Docs/Sage100-v7.09-ResolveTransactionNotFound.pdf

    If you have any questions, please contact support. 

    Sincerely, 
    REPAY Sales 



    ------------------------------
    Brett Zimmerman
    Net at Work
    Greater Boston Area
    ------------------------------

    Original Message


Related Content