You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mridul Pathak (Jira)" <ji...@apache.org> on 2026/06/22 11:38:00 UTC

[jira] [Updated] (OFBIZ-13446) Remove deprecated and defunct 3rd Party Payment Integrations from applications

     [ https://issues.apache.org/jira/browse/OFBIZ-13446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Pathak updated OFBIZ-13446:
----------------------------------
    Description: 
Remove 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.*{}}}{color:#0a0a0a}) is unavailable publicly and excluded from compilation.{color}Ref: [https://developer.paypal.com/api/rest/deprecated-resources/]
Ref: [https://developer.paypal.com/api/nvp-soap/]
 * {color:#000000}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|http://select.worldpay.com/]{}}}) with no equivalent in the current Access Worldpay REST API.{color}
{color:#000000}Ref: [https://developer.worldpay.com|https://developer.worldpay.com/]{color}

 * SecurePay (Australia):{color:#000000} 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.
{color}Ref: [https://www.fatzebra.com/blog/fat-zebra-acquires-securepay]

 * eWay (Australia): {color:#000000}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.
{color}Ref: [https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html]
Ref: [https://eway.io/api-v3/]

 * {color:#000000}SagePay (now Elavon/Opayo): The integration targets SagePay's VPS Protocol v3.00, communicating with {{*.[sagepay.com|http://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|http://sagepay.com/]}} URLs ({{{}[live.sagepay.com|http://live.sagepay.com/]{}}}, {{{}[test.sagepay.com|http://test.sagepay.com/]{}}}) stopped working after March 31, 2024.{color}

 * {color:#000000}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.
{color}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]

 * {color:#000000}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.
{color}Ref: [https://developer.authorize.net/api/upgrade_guide.html]

  was:
Remove 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.*{}}}{color:#0a0a0a}) is unavailable publicly and excluded from compilation.
{color}Ref: [https://developer.paypal.com/api/rest/deprecated-resources/]
Ref: [https://developer.paypal.com/api/nvp-soap/]
 * {color:#000000}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|http://select.worldpay.com/]{}}}) with no equivalent in the current Access Worldpay REST API.{color}
{color:#000000}Ref: [https://developer.worldpay.com|https://developer.worldpay.com/]{color}

 * SecurePay (Australia):{color:#000000} 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.{color}

{color:#000000}Ref: [https://www.fatzebra.com/blog/fat-zebra-acquires-securepay]{color}

 * eWay (Australia): {color:#000000}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.{color}

{color:#000000}Ref: [https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html]
Ref: [https://eway.io/api-v3/]{color}

 * {color:#000000}SagePay (now Elavon/Opayo): The integration targets SagePay's VPS Protocol v3.00, communicating with {{*.[sagepay.com|http://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|http://sagepay.com/]}} URLs ({{{}[live.sagepay.com|http://live.sagepay.com/]{}}}, {{{}[test.sagepay.com|http://test.sagepay.com/]{}}}) stopped working after March 31, 2024.{color}

 * {color:#000000}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.{color}

{color:#000000}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]{color}

 * {color:#000000}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.{color}

{color:#000000}Ref: [https://developer.authorize.net/api/upgrade_guide.html]{color}


> Remove deprecated and defunct 3rd Party Payment Integrations from applications
> ------------------------------------------------------------------------------
>
>                 Key: OFBIZ-13446
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13446
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting, order
>    Affects Versions: Upcoming Branch
>            Reporter: Mridul Pathak
>            Assignee: Mridul Pathak
>            Priority: Major
>
> Remove 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.*{}}}{color:#0a0a0a}) is unavailable publicly and excluded from compilation.{color}Ref: [https://developer.paypal.com/api/rest/deprecated-resources/]
> Ref: [https://developer.paypal.com/api/nvp-soap/]
>  * {color:#000000}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|http://select.worldpay.com/]{}}}) with no equivalent in the current Access Worldpay REST API.{color}
> {color:#000000}Ref: [https://developer.worldpay.com|https://developer.worldpay.com/]{color}
>  * SecurePay (Australia):{color:#000000} 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.
> {color}Ref: [https://www.fatzebra.com/blog/fat-zebra-acquires-securepay]
>  * eWay (Australia): {color:#000000}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.
> {color}Ref: [https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1492528191.html]
> Ref: [https://eway.io/api-v3/]
>  * {color:#000000}SagePay (now Elavon/Opayo): The integration targets SagePay's VPS Protocol v3.00, communicating with {{*.[sagepay.com|http://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|http://sagepay.com/]}} URLs ({{{}[live.sagepay.com|http://live.sagepay.com/]{}}}, {{{}[test.sagepay.com|http://test.sagepay.com/]{}}}) stopped working after March 31, 2024.{color}
>  * {color:#000000}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.
> {color}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]
>  * {color:#000000}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.
> {color}Ref: [https://developer.authorize.net/api/upgrade_guide.html]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)