You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Mridul Pathak <mr...@apache.org> on 2026/06/19 13:06:51 UTC

Proposal: Remove deprecated third-party payment gateway integrations

Hi all,


I'd like to propose removing the following payment gateway integrations
from applications/accounting/ whose third-party APIs and SDKs are no longer
operational, deprecated, and haven't been maintained for a while:


   - PCCharge & RITA (GO Software / Verifone): Verifone announced
   end-of-life in April 2015; all support terminated on October 1, 2015. Both
   communicate over raw TCP/IP sockets to a local Windows daemon with no cloud
   successor.
   Ref:
   https://3dmerchant.com/blog/merchant-processing-industry-news/pccharge-life-notice-verifone
   - ClearCommerce: Acquired by FIS. Implemented back in 2006 and never
   really maintained. The original platform and its test endpoint are no
   longer reachable.
   - Orbital (Chase Paymentech / Fiserv): Deprecated; no new onboarding
   available. The proprietary SDK is no longer distributed and the integration
   is already excluded from standard compilation.
   - Payflow Pro (PayPal): Officially labeled "legacy" by PayPal. ACH
   closed May 2021, 3DS v1.x  deprecated October 2022. The SDK (
   paypal.payflow.PayflowAPI) is unavailable in any public repository and
   excluded from compilation.
   - PayPal NVP / Classic API: Officially labeled "legacy". All dependent
   resources (Orders v1, Payments v1, Billing Agreements, etc.) are formally
   deprecated by PayPal. The SDK (com.paypal.sdk.core.nvp.*) is unavailable
   publicly and excluded from compilation.
   Ref: https://developer.paypal.com/api/rest/deprecated-resources/
   Ref: https://developer.paypal.com/api/nvp-soap/
   - WorldPay: The specific product this integration targets, WorldPay
   Select Junior, is absent from Worldpay's current developer documentation
   entirely. The integration uses a redirect-based flow (instId parameter,
   select.worldpay.com) with no equivalent in the current Access Worldpay
   REST API.

   Ref: https://developer.worldpay.com
   -

   SecurePay (Australia): The integration uses the proprietary
securepay.jxa Java
   SDK targeting https://api.securepay.com.au/xmlapi/payment, which has no
   public repository or Maven artifact. SecurePay has been acquired by Fat
   Zebra, whose platform is built on REST APIs with no equivalent to this
   XML-based integration. The integration is already excluded from standard
   compilation in build.gradle due to the missing SDK.

   Ref: https://www.fatzebra.com/blog/fat-zebra-acquires-securepay
   -

   eWay (Australia): The integration targets hardcoded legacy .asp XML
   endpoints (https://www.eway.com.au/gateway/xmlpayment.asp,
   gateway_cvn/xmlpayment.asp) from eWAY's original gateway circa 2003.
   eWAY has fully replaced this with the Rapid API (REST/JSON). NetSuite has
   officially retired the eWAY XML gateway integration.

   Ref:
   https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html
   Ref: https://eway.io/api-v3/
   -

   SagePay (now Elavon/Opayo): The integration targets SagePay's VPS
   Protocol v3.00, communicating with *.sagepay.com endpoints. SagePay was
   sold to Elavon in 2020 and rebranded as Opayo. Protocol v3.00 has since
   been mandated for removal in favour of v4.00, and all legacy
sagepay.com URLs
   (live.sagepay.com, test.sagepay.com) stopped working after March 31,
   2024.
   -

   CyberSource ICS (Simple Order API / SOAP): The integration uses the
   com.cybersource.ws.client SOAP SDK targeting API version 1.43.
   CyberSource has mandated migration away from the Simple Order API to its
   REST API, stating that users "must migrate" to REST-based services.
   Additionally, the SOAP API's current username/password authentication will
   be rejected after June 24, 2026, with no path to continue using the
   Simple Order API beyond that point without a full re-implementation. The
   integration is already excluded from standard compilation in
build.gradle due
   to the missing SDK JAR.

   Ref:
   https://developer.cybersource.com/docs/cybs/en-us/rb-upgrade/migration/all/na/recurring-billing-upgrade/rb-upgrade-actions/rb-upgrade-updating/rb-upgrade-apis.html
   Ref:
   https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.html
   -

   Authorize.Net AIM: The integration posts to transact.dll using
   Name-Value Pair (NVP) fields prefixed with x_ — the exact pattern
   Authorize.net has deprecated. AIM is officially labeled "Deprecated" and
   will no longer receive updates including payment network mandate compliance
   updates.

   Ref: https://developer.authorize.net/api/upgrade_guide.html


Thanks,
Mridul Pathak

Re: Proposal: Remove deprecated third-party payment gateway integrations

Posted by Anil Patel <an...@hotwaxsystems.com>.
https://issues.apache.org/jira/browse/OFBIZ-3895



Thanks and Regards
Anil Patel
CEO
HotWax Systems
http://www.hotwaxsystems.com
Cell: + 1 509 398 3120


On Fri, Jun 19, 2026 at 7:41 PM Ratnesh Upadhyay <up...@gmail.com>
wrote:

> Hi Mridul,
>
> Thank you for putting together such a detailed and well-researched
> proposal.
>
> +1 on removing these legacy payment gateway integrations.
>
> Maintaining dead code adds unnecessary technical debt to the project.
>
> Cleaning these out makes complete sense; it prevents new users or adopters
> from trying to implement gateways that are fundamentally broken or
> deprecated by the vendors themselves.
>
> Regards,
>
> Ratnesh Upadhyay
>
> On Fri, 19 Jun 2026 at 19:23, Arun Patidar <ar...@hotwax.co> wrote:
>
> > Hi Mridul,
> >
> > +1 for removing these integrations.
> >
> >
> > Thanks,
> >
> > Arun Patidar
> >
> > On Fri, Jun 19, 2026 at 7:18 PM Anil Patel <anil.patel@hotwaxsystems.com
> >
> > wrote:
> >
> > > Hi Mridul,
> > >
> > > Thank you for the thorough research. I fully support this proposal.
> > >
> > > A quick look at the current trunk confirms the picture:
> > >
> > > All 25 Java source files across these 9 gateway directories are still
> > > present in
> > >
> > >
> >
> applications/accounting/src/main/java/org/apache/ofbiz/accounting/thirdparty/,
> > > totalling approximately 12,000 lines of code.
> > > Every recent commit touching these files has been cosmetic — checkstyle
> > > fixes, indentation corrections, unused import removal. Not one has
> > > addressed actual payment logic. The upstream APIs they target have
> moved
> > > on, and the code has not.
> > > The SagePay/Opayo endpoints (live.sagepay.com, test.sagepay.com)
> stopped
> > > responding on March 31, 2024 — already over a year ago. Any OFBiz
> > > installation still wired to SagePay is silently failing.
> > > The CyberSource SOAP API deadline is June 24, 2026 — five days from
> now.
> > > Username/password authentication will be rejected at that point with no
> > > remediation path short of a full rewrite.
> > >
> > > Dead code that cannot be tested against a live endpoint is worse than
> no
> > > code — it gives implementors false confidence, adds maintenance surface
> > for
> > > security patches and Java upgrades, and makes the codebase harder to
> > > navigate.
> > >
> > > +1 to remove all of the listed integrations. If any active user is
> > running
> > > one of these gateways, now is the right time for them to speak up —
> > > otherwise the silence is its own answer.
> > >
> > > Thanks again for the detailed write-up.
> > >
> > >
> > >
> > > Thanks and Regards
> > > Anil Patel
> > > CEO
> > > HotWax Systems
> > > http://www.hotwaxsystems.com
> > > Cell: + 1 509 398 3120
> > >
> > >
> > > On Fri, Jun 19, 2026 at 6:37 PM Mridul Pathak <mridulpathak@apache.org
> >
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > >
> > > > I'd like to propose removing the following payment gateway
> integrations
> > > > from applications/accounting/ whose third-party APIs and SDKs are no
> > > longer
> > > > operational, deprecated, and haven't been maintained for a while:
> > > >
> > > >
> > > >    - PCCharge & RITA (GO Software / Verifone): Verifone announced
> > > >    end-of-life in April 2015; all support terminated on October 1,
> > 2015.
> > > > Both
> > > >    communicate over raw TCP/IP sockets to a local Windows daemon with
> > no
> > > > cloud
> > > >    successor.
> > > >    Ref:
> > > >
> > > >
> > >
> >
> https://3dmerchant.com/blog/merchant-processing-industry-news/pccharge-life-notice-verifone
> > > >    - ClearCommerce: Acquired by FIS. Implemented back in 2006 and
> never
> > > >    really maintained. The original platform and its test endpoint are
> > no
> > > >    longer reachable.
> > > >    - Orbital (Chase Paymentech / Fiserv): Deprecated; no new
> onboarding
> > > >    available. The proprietary SDK is no longer distributed and the
> > > > integration
> > > >    is already excluded from standard compilation.
> > > >    - Payflow Pro (PayPal): Officially labeled "legacy" by PayPal. ACH
> > > >    closed May 2021, 3DS v1.x  deprecated October 2022. The SDK (
> > > >    paypal.payflow.PayflowAPI) is unavailable in any public repository
> > and
> > > >    excluded from compilation.
> > > >    - PayPal NVP / Classic API: Officially labeled "legacy". All
> > dependent
> > > >    resources (Orders v1, Payments v1, Billing Agreements, etc.) are
> > > > formally
> > > >    deprecated by PayPal. The SDK (com.paypal.sdk.core.nvp.*) is
> > > unavailable
> > > >    publicly and excluded from compilation.
> > > >    Ref: https://developer.paypal.com/api/rest/deprecated-resources/
> > > >    Ref: https://developer.paypal.com/api/nvp-soap/
> > > >    - WorldPay: The specific product this integration targets,
> WorldPay
> > > >    Select Junior, is absent from Worldpay's current developer
> > > documentation
> > > >    entirely. The integration uses a redirect-based flow (instId
> > > parameter,
> > > >    select.worldpay.com) with no equivalent in the current Access
> > > Worldpay
> > > >    REST API.
> > > >
> > > >    Ref: https://developer.worldpay.com
> > > >    -
> > > >
> > > >    SecurePay (Australia): The integration uses the proprietary
> > > > securepay.jxa Java
> > > >    SDK targeting https://api.securepay.com.au/xmlapi/payment, which
> > has
> > > no
> > > >    public repository or Maven artifact. SecurePay has been acquired
> by
> > > Fat
> > > >    Zebra, whose platform is built on REST APIs with no equivalent to
> > this
> > > >    XML-based integration. The integration is already excluded from
> > > standard
> > > >    compilation in build.gradle due to the missing SDK.
> > > >
> > > >    Ref: https://www.fatzebra.com/blog/fat-zebra-acquires-securepay
> > > >    -
> > > >
> > > >    eWay (Australia): The integration targets hardcoded legacy .asp
> XML
> > > >    endpoints (https://www.eway.com.au/gateway/xmlpayment.asp,
> > > >    gateway_cvn/xmlpayment.asp) from eWAY's original gateway circa
> 2003.
> > > >    eWAY has fully replaced this with the Rapid API (REST/JSON).
> > NetSuite
> > > > has
> > > >    officially retired the eWAY XML gateway integration.
> > > >
> > > >    Ref:
> > > >
> > > >
> > >
> >
> https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html
> > > >    Ref: https://eway.io/api-v3/
> > > >    -
> > > >
> > > >    SagePay (now Elavon/Opayo): The integration targets SagePay's VPS
> > > >    Protocol v3.00, communicating with *.sagepay.com endpoints.
> SagePay
> > > was
> > > >    sold to Elavon in 2020 and rebranded as Opayo. Protocol v3.00 has
> > > since
> > > >    been mandated for removal in favour of v4.00, and all legacy
> > > > sagepay.com URLs
> > > >    (live.sagepay.com, test.sagepay.com) stopped working after March
> > 31,
> > > >    2024.
> > > >    -
> > > >
> > > >    CyberSource ICS (Simple Order API / SOAP): The integration uses
> the
> > > >    com.cybersource.ws.client SOAP SDK targeting API version 1.43.
> > > >    CyberSource has mandated migration away from the Simple Order API
> to
> > > its
> > > >    REST API, stating that users "must migrate" to REST-based
> services.
> > > >    Additionally, the SOAP API's current username/password
> > authentication
> > > > will
> > > >    be rejected after June 24, 2026, with no path to continue using
> the
> > > >    Simple Order API beyond that point without a full
> re-implementation.
> > > The
> > > >    integration is already excluded from standard compilation in
> > > > build.gradle due
> > > >    to the missing SDK JAR.
> > > >
> > > >    Ref:
> > > >
> > > >
> > >
> >
> https://developer.cybersource.com/docs/cybs/en-us/rb-upgrade/migration/all/na/recurring-billing-upgrade/rb-upgrade-actions/rb-upgrade-updating/rb-upgrade-apis.html
> > > >    Ref:
> > > >
> > > >
> > >
> >
> https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.html
> > > >    -
> > > >
> > > >    Authorize.Net AIM: The integration posts to transact.dll using
> > > >    Name-Value Pair (NVP) fields prefixed with x_ — the exact pattern
> > > >    Authorize.net has deprecated. AIM is officially labeled
> "Deprecated"
> > > and
> > > >    will no longer receive updates including payment network mandate
> > > > compliance
> > > >    updates.
> > > >
> > > >    Ref: https://developer.authorize.net/api/upgrade_guide.html
> > > >
> > > >
> > > > Thanks,
> > > > Mridul Pathak
> > > >
> > >
>

Re: Proposal: Remove deprecated third-party payment gateway integrations

Posted by Ratnesh Upadhyay <up...@gmail.com>.
Hi Mridul,

Thank you for putting together such a detailed and well-researched proposal.

+1 on removing these legacy payment gateway integrations.

Maintaining dead code adds unnecessary technical debt to the project.

Cleaning these out makes complete sense; it prevents new users or adopters
from trying to implement gateways that are fundamentally broken or
deprecated by the vendors themselves.

Regards,

Ratnesh Upadhyay

On Fri, 19 Jun 2026 at 19:23, Arun Patidar <ar...@hotwax.co> wrote:

> Hi Mridul,
>
> +1 for removing these integrations.
>
>
> Thanks,
>
> Arun Patidar
>
> On Fri, Jun 19, 2026 at 7:18 PM Anil Patel <an...@hotwaxsystems.com>
> wrote:
>
> > Hi Mridul,
> >
> > Thank you for the thorough research. I fully support this proposal.
> >
> > A quick look at the current trunk confirms the picture:
> >
> > All 25 Java source files across these 9 gateway directories are still
> > present in
> >
> >
> applications/accounting/src/main/java/org/apache/ofbiz/accounting/thirdparty/,
> > totalling approximately 12,000 lines of code.
> > Every recent commit touching these files has been cosmetic — checkstyle
> > fixes, indentation corrections, unused import removal. Not one has
> > addressed actual payment logic. The upstream APIs they target have moved
> > on, and the code has not.
> > The SagePay/Opayo endpoints (live.sagepay.com, test.sagepay.com) stopped
> > responding on March 31, 2024 — already over a year ago. Any OFBiz
> > installation still wired to SagePay is silently failing.
> > The CyberSource SOAP API deadline is June 24, 2026 — five days from now.
> > Username/password authentication will be rejected at that point with no
> > remediation path short of a full rewrite.
> >
> > Dead code that cannot be tested against a live endpoint is worse than no
> > code — it gives implementors false confidence, adds maintenance surface
> for
> > security patches and Java upgrades, and makes the codebase harder to
> > navigate.
> >
> > +1 to remove all of the listed integrations. If any active user is
> running
> > one of these gateways, now is the right time for them to speak up —
> > otherwise the silence is its own answer.
> >
> > Thanks again for the detailed write-up.
> >
> >
> >
> > Thanks and Regards
> > Anil Patel
> > CEO
> > HotWax Systems
> > http://www.hotwaxsystems.com
> > Cell: + 1 509 398 3120
> >
> >
> > On Fri, Jun 19, 2026 at 6:37 PM Mridul Pathak <mr...@apache.org>
> > wrote:
> >
> > > Hi all,
> > >
> > >
> > > I'd like to propose removing the following payment gateway integrations
> > > from applications/accounting/ whose third-party APIs and SDKs are no
> > longer
> > > operational, deprecated, and haven't been maintained for a while:
> > >
> > >
> > >    - PCCharge & RITA (GO Software / Verifone): Verifone announced
> > >    end-of-life in April 2015; all support terminated on October 1,
> 2015.
> > > Both
> > >    communicate over raw TCP/IP sockets to a local Windows daemon with
> no
> > > cloud
> > >    successor.
> > >    Ref:
> > >
> > >
> >
> https://3dmerchant.com/blog/merchant-processing-industry-news/pccharge-life-notice-verifone
> > >    - ClearCommerce: Acquired by FIS. Implemented back in 2006 and never
> > >    really maintained. The original platform and its test endpoint are
> no
> > >    longer reachable.
> > >    - Orbital (Chase Paymentech / Fiserv): Deprecated; no new onboarding
> > >    available. The proprietary SDK is no longer distributed and the
> > > integration
> > >    is already excluded from standard compilation.
> > >    - Payflow Pro (PayPal): Officially labeled "legacy" by PayPal. ACH
> > >    closed May 2021, 3DS v1.x  deprecated October 2022. The SDK (
> > >    paypal.payflow.PayflowAPI) is unavailable in any public repository
> and
> > >    excluded from compilation.
> > >    - PayPal NVP / Classic API: Officially labeled "legacy". All
> dependent
> > >    resources (Orders v1, Payments v1, Billing Agreements, etc.) are
> > > formally
> > >    deprecated by PayPal. The SDK (com.paypal.sdk.core.nvp.*) is
> > unavailable
> > >    publicly and excluded from compilation.
> > >    Ref: https://developer.paypal.com/api/rest/deprecated-resources/
> > >    Ref: https://developer.paypal.com/api/nvp-soap/
> > >    - WorldPay: The specific product this integration targets, WorldPay
> > >    Select Junior, is absent from Worldpay's current developer
> > documentation
> > >    entirely. The integration uses a redirect-based flow (instId
> > parameter,
> > >    select.worldpay.com) with no equivalent in the current Access
> > Worldpay
> > >    REST API.
> > >
> > >    Ref: https://developer.worldpay.com
> > >    -
> > >
> > >    SecurePay (Australia): The integration uses the proprietary
> > > securepay.jxa Java
> > >    SDK targeting https://api.securepay.com.au/xmlapi/payment, which
> has
> > no
> > >    public repository or Maven artifact. SecurePay has been acquired by
> > Fat
> > >    Zebra, whose platform is built on REST APIs with no equivalent to
> this
> > >    XML-based integration. The integration is already excluded from
> > standard
> > >    compilation in build.gradle due to the missing SDK.
> > >
> > >    Ref: https://www.fatzebra.com/blog/fat-zebra-acquires-securepay
> > >    -
> > >
> > >    eWay (Australia): The integration targets hardcoded legacy .asp XML
> > >    endpoints (https://www.eway.com.au/gateway/xmlpayment.asp,
> > >    gateway_cvn/xmlpayment.asp) from eWAY's original gateway circa 2003.
> > >    eWAY has fully replaced this with the Rapid API (REST/JSON).
> NetSuite
> > > has
> > >    officially retired the eWAY XML gateway integration.
> > >
> > >    Ref:
> > >
> > >
> >
> https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html
> > >    Ref: https://eway.io/api-v3/
> > >    -
> > >
> > >    SagePay (now Elavon/Opayo): The integration targets SagePay's VPS
> > >    Protocol v3.00, communicating with *.sagepay.com endpoints. SagePay
> > was
> > >    sold to Elavon in 2020 and rebranded as Opayo. Protocol v3.00 has
> > since
> > >    been mandated for removal in favour of v4.00, and all legacy
> > > sagepay.com URLs
> > >    (live.sagepay.com, test.sagepay.com) stopped working after March
> 31,
> > >    2024.
> > >    -
> > >
> > >    CyberSource ICS (Simple Order API / SOAP): The integration uses the
> > >    com.cybersource.ws.client SOAP SDK targeting API version 1.43.
> > >    CyberSource has mandated migration away from the Simple Order API to
> > its
> > >    REST API, stating that users "must migrate" to REST-based services.
> > >    Additionally, the SOAP API's current username/password
> authentication
> > > will
> > >    be rejected after June 24, 2026, with no path to continue using the
> > >    Simple Order API beyond that point without a full re-implementation.
> > The
> > >    integration is already excluded from standard compilation in
> > > build.gradle due
> > >    to the missing SDK JAR.
> > >
> > >    Ref:
> > >
> > >
> >
> https://developer.cybersource.com/docs/cybs/en-us/rb-upgrade/migration/all/na/recurring-billing-upgrade/rb-upgrade-actions/rb-upgrade-updating/rb-upgrade-apis.html
> > >    Ref:
> > >
> > >
> >
> https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.html
> > >    -
> > >
> > >    Authorize.Net AIM: The integration posts to transact.dll using
> > >    Name-Value Pair (NVP) fields prefixed with x_ — the exact pattern
> > >    Authorize.net has deprecated. AIM is officially labeled "Deprecated"
> > and
> > >    will no longer receive updates including payment network mandate
> > > compliance
> > >    updates.
> > >
> > >    Ref: https://developer.authorize.net/api/upgrade_guide.html
> > >
> > >
> > > Thanks,
> > > Mridul Pathak
> > >
> >

Re: Proposal: Remove deprecated third-party payment gateway integrations

Posted by Arun Patidar <ar...@hotwax.co>.
Hi Mridul,

+1 for removing these integrations.


Thanks,

Arun Patidar

On Fri, Jun 19, 2026 at 7:18 PM Anil Patel <an...@hotwaxsystems.com>
wrote:

> Hi Mridul,
>
> Thank you for the thorough research. I fully support this proposal.
>
> A quick look at the current trunk confirms the picture:
>
> All 25 Java source files across these 9 gateway directories are still
> present in
>
> applications/accounting/src/main/java/org/apache/ofbiz/accounting/thirdparty/,
> totalling approximately 12,000 lines of code.
> Every recent commit touching these files has been cosmetic — checkstyle
> fixes, indentation corrections, unused import removal. Not one has
> addressed actual payment logic. The upstream APIs they target have moved
> on, and the code has not.
> The SagePay/Opayo endpoints (live.sagepay.com, test.sagepay.com) stopped
> responding on March 31, 2024 — already over a year ago. Any OFBiz
> installation still wired to SagePay is silently failing.
> The CyberSource SOAP API deadline is June 24, 2026 — five days from now.
> Username/password authentication will be rejected at that point with no
> remediation path short of a full rewrite.
>
> Dead code that cannot be tested against a live endpoint is worse than no
> code — it gives implementors false confidence, adds maintenance surface for
> security patches and Java upgrades, and makes the codebase harder to
> navigate.
>
> +1 to remove all of the listed integrations. If any active user is running
> one of these gateways, now is the right time for them to speak up —
> otherwise the silence is its own answer.
>
> Thanks again for the detailed write-up.
>
>
>
> Thanks and Regards
> Anil Patel
> CEO
> HotWax Systems
> http://www.hotwaxsystems.com
> Cell: + 1 509 398 3120
>
>
> On Fri, Jun 19, 2026 at 6:37 PM Mridul Pathak <mr...@apache.org>
> wrote:
>
> > Hi all,
> >
> >
> > I'd like to propose removing the following payment gateway integrations
> > from applications/accounting/ whose third-party APIs and SDKs are no
> longer
> > operational, deprecated, and haven't been maintained for a while:
> >
> >
> >    - PCCharge & RITA (GO Software / Verifone): Verifone announced
> >    end-of-life in April 2015; all support terminated on October 1, 2015.
> > Both
> >    communicate over raw TCP/IP sockets to a local Windows daemon with no
> > cloud
> >    successor.
> >    Ref:
> >
> >
> https://3dmerchant.com/blog/merchant-processing-industry-news/pccharge-life-notice-verifone
> >    - ClearCommerce: Acquired by FIS. Implemented back in 2006 and never
> >    really maintained. The original platform and its test endpoint are no
> >    longer reachable.
> >    - Orbital (Chase Paymentech / Fiserv): Deprecated; no new onboarding
> >    available. The proprietary SDK is no longer distributed and the
> > integration
> >    is already excluded from standard compilation.
> >    - Payflow Pro (PayPal): Officially labeled "legacy" by PayPal. ACH
> >    closed May 2021, 3DS v1.x  deprecated October 2022. The SDK (
> >    paypal.payflow.PayflowAPI) is unavailable in any public repository and
> >    excluded from compilation.
> >    - PayPal NVP / Classic API: Officially labeled "legacy". All dependent
> >    resources (Orders v1, Payments v1, Billing Agreements, etc.) are
> > formally
> >    deprecated by PayPal. The SDK (com.paypal.sdk.core.nvp.*) is
> unavailable
> >    publicly and excluded from compilation.
> >    Ref: https://developer.paypal.com/api/rest/deprecated-resources/
> >    Ref: https://developer.paypal.com/api/nvp-soap/
> >    - WorldPay: The specific product this integration targets, WorldPay
> >    Select Junior, is absent from Worldpay's current developer
> documentation
> >    entirely. The integration uses a redirect-based flow (instId
> parameter,
> >    select.worldpay.com) with no equivalent in the current Access
> Worldpay
> >    REST API.
> >
> >    Ref: https://developer.worldpay.com
> >    -
> >
> >    SecurePay (Australia): The integration uses the proprietary
> > securepay.jxa Java
> >    SDK targeting https://api.securepay.com.au/xmlapi/payment, which has
> no
> >    public repository or Maven artifact. SecurePay has been acquired by
> Fat
> >    Zebra, whose platform is built on REST APIs with no equivalent to this
> >    XML-based integration. The integration is already excluded from
> standard
> >    compilation in build.gradle due to the missing SDK.
> >
> >    Ref: https://www.fatzebra.com/blog/fat-zebra-acquires-securepay
> >    -
> >
> >    eWay (Australia): The integration targets hardcoded legacy .asp XML
> >    endpoints (https://www.eway.com.au/gateway/xmlpayment.asp,
> >    gateway_cvn/xmlpayment.asp) from eWAY's original gateway circa 2003.
> >    eWAY has fully replaced this with the Rapid API (REST/JSON). NetSuite
> > has
> >    officially retired the eWAY XML gateway integration.
> >
> >    Ref:
> >
> >
> https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html
> >    Ref: https://eway.io/api-v3/
> >    -
> >
> >    SagePay (now Elavon/Opayo): The integration targets SagePay's VPS
> >    Protocol v3.00, communicating with *.sagepay.com endpoints. SagePay
> was
> >    sold to Elavon in 2020 and rebranded as Opayo. Protocol v3.00 has
> since
> >    been mandated for removal in favour of v4.00, and all legacy
> > sagepay.com URLs
> >    (live.sagepay.com, test.sagepay.com) stopped working after March 31,
> >    2024.
> >    -
> >
> >    CyberSource ICS (Simple Order API / SOAP): The integration uses the
> >    com.cybersource.ws.client SOAP SDK targeting API version 1.43.
> >    CyberSource has mandated migration away from the Simple Order API to
> its
> >    REST API, stating that users "must migrate" to REST-based services.
> >    Additionally, the SOAP API's current username/password authentication
> > will
> >    be rejected after June 24, 2026, with no path to continue using the
> >    Simple Order API beyond that point without a full re-implementation.
> The
> >    integration is already excluded from standard compilation in
> > build.gradle due
> >    to the missing SDK JAR.
> >
> >    Ref:
> >
> >
> https://developer.cybersource.com/docs/cybs/en-us/rb-upgrade/migration/all/na/recurring-billing-upgrade/rb-upgrade-actions/rb-upgrade-updating/rb-upgrade-apis.html
> >    Ref:
> >
> >
> https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.html
> >    -
> >
> >    Authorize.Net AIM: The integration posts to transact.dll using
> >    Name-Value Pair (NVP) fields prefixed with x_ — the exact pattern
> >    Authorize.net has deprecated. AIM is officially labeled "Deprecated"
> and
> >    will no longer receive updates including payment network mandate
> > compliance
> >    updates.
> >
> >    Ref: https://developer.authorize.net/api/upgrade_guide.html
> >
> >
> > Thanks,
> > Mridul Pathak
> >
>

Re: Proposal: Remove deprecated third-party payment gateway integrations

Posted by Anil Patel <an...@hotwaxsystems.com>.
Hi Mridul,

Thank you for the thorough research. I fully support this proposal.

A quick look at the current trunk confirms the picture:

All 25 Java source files across these 9 gateway directories are still
present in
applications/accounting/src/main/java/org/apache/ofbiz/accounting/thirdparty/,
totalling approximately 12,000 lines of code.
Every recent commit touching these files has been cosmetic — checkstyle
fixes, indentation corrections, unused import removal. Not one has
addressed actual payment logic. The upstream APIs they target have moved
on, and the code has not.
The SagePay/Opayo endpoints (live.sagepay.com, test.sagepay.com) stopped
responding on March 31, 2024 — already over a year ago. Any OFBiz
installation still wired to SagePay is silently failing.
The CyberSource SOAP API deadline is June 24, 2026 — five days from now.
Username/password authentication will be rejected at that point with no
remediation path short of a full rewrite.

Dead code that cannot be tested against a live endpoint is worse than no
code — it gives implementors false confidence, adds maintenance surface for
security patches and Java upgrades, and makes the codebase harder to
navigate.

+1 to remove all of the listed integrations. If any active user is running
one of these gateways, now is the right time for them to speak up —
otherwise the silence is its own answer.

Thanks again for the detailed write-up.



Thanks and Regards
Anil Patel
CEO
HotWax Systems
http://www.hotwaxsystems.com
Cell: + 1 509 398 3120


On Fri, Jun 19, 2026 at 6:37 PM Mridul Pathak <mr...@apache.org>
wrote:

> Hi all,
>
>
> I'd like to propose removing the following payment gateway integrations
> from applications/accounting/ whose third-party APIs and SDKs are no longer
> operational, deprecated, and haven't been maintained for a while:
>
>
>    - PCCharge & RITA (GO Software / Verifone): Verifone announced
>    end-of-life in April 2015; all support terminated on October 1, 2015.
> Both
>    communicate over raw TCP/IP sockets to a local Windows daemon with no
> cloud
>    successor.
>    Ref:
>
> https://3dmerchant.com/blog/merchant-processing-industry-news/pccharge-life-notice-verifone
>    - ClearCommerce: Acquired by FIS. Implemented back in 2006 and never
>    really maintained. The original platform and its test endpoint are no
>    longer reachable.
>    - Orbital (Chase Paymentech / Fiserv): Deprecated; no new onboarding
>    available. The proprietary SDK is no longer distributed and the
> integration
>    is already excluded from standard compilation.
>    - Payflow Pro (PayPal): Officially labeled "legacy" by PayPal. ACH
>    closed May 2021, 3DS v1.x  deprecated October 2022. The SDK (
>    paypal.payflow.PayflowAPI) is unavailable in any public repository and
>    excluded from compilation.
>    - PayPal NVP / Classic API: Officially labeled "legacy". All dependent
>    resources (Orders v1, Payments v1, Billing Agreements, etc.) are
> formally
>    deprecated by PayPal. The SDK (com.paypal.sdk.core.nvp.*) is unavailable
>    publicly and excluded from compilation.
>    Ref: https://developer.paypal.com/api/rest/deprecated-resources/
>    Ref: https://developer.paypal.com/api/nvp-soap/
>    - WorldPay: The specific product this integration targets, WorldPay
>    Select Junior, is absent from Worldpay's current developer documentation
>    entirely. The integration uses a redirect-based flow (instId parameter,
>    select.worldpay.com) with no equivalent in the current Access Worldpay
>    REST API.
>
>    Ref: https://developer.worldpay.com
>    -
>
>    SecurePay (Australia): The integration uses the proprietary
> securepay.jxa Java
>    SDK targeting https://api.securepay.com.au/xmlapi/payment, which has no
>    public repository or Maven artifact. SecurePay has been acquired by Fat
>    Zebra, whose platform is built on REST APIs with no equivalent to this
>    XML-based integration. The integration is already excluded from standard
>    compilation in build.gradle due to the missing SDK.
>
>    Ref: https://www.fatzebra.com/blog/fat-zebra-acquires-securepay
>    -
>
>    eWay (Australia): The integration targets hardcoded legacy .asp XML
>    endpoints (https://www.eway.com.au/gateway/xmlpayment.asp,
>    gateway_cvn/xmlpayment.asp) from eWAY's original gateway circa 2003.
>    eWAY has fully replaced this with the Rapid API (REST/JSON). NetSuite
> has
>    officially retired the eWAY XML gateway integration.
>
>    Ref:
>
> https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html
>    Ref: https://eway.io/api-v3/
>    -
>
>    SagePay (now Elavon/Opayo): The integration targets SagePay's VPS
>    Protocol v3.00, communicating with *.sagepay.com endpoints. SagePay was
>    sold to Elavon in 2020 and rebranded as Opayo. Protocol v3.00 has since
>    been mandated for removal in favour of v4.00, and all legacy
> sagepay.com URLs
>    (live.sagepay.com, test.sagepay.com) stopped working after March 31,
>    2024.
>    -
>
>    CyberSource ICS (Simple Order API / SOAP): The integration uses the
>    com.cybersource.ws.client SOAP SDK targeting API version 1.43.
>    CyberSource has mandated migration away from the Simple Order API to its
>    REST API, stating that users "must migrate" to REST-based services.
>    Additionally, the SOAP API's current username/password authentication
> will
>    be rejected after June 24, 2026, with no path to continue using the
>    Simple Order API beyond that point without a full re-implementation. The
>    integration is already excluded from standard compilation in
> build.gradle due
>    to the missing SDK JAR.
>
>    Ref:
>
> https://developer.cybersource.com/docs/cybs/en-us/rb-upgrade/migration/all/na/recurring-billing-upgrade/rb-upgrade-actions/rb-upgrade-updating/rb-upgrade-apis.html
>    Ref:
>
> https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.html
>    -
>
>    Authorize.Net AIM: The integration posts to transact.dll using
>    Name-Value Pair (NVP) fields prefixed with x_ — the exact pattern
>    Authorize.net has deprecated. AIM is officially labeled "Deprecated" and
>    will no longer receive updates including payment network mandate
> compliance
>    updates.
>
>    Ref: https://developer.authorize.net/api/upgrade_guide.html
>
>
> Thanks,
> Mridul Pathak
>