[4.0] Common Payment API

[nobicycle]

Is your feature request related to a problem? Please describe.

8000 extensions in the JED. Probably several hundred payment gateways in existence globally.
8000 x 400 = 3 200 000 = 3.2 million potential gateway pieces of code.

Financial processing is probably the most highly sensitive of all processing done within Joomla, and yet it is dispersed among innumerable code plugins. The risks are:

• Waste of resources.
• Each gateway code coded by a different developer - risk of errors.
• Should this situation be exploited by an unscrupulous developer it might reflect badly on Joomla.

Describe the solution you'd like

Choose one of the Open Source Common Gateway's that have been offered to the Joomla community and incorporate it in core Joomla. Candidates known to me are:

1. Payage
   https://www.lesarbresdesign.info/extensions/payage

2.Techjoomla
https://techjoomla.com/common-payment-api

Please report at https://github.com/joomla/jed-issues/issues/new

Closed as wrong Repo.

[nobicycle]

Closing this within 200 microseconds is impressive. However, the issue raised was about the core. Not JED.

@nobicycle sorry, reopened for Reason stated above.

[alikon]

IMHO this matter should be re-considered for inclusion in 4.x at least to give some basic API
given we already have some proposal like https://techjoomla.com/common-payment-api standing from 2012

[mbabker]

👎 because Joomla seems to love re-inventing the wheel, Joomla does not have the resources to build and maintain its own payment gateway APIs. There is nothing wrong with encouraging developers to utilize libraries such as Omnipay or Payum, or utilizing the SDKs of the gateways they do support, but this is not core territory.

[Bakual]

As Michael already wrote, there is no way we could even remotely support that, nor should we.
Use one of the solutions which already exist.

[dgrammatiko]

@mbabker is right not only for the reasons stated above but mainly because the W3C already solved this problems for us (devs) with the payment API:
https://caniuse.com/#feat=payment-request

https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API

It would be nice to check the state of the web periodically, things do evolve...

[Fedik]

@nobicycle when you doing your Shop extension, set dependency to one of existing payment extension, and if everyone will do that, then your problem are solved.
Easy, no?

There also many PHP libraries for it:
https://github.com/thephpleague/omnipay
https://github.com/Payum/Payum

In the core it will be dead and useless piece of code.
Maximum that it could be it like com_weblinks, separated component (that actually can be just wrapper to one of existing library). But be honest, who will support it?

[Bakual]

I'm closing this issue for the reasons stated above.