Bien Nguyen
Sep 14, 2017
  6307
(5 votes)

Payment providers source code are now available on GitHub

The source code for payment providers, including PayPal, DIBS, DataCash have been released to GitHub. These projects were upgraded to work with latest version of Commerce (11.2.2) and other components, that contains a few fixes and refactoring. They're now open-source and you might be great contributors :). We'll continue to update them. It means that we'll do continuous releases for them but they might be updated less frequently (than Commerce packages). It also means that we won't provide source code packages for those projects (.zip files) from the release 11.2.2. If you need the source codes, you can download from GitHub. 

So now with the /nSoftware payment gateways, which has been available on GitHub from about 1 year, we have now 4 payment provider projects on GitHub. Please visit the repository on GitHub for more detail.

All documentation related to installation/configuration are still on EPi World.

Sep 14, 2017

Comments

Frederik Vig
Frederik Vig Sep 15, 2017 03:16 PM

Could you also add the Authorize.net gateway source code? Thanks.

Quan Mai
Quan Mai Sep 16, 2017 11:09 AM

@Frederik: We haven't released Authorize.net source code yet, so it's not part of the moving to to Github this time. But we will look into this and that might happen in the future.

Frederik Vig
Frederik Vig Sep 16, 2017 04:11 PM

@Quan - thanks, for us it would be very useful, since we've had to do some modifications in order to integrate with a fraud detection service (and we're always happy to do PRs to support and improve it).

Please login to comment.
Latest blogs
A First Look at Optimizely Remote MCP Server for Experimentation

Optimizely just released a Remote MCP Server for Experimentation and I've been trying it out to see what it can do. If you don't know, MCP (Model...

Jacob Pretorius | May 1, 2026

Promoted and Certified

What a busy week

Andy Blyth | May 1, 2026 |

Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |